Editing Talk:RCOXML Objects

=WidgetType=
See the "paf" [[VSH Exports]]

It seems the '''WidgetType''' is an identifyer of what rcomage and this wiki page baptished as "objects". Of all them, or only a group

By looking at the internal RCO structure is obvious that the value used internally to identify every "object" is the first field of what we has been naming [[Template:RCO TOC entry common area]], or in other words, the [[Template:RCO TOC entry types]]

So the question is... all "RCO TOC entry types" should be considered WidgetType ? (and consequentlly needed to be renamed in wiki pages)... or only a group of them are considered "widgets" ? and there is other group (no idea wich one by now, but [RCOXML Animations] could have a different name)

By looking [https://gist.github.com/anonymous/331c41b7b60af35c62363700ad88e6b3 at this list] is posible to make a list of the exports that uses the keyword "WidgetType" and deduce the correspondency with the names we have been using in rcomage/wiki. Most of the "unnofficial" names we have been using matches exactlly, others partially, and there are a few "new" names hard to deduce to wich "object" corresponds, and probably are included the 2 infamous '''ObjUnknown0xB''' and '''ObjUnknown0x1B''' that are completlly unknown for rcomage and doesnt seems to be used in any of the official PSP and PS3 firmwares

{| class="wikitable"
|-
! [[VSH Exports]] string chunk !! <abbr title="and name in wiki by now, at some point could be changed">name in RCOmage</abbr> !! internal type value !! Notes
|-
| ZN3paf8Ph'''Widget'''10WidgetTypeEv || ? || ? || weird, a WidgetType named Widget ?... this sounds too generic
|-
| ZN3paf7Ph'''Scene'''10WidgetTypeEv || ? || ? || also, this one sounds too generic too, maybe is the name of the "ObjectTree" (actually, all the trees ?)
|-
| ZN3paf7Ph'''Plane'''10WidgetTypeEv || {{cellcolors|#00aa00}} <abbr title="the unnofficial name matches with the official name">'''Plane'''</abbr> || 0x02 || 
|-
| ZN3paf8Ph'''Button'''10WidgetTypeEv || {{cellcolors|#00aa00}} <abbr title="the unnofficial name matches with the official name">'''Button'''</abbr> || 0x03 || 
|-
| ZN3paf6Ph'''Text'''10WidgetTypeEv || {{cellcolors|#00aa00}} <abbr title="the unnofficial name matches with the official name">'''Text'''</abbr> || 0x0D || 
|-
| ZN3paf8Ph'''Scroll'''10WidgetTypeEv || {{cellcolors|#00aa00}} <abbr title="the unnofficial name matches with the official name">'''Scroll'''</abbr> || 0x08 || 
|-
| ZN3paf11Ph'''LabelPrim'''10WidgetTypeEv || ? || ? || candidate to be '''ObjUnknown0xB''' or '''ObjUnknown0x1B'''
|-
| ZN3paf12Ph'''LevelMeter'''10WidgetTypeEv || {{cellcolors|#aa0000}} <abbr title="the unnofficial name matches partially with the official name">'''Meter'''</abbr> || 0x1E || 
|-
| ZN3paf10Ph'''Progress'''10WidgetTypeEv || {{cellcolors|#00aa00}} <abbr title="the unnofficial name matches with the official name">'''Progress'''</abbr> || 0x07 || 
|-
| ZN3paf10Ph'''CheckBox'''10WidgetTypeEv || {{cellcolors|#aa0000}} <abbr title="the unnofficial name matches partially with the official name, but the unnofficial is more explicit, only problem with the unnofficial name is longer">'''CheckBoxItem'''</abbr> || 0X1D || 
|-
| ZN3paf7Ph'''XmBar'''10WidgetTypeEv || ? || ? || 
|-
| ZN3paf8Ph'''XmList'''10WidgetTypeEv || ? || ? || 
|-
| ZN3paf8Ph'''XmItem'''10WidgetTypeEv || ? || ? || 
|-
| ZN3paf10Ph'''ItemSpin'''10WidgetTypeEv || {{cellcolors|#00aa00}} <abbr title="the unnofficial name matches with the official name">'''ItemSpin'''</abbr> || 0x11 || 
|-
| <abbr title="and ZNK3paf9Ph'''NumSpin'''13GetWidgetTypeEv">ZN3paf9Ph'''NumSpin'''10WidgetTypeEv</abbr> || {{cellcolors|#aa0000}} <abbr title="the unnofficial name matches partially with the official name">'''Spin'''</abbr> ? || 0x0F ? || 
|-
| ZN3paf6Ph'''List'''10WidgetTypeEv || ? || ? || 
|-
| ZN3paf10Ph'''InfoList'''10WidgetTypeEv || {{cellcolors|#aa0000}} <abbr title="the unnofficial name matches partially with the official name">'''IList'''</abbr> || 0x17 || 
|-
| ZN3paf10Ph'''MenuList'''10WidgetTypeEv || {{cellcolors|#aa0000}} <abbr title="the unnofficial name matches partially with the official name">'''MList'''</abbr> || 0x09 || 
|-
| ZN3paf14Ph'''CheckBoxList'''10WidgetTypeEv || {{cellcolors|#aa0000}} <abbr title="the unnofficial name matches partially with the official name">'''CheckBoxGroup'''</abbr> || 0x1C || 
|-
| ZN3paf11Ph'''LabelText'''10WidgetTypeEv || {{cellcolors|#aa0000}} <abbr title="the unnofficial name doesn't matches with the official name">'''EditBox'''</abbr> ? || 0x1F ? || 
|-
| ZN3paf7Ph'''Clock'''10WidgetTypeEv || {{cellcolors|#00aa00}} <abbr title="the unnofficial name matches with the official name">'''Clock'''</abbr> || 0x16 || 
|-
| ZN3paf8Ph'''IPAddr'''10WidgetTypeEv || ? || ? || candidate to be '''ObjUnknown0xB''' or '''ObjUnknown0x1B'''. <abbr title="it could be the frame used to display the red warning of ''service mode''">A widget only to dislay the IP address ?</abbr>
|}

=ObjUnknown0xB=
<strike>*Superbrainstorming based on smoke</strike>. '''This brainstorming seems to be wrong''', because the object named "XMList" by rcomage seems to be an "item" so it cant have other xml "item" childrens
<strike>**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--[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 08:16, 8 December 2015 (UTC)
</strike>

=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...=
*[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%25E3%2581%25A7%25E4%25BD%25BF%25E7%2594%25A8%25E3%2581%2595%25E3%2582%258C%25E3%2582%258B%25E8%25A6%2581%25E7%25B4%25A0%25E3%2581%25A8%25E5%25B1%259E%25E6%2580%25A7&usg=ALkJrhgDxWnUbgejQi-PgJ-wyqCtUxGy_g Elements and attributes to be used in RCOmageXML]
*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=