Talk:RCOXML Objects: Difference between revisions
mNo edit summary |
m (→Objects used to build menues and ObjUnknown0xB: i would replace the short-names of the objects to build menues by the explicit-names, are much more intuitive, but im not sure wich names could be better) |
||
| Line 2: | Line 2: | ||
Probably shares some attributes and follows an strict hierarchy of parent/children: | Probably shares some attributes and follows an strict hierarchy of parent/children: | ||
XMenu | 0x04 XMenu (XMB Menu) | ||
XMList | 0x05 XMList (XMB Main List) | ||
XList | 0x06 XList (XMB List) | ||
XItem | 0x0C XItem (XMB List Item) | ||
MList | 0x09 MList (Menu List) | ||
MItem | 0x0A MItem (Menu Item) | ||
LList | 0x13 LList (L?? List) | ||
LItem | 0x14 LItem (L?? Item) | ||
IList | 0x17 IList (Info List) | ||
IItem | 0x18 IItem (Info Item) | ||
*Superbrainstorming based on smoke | *Superbrainstorming based on smoke | ||
Revision as of 16:05, 5 September 2016
Probably shares some attributes and follows an strict hierarchy of parent/children:
0x04 XMenu (XMB Menu) 0x05 XMList (XMB Main List) 0x06 XList (XMB List) 0x0C XItem (XMB List Item) 0x09 MList (Menu List) 0x0A MItem (Menu Item) 0x13 LList (L?? List) 0x14 LItem (L?? Item) 0x17 IList (Info List) 0x18 IItem (Info Item)
- Superbrainstorming based on smoke
what about this ?, matches prety fine with how are grouped. Main menu separated because is an special object created specifically for top XMB menu, and the others grouped in pairs for "list" and "item". Also matches how are ordered in rcomage. All this attributes appears consecutivelly in groups of two, at top... XMList and XList... then MList MItem... then ObjUnknown0xB and XItem... then LList and LItem... then IList and IItem. Note how XMList doesnt seems to have an XMItem
XMenu XMList ObjUnknown0xB <------ is XMItem ? XList XItem MList MItem LList LItem IList IItem
If this is true and ObjUnknown0xB is actually XMItem it seems is posible to deduce the attributes because the other "item" objects uses pretty similar attributes (usually 3 attributes, either images or texts), to verify it are needed some/lot of tests by copying the attributes from the other items and creating a 100% custom object for the experiment also a good understanding of all the other rcoxml code, so is hard to know, im not skilled/brave to build this frankenstein but i think the theory is good enought--Sandungas (talk) 08:16, 8 December 2015 (UTC)
Objects using overrides in the "specific" attributes
The "standard" attributes contains 6 overrides and most objects uses the "standard" attributes, but additionally to this ones some of the objects (seems to) use more overrides in the "specific" attributes
- Some menu builders
- MList (3 ?)
- LList (2 ?)
- IList (1 ?)
- Text based objects
- Text (3 ?)
- EditBox (3 ?)
- Others
- CheckboxGroup (1 ?)
- Meter (1 ?)
Links, notes, etc...
Elements and attributes to be used in RCOmageXML
rcomage xml
- https://translate.googleusercontent.com/translate_c?depth=1&hl=es&rurl=translate.google.com&sl=auto&tl=en&u=http://ctfs.wiki.fc2.com/wiki/RCOmageXML&usg=ALkJrhjRxsEgJ7QEiFf9aBAfxp9-eXKIsQ
- http://electricvoice.blog40.fc2.com/blog-entry-668.html
- https://translate.googleusercontent.com/translate_c?act=url&depth=1&hl=es&ie=UTF8&prev=_t&rurl=translate.google.com&sl=auto&tl=en&u=http://electricvoice.blog40.fc2.com/blog-category-21.html&usg=ALkJrhg33PGW3RXbfzfYuN1OcV9P5AkM0w
Suggestions
WIKI links spiderweb
All the info in front page related with "units conversions", "measure units" or "event types" from other pages has been moved here, but at some point needs to be converted to templates because is needed for RCOXML Objects, RCOXML Animations, one option is what i was trying to do before that is moving it to RCOXML Coding but now i prefer to keep that page only for XML coding (is a bit empty by now but is needed to fill it with basic examples and explain of how the xml tags are linked or connected)
Actually, the "event types" are the responsibles of triggering "actions" of the .sprx module associated (and the .sprx has hardcoded the events allowed by the .rco) so it could be interesting to display this template in some of the .sprx wiki pages with a short explain of what are the "events" and his "types"
Some interesting details: This same method of triggering "actions" from the .rco by using "events" works the same with the embedded VSMX file (but none of the .rco used on PS3 includes an VSMX file, this format is from PSP days but is supposed to work on PS3). By looking at the code of an .rco you can find some "events" used but by looking at the .sprx sometimes there are secret/unused events
I been updating and cleaning up other pages to centralize a bit the mess in the pages related mostly with the info about how "override" attributes works, sorry for the confussion and all the movements of info but is because i wrote a lot before when most of it was research (like all related with the changelog of custom_render_plugin.rco) or speculations, later when i understood it i tryed to write a detailed explain (but is dirty and not short enought) and there is still a bit of "unknown" left (the purpose of the "factor" files from the "XMB Layouts", and last 2 bytes of the values stored as "overrides", proably are related). All this has been moved to XMB Layouts, i think the extended explain of how "overrides" works needs to be written there, but is needed a mention here in RCOXML Objects