XMBML Coding: Difference between revisions
(→Items) |
mNo edit summary |
||
Line 33: | Line 33: | ||
**<View id="seg_browser"> contains 1 <Items> with the key="browser" | **<View id="seg_browser"> contains 1 <Items> with the key="browser" | ||
=== View id === | === View id (Target ID's, and segment ID's) === | ||
Must consist of UTF-8 characters and have no spaces. There must be no other entries with the same '''<View id>'''. | Must consist of UTF-8 characters and have no spaces. There must be no other entries with the same '''<View id>'''. | ||
Line 44: | Line 44: | ||
**Links to a '''<View id>''' in another .xml file uses the '''localhost''' functions with the full path of the file followed by the character "'''#'''" and the '''<View id>''' of the linked item (e.g: '''src="xmb://localhost/dev_flash/vsh/resource/explore/xmb/category_user.xml#seg_poweroff"''') | **Links to a '''<View id>''' in another .xml file uses the '''localhost''' functions with the full path of the file followed by the character "'''#'''" and the '''<View id>''' of the linked item (e.g: '''src="xmb://localhost/dev_flash/vsh/resource/explore/xmb/category_user.xml#seg_poweroff"''') | ||
==== Items ==== | ==== Items contents (classes) ==== | ||
The contents of this sub group dictates what exists on the XMB when this entry is used. There can be more than one. | The contents of this sub group dictates what exists on the XMB when this entry is used. There can be more than one. | ||
Line 131: | Line 131: | ||
**Use a XMB database function. Example: '''src="xcb://localhost/query?table=MMS_MEDIA_TYPE_SYSTEM&genre=Music&sort=+StorageMedia:Common.titleForSort&cond=Ae+StorageMedia:StorageMedia.type %xCB_MEDIA_TYPE_DLNA"''' | **Use a XMB database function. Example: '''src="xcb://localhost/query?table=MMS_MEDIA_TYPE_SYSTEM&genre=Music&sort=+StorageMedia:Common.titleForSort&cond=Ae+StorageMedia:StorageMedia.type %xCB_MEDIA_TYPE_DLNA"''' | ||
==== Attributes ==== | ==== Attributes contents (pair keys) ==== | ||
This provides additional information about '''<Items>''' sub-entries by linking them to a table with attributes associated (is optionall, not all <Items> requires attributes), this tables uses a '''< Table key>''' matching the '''<attr>''' sub-entry asociated and contains one or more attributes separated in lines starting with '''<Pair key>'''. | This provides additional information about '''<Items>''' sub-entries by linking them to a table with attributes associated (is optionall, not all <Items> requires attributes), this tables uses a '''< Table key>''' matching the '''<attr>''' sub-entry asociated and contains one or more attributes separated in lines starting with '''<Pair key>'''. | ||
Revision as of 08:12, 23 January 2014
This page will outline the logic behind XMB .xml configuration files.
Basic Structure
This is a reduced version of category_network.xml with only one icon (tex_browser) that launches the webbrowser (type:x-xmb/xmlwebbrowser). The .xml is loaded starting from <View id="root">, then inside the <Items> table there is a <Query> linking to #seg_browser (the character "#" links to a <View id> in the same file, so is linked to <View id="seg_browser">). When <View id="seg_browser"> is loaded first starts reading the table of <Items> that contains an <Item> that is linked using attr="browser" to a table of attributes <Table key="browser"
Code Sample
- The whole contents of the .xml file can be identifyed by the <View id> and <key> this way:
- <View id="root"> contains 1 <Items> with the key="seg_browser"
- <View id="seg_browser"> contains 1 <Items> with the key="browser"
View id (Target ID's, and segment ID's)
Must consist of UTF-8 characters and have no spaces. There must be no other entries with the same <View id>.
- There are some specific <View id> names that are placed at the top of the .xml and can be considered the "XMB enviroments" that can be loaded by VSH
- "root", "root_for_dex", " tool_root", "shop_root", "shop_guest_root", "shop_staff_root", and "root_arcade"
- Are used to be able to load specific items for every Target ID or for loading items in specific conditions (e.g: is shop firmware "locked" or "unlocked" modes)
- A <View id> can load another <View id> from the same or other .xml file by making one of his <items> to point to the other <View id>
- Links to a <View id> in the same .xml file can be considered "direct links" and uses the character "#" followed by the <View id> of the linked item (e.g: src="#seg_poweroff")
- Links to a <View id> in another .xml file uses the localhost functions with the full path of the file followed by the character "#" and the <View id> of the linked item (e.g: src="xmb://localhost/dev_flash/vsh/resource/explore/xmb/category_user.xml#seg_poweroff")
Items contents (classes)
The contents of this sub group dictates what exists on the XMB when this entry is used. There can be more than one.
When creating a XMB entry, you must tell vsh.self and its modules what you want to do. And the first part of a <Items> sub-entry does just this by telling the PS3 the "class" of the entry in the form of either "<Item class=""" or "<Query class=""" (in the case of "<Query class=""" can be used several times under the same <items> to perform group of actions). There are many acceptable values possible, here are some examples:
Query classes x-xmb | <key> | <attr> | <src> | Remarks |
---|---|---|---|---|
<Query class="type:x-xmb/folder-pixmap" | Yes | Opt | Yes | Has many uses see here |
<Query class="type:x-xmb/xmlmcutility" | Yes | Yes | Yes | PS1 and PS2 virtual memory card utility |
<Query class="type:x-xmb/xmlpackagefolder" | Yes | No | Yes | Used for installing package files |
<Query class="type:x-xmb/xmlpsp2appdata" | Yes | Yes | No | PSVita application utility |
<Query class="type:x-xmb/xmlsavedata-plus" | Yes | Yes | No | Online storage |
<Query class="type:x-xmb/xmlsavedata-ps2" | Yes | Yes | No | Savedata utility PS2 |
<Query class="type:x-xmb/xmlsavedata-ps3" | Yes | Yes | No | Savedata utility PS3 |
<Query class="type:x-xmb/xmlsavedata-psp" | Yes | Yes | No | Savedata utility PSP |
Item classes x-xmb | <key> | <attr> | <src> | Remarks |
<Item class="type:x-xmb/module-action" | Yes | Yes | No | Uses a particular module to support the XMB item. See VSH module-action page |
<Item class="type:x-xmb/vmc-new" | Yes | Yes | No | |
<Item class="type:x-xmb/xmlbddatamgmt" | Yes | Yes | No | |
<Item class="type:x-xmb/xmleditingvideo" | Yes | Yes | No | |
<Item class="type:x-xmb/xmlgameexit" | Yes | No | No | |
<Item class="type:x-xmb/xmlhakoniwa" | Yes | Yes | No | |
<Item class="type:x-xmb/xmliboard" | Yes | Yes | No | Used in Widgets |
<Item class="type:x-xmb/xmlmessagelist" | Yes | Yes | No | |
<Item class="type:x-xmb/xmlnowplaying" | Yes | Yes | No | |
<Item class="type:x-xmb/xmlnpsignup" | Yes | Yes | No | |
<Item class="type:x-xmb/xmlplaylist" | Yes | Yes | No | |
<Item class="type:x-xmb/xmlplus" | Yes | No | No | |
<Item class="type:x-xmb/xmlpoweroff" | Yes | No | No | |
<Item class="type:x-xmb/xmlpremo" | Yes | No | No | |
<Item class="type:x-xmb/xmlpsp2appdata-cont" | Yes | Yes | No | PSVita Applications (PSVita, PSP, PS1, PSMobile) |
<Item class="type:x-xmb/xmlscreenshot" | Yes | No | No | |
<Item class="type:x-xmb/xmlsysconf" | Yes | Yes | No | |
<Item class="type:x-xmb/xmltrophy" | Yes | Yes | No | |
<Item class="type:x-xmb/xmlwebbrowser" | Yes | Yes | No | |
<Item class="type:x-xmb/xmlwelcome" | Yes | Yes | No | |
Item classes x-chat | <key> | <attr> | <src> | Remarks |
<Item class="type:x-chat/xmlchatroom-manager" | Yes | Yes | No |
- <key>
- Used to identify the sub-entry inside <Items> tables (usually the same value as <attr> and the <Table key> associated if present)
- Example: key="my_icon"
- <attr>
- Used to link <Items> to a table of attributes with the same name <Table key> inside <Attributes>
- Example: attr="my_icon_metadata"
- <src>
- Used to link to other xml files or utilise a XMB database functions (see XMB database)
- Refer to another XMB entry inside the current xml file. Example: src="#seg_package_files"
- Refer to another XMB entry inside another xml file. Example: src="xmb://localhost/dev_flash/vsh/resource/explore/xmb/category_game_tool2.xml#seg_package_files"
- Use a XMB database function. Example: src="xcb://localhost/query?table=MMS_MEDIA_TYPE_SYSTEM&genre=Music&sort=+StorageMedia:Common.titleForSort&cond=Ae+StorageMedia:StorageMedia.type %xCB_MEDIA_TYPE_DLNA"
Attributes contents (pair keys)
This provides additional information about <Items> sub-entries by linking them to a table with attributes associated (is optionall, not all <Items> requires attributes), this tables uses a < Table key> matching the <attr> sub-entry asociated and contains one or more attributes separated in lines starting with <Pair key>.
Attribute | Query classes x-xmb | Item classes x-xmb | Item classes x-chat | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
folder-pixmap | xmlmcutility | xmlpackagefolder | xmlsavedata-ps3 | xmlsavedata-psp | module-action | vmc-new | xmlbddatamgmt | xmleditingvideo | xmlgameexit | xmlhakoniwa | xmliboard | xmlmessagelist | xmlnowplaying | xmlnpsignup | xmlplaylist | xmlpoweroff | xmlpremo | xmlscreenshot | xmlsysconf | xmltrophy | xmlwebbrowser | xmlwelcome | xmlchatroom-manager | |
action | Yes | Yes | ? | Yes | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
bar_action | No | ? | No | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
cf_connection | ? | ? | ? | Yes | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
ch_pos | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
child | Yes | ? | Yes | ? | ? | No | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
content_id | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? |
content_info_pict | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? |
content_info_pict_sd | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? |
content_info_tex | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? |
content_info_title | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? |
content_info_title_sd | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? |
content_name | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? |
content_type | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? |
custom_priority | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
data_connection | ? | ? | ? | Yes | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? |
fo_lbl2_alpha | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
focus | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? |
focus_detect | Yes | ? | Yes | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
focus_priority | Yes | ? | Yes | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
fs_path | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
icon | Yes | ? | Yes | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
icon_notation | Yes | ? | Yes | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
icon_rsc | Yes | ? | Yes | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
id | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? |
info | Yes | ? | Yes | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? |
info_rsc | Yes | ? | Yes | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
ingame | Yes | ? | Yes | ? | ? | No | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
instruction_rsc | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? |
item_type | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
lbl_half | No | ? | No | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
mass_connection | ? | ? | ? | Yes | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
mode | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? |
module_action | No | ? | No | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
module_name | No | ? | No | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
ms_connection | ? | ? | ? | Yes | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
path | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? |
pkg_src | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? |
prod_pic_path | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? |
sd_connection | ? | ? | ? | Yes | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
start_factory_play | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
str_noitem | Yes | ? | No | ? | ? | No | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
title | Yes | ? | Yes | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
title_fo | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
title_rsc | Yes | ? | Yes | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
type | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? |
vmc | ? | Yes | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
action. Example: "exec_game", "exec_vmcsavedata", "exec_ps3savedata", "exec_pspsavedata"
bar_action Example: "none"
cf_connection. Example: xcb://localhost/query?... (too long for wiki)
ch_pos. Example: "1"
child Use: tells the PS3 what action should be taken when the XMB item is selected. Example: "segment"
content_id. Example: IP9100-NPIA00002_00-0000111122223333
content_info_pict. Example: /dev_flash/vsh/resource/explore/icon/pstex01.png
content_info_pict_sd. Example: /dev_flash/vsh/resource/explore/icon/pstex-sd.png
content_info_text. Example: msg_ps3_portal
content_info_title. Example: msg_psstore_explanation_hd
content_info_title_sd. Example: msg_psstore_explanation_sd
content_name. Example: "msg_title_lwp", "msg_information_board"
content_type. Example: game
custom_priority. Example: "game=-80", "video=-80"
data_connection. Example: xcb://localhost/query?... (too long for wiki)
fo_lbl2_alpha. Example: "0"
focus. Example: last
focus_detect Use: tells the PS3 to focus on the item if it is activated/utilised (like inserting a PS3 game disc). Of course the vsh.self has the final say on whether it is used (turning off auto boot). Example: "enable"
focus_priority Use: tells the PS3 the order in which the XMB items are loaded. This is use more by XMB items on the root of the XMB. Example: any integer
fs_path. Example: "/dev_hdd0/widget/npdrm/informationboard"
icon Use: displays a .png image from an absolute path as XMB icon. Cannot be used at the same time as 'icon_rsc'. Example: "/dev_hdd0/myicon.png"
icon_notation Use: tells the XMB how to treat the icon (transparency etc.) by refering to the relevant .rco. Can in some cases override 'icon' or 'icon_rsc'. Example: "WNT_XmbItemSavePS3"
icon_rsc Use: displays a .rco referable image as XMB icon. Cannot be used at the same time as 'icon'. Example: "tex_album_icon"
id. Example:
info Use: displays XMB title information from plain text input. This is shown below the 'title' or 'title_rsc' entry ins a smaller font. Cannot be used at the same time as 'info_rsc'. Example: "This is a cool plain text info string", "net_package_install_with_eula"
info_rsc Use: displays XMB title information from relevant .rco. This is shown below the 'title' or 'title_rsc' entry ins a smaller font. Cannot be used at the same time as 'info'. Example: "item_tex_cam_icon"
ingame Use: tells the PS3 if the item can be accessed ingame. Example: "enable"/"disable"
instruction_rsc. Example: msg_lwp_explanation
item_type. Example: "systop"
lbl_half Example: "1"
mass_connection. Example: xcb://localhost/query?... (too long for wiki)
mode. Example: playlistmgmt
module_action Use: what the module is commanded to use. The example commands are in respect the above modules. Example: "http://m.facebook.com"/"NotifyErrorNoExecute"
module_name Use: the name of the module to be used from this list. Example: "webbrowser_plugin"/"explore_plugin"
ms_connection. Example: xcb://localhost/query?... (too long for wiki)
path. Example:
pkg_src. Example: http://dL-REGION01.ps3.download.playstation.net/download/ps3/L-REGION/lwp/lwp.pkg
prod_pict_path. Example: "/dev_flash/vsh/resource/explore/icon/fah-xmb.png", "/dev_hdd0/widget/npdrm/informationboard/Icon.png"
sd_connection. Example: xcb://localhost/query?... (too long for wiki)
start_factor_play. Example: disable
str_noitem Use: displays information from relevant .rco when no data/XMB items are found from then search function of the current XMB item. Example: "msg_error_no_gamedata"
title Use: displays XMB main title from plain text input. Cannot be used at the same time as 'title_rsc'. Example: "Debug Settings"
title_fo. Example: 1
title_rsc Use: displays XMB main title text referred from relevant .rco. Cannot be used at the same time as 'title'. Example: "msg_tool_app_home_ps3_game"
type. Example: "photo", "music"
vmc. Example: promote
Examples
An XMB item tree
For this we will make a XMB item which will act as a folder opening up into 3 other XMB items.
1/ First create the root XMB item which acts as a folder
Code Sample
Important Notes:
- I've used "<Query class="type:x-xmb/folder-pixmap"" for <Items> sub-entry type as it is good for displaying menus.
- The 'attr' in the <Items> sub-entry (xmb_folder) is the same as the table key in Attibutes, so those attributes are assigned to the xmb_folder <Items> sub-entry.
- the 'src' is pointing to 'XMB_Folder_1_container' - the another XMB .xml entry in the current .xml
- the icon is from a .rco file and is a basic folder icon, like what the 'Game Data' XMB item uses
- 'title' and 'info' are in plain text
- 'child' is set as 'segment' so the XMB knows this item will subdivide into other XMB items
In order to create a working XMB sub menu the root xmb item (in this "XMB_Folder_1") must have its 'src' linking to a "container" (its the best way to think about it) and not directly linking to XMB items in the sub menu.( If you do not do this when you select your root XMB item to display a sub menu, the 'output' or 'action' of the XMB items of the sub menu will be shown rather than the actual XMB items):
Code Sample
Important Notes:
- This has no attributes as it simply acts as a contents container/linker
Now to create the XMB .xml entry which holds the sub menu items:
Code Sample
Important Notes:
- These are dummy items, they do not 'go anywhere' or perform any function. They will just print the str_noitem message when clicked because they have no function
- notice how the <attr> from the <Items> sub entries matches the <Table keys> from the <Attributes> sub entries
- The <Attributes> and the <Items> sub entries do not have to be in the same order to work
A Web-Site link
This type of entry could be placed on the root of the XMB category, or in an XMB Item Tree. This is also an application of the 'module-action' function. Example:
Code Sample
- Important Notes:
- The 'Attributes' for this Web-Link follows the Attribute rules for a 'module-action' entry.
- The 'webbrowser_plugin' module has been used to handle the request in the 'module_action' pair key, which is a web address
- The 'attr' in the Items sub-entry is the same as the table key in the 'Attributes' sub-entry.
- Remember that the icon_rsc string will search the rco file(used by the module running the category which this web link is on) for the icon 'dev_wiki_icon'. Whereas the title and info strings will just print the contents of the string.