XMB Integrated File Manager - (Constantly Work-In-Progress / Proof-Of-Concept)

[ps3hen]

From what I have found(in relation to the XMB):

VSH.self loads (among other things) -> a series of (but not all) modules (.sprx) and associated .rco files.
->some of these modules are responsible for specific XMB categories, such as the "explore_category_game.sprx". These (as I call them) XMB Category Modules, are programed to read and interpret XMB .xml files. Each XMB Category Module has a list of "functions" it can support, for example the famous "x-xcb/game-debug" used by Jailbroken/Debug PS3s to run game backups from HDD. Here is .xml code for utilising it:

	<View id="seg_gamedebug">
		<Attributes>
			<Table key="game_debug">
				<Pair key="icon_rsc"><String>tex_album_icon</String></Pair>
				<Pair key="title_rsc"><String>msg_tool_app_home_ps3_game</String></Pair>
				<Pair key="child"><String>segment</String></Pair>
			</Table>
		</Attributes>
		<Items>
			<Query class="type:x-xcb/game-debug" key="game_debug"  attr="game_debug" />
		</Items>
	</View>

If the module receives a function from the .xml that it doesn't understand, that XMB item never loads as the module doesn't know what to do with it. This can create issues for XMB mods, because it limits certain types of functions to certain categories, this is why you can't have "debug settings" in the game category.

But here comes the interesting bit. There are a number of modules and associated .rco files, which aren't directly loaded by the VSH because they are made to be used on demand by the VSH and it's modules. If you have looked though some of the VSH modules you'll notice references like "explore_plugin" which may seem odd, as they don't contain a file extension or file path. This is because they are sending commands to another module to do a task. These "on-demand" modules are indexed by the xmb_plugin.sprx module. Take a look:

Module Reference	Associated .rco Filepath	Module Filepath
playlist_plugin	/dev_flash/vsh/resource/playlist_plugin.rco	/dev_flash/vsh/module/playlist_plugin.sprx
scenefolder_plugin	/dev_flash/vsh/resource/scenefolder_plugin.rco	/dev_flash/vsh/module/scenefolder_plugin.sprx
system_plugin	N/A	N/A
xmb_plugin	N/A	N/A
explore_plugin	/dev_flash/vsh/resource/explore_plugin_full.rco	/dev_flash/vsh/module/explore_plugin.sprx
game_plugin	/dev_flash/vsh/resource/game_plugin.rco	/dev_flash/vsh/module/basic_plugins.sprx
np_trophy_ingame	/dev_flash/vsh/resource/np_trophy_ingame.rco	/dev_flash/vsh/module/np_trophy_ingame.sprx
gamedata_plugin	/dev_flash/vsh/resource/gamedata_plugin.rco	/dev_flash/vsh/module/gamedata_plugin.sprx
game_ext_plugin	/dev_flash/vsh/resource/game_ext_plugin.rco	/dev_flash/vsh/module/game_ext_plugin.sprx
premo_plugin	/dev_flash/vsh/resource/premo_plugin.rco	/dev_flash/vsh/module/premo_plugin.sprx
micon_lock_plugin	N/A	/dev_flash/vsh/module/micon_lock_plugin.sprx
category_setting_plugin	/dev_flash/vsh/resource/category_setting_plugin.rco	/dev_flash/vsh/module/category_setting_plugin.sprx
sysconf_plugin	/dev_flash/vsh/resource/sysconf_plugin.rco	/dev_flash/vsh/module/sysconf_plugin.sprx
netconf_plugin	/dev_flash/vsh/resource/netconf_plugin.rco	/dev_flash/vsh/module/netconf_plugin.sprx
software_update_plugin	/dev_flash/vsh/resource/software_update_plugin.rco	/dev_flash/vsh/module/software_update_plugin.sprx
bdp_plugin	/dev_flash/vsh/resource/bdp_plugin.rco	/dev_flash/vsh/module/bdp_plugin.sprx
bdp_disccheck_plugin	/dev_flash/vsh/resource/bdp_disccheck_plugin.rco	/dev_flash/vsh/module/bdp_disccheck_plugin.sprx
bdp_storage_plugin	/dev_flash/vsh/resource/bdp_storage_plugin.rco	/dev_flash/vsh/module/bdp_storage_plugin.sprx
user_plugin	/dev_flash/vsh/resource/user_plugin.rco	/dev_flash/vsh/module/user_plugin.sprx
friendim_plugin	N/A	/dev_flash/vsh/module/friendim_plugin.sprx
friendml_plugin	/dev_flash/vsh/resource/friendml_plugin.rco	/dev_flash/vsh/module/friendml_plugin.sprx
friendtrophy_plugin	/dev_flash/vsh/resource/friendtrophy_plugin.rco	/dev_flash/vsh/module/friendtrophy_plugin.sprx
profile_plugin	/dev_flash/vsh/resource/profile_plugin.rco	/dev_flash/vsh/module/profile_plugin.sprx
photoviewer_plugin	/dev_flash/vsh/resource/photoviewer_plugin.rco	/dev_flash/vsh/module/photoviewer_plugin.sprx
videoplayer_plugin	/dev_flash/vsh/resource/videoplayer_plugin.rco	/dev_flash/vsh/module/videoplayer_plugin.sprx
webbrowser_plugin	/dev_flash/vsh/resource/webbrowser_plugin.rco	/dev_flash/vsh/module/webbrowser_plugin.sprx
webrender_plugin	/dev_flash/vsh/resource/webrender_plugin.rco	/dev_flash/vsh/module/webrender_plugin.sprx
xai_plugin	/dev_flash/vsh/resource/xai_plugin.rco	/dev_flash/vsh/module/xai_plugin.sprx
audioplayer_plugin	/dev_flash/vsh/resource/audioplayer_plugin.rco	/dev_flash/vsh/module/audioplayer_plugin.sprx
videodownloader_plugin	/dev_flash/vsh/resource/videodownloader_plugin.rco	/dev_flash/vsh/module/videodownloader_plugin.sprx
nas_plugin	/dev_flash/vsh/resource/nas_plugin.rco	/dev_flash/vsh/module/nas_plugin.sprx
download_plugin	/dev_flash/vsh/resource/download_plugin.rco	/dev_flash/vsh/module/download_plugin.sprx
ps3_savedata_plugin	/dev_flash/vsh/resource/ps3_savedata_plugin.rco	/dev_flash/vsh/module/ps3_savedata_plugin.sprx
vmc_savedata_plugin	/dev_flash/vsh/resource/vmc_savedata_plugin.rco.	/dev_flash/vsh/module/vmc_savedata_plugin.sprx
thumthum_plugin	/dev_flash/vsh/resource/thumthum_plugin.rco	/dev_flash/vsh/module/thumthum_plugin.sprx
npsignin_plugin	/dev_flash/vsh/resource/npsignin_plugin.rco	/dev_flash/vsh/module/npsignin_plugin.sprx.
avc_plugin	/dev_flash/vsh/resource/avc_plugin.rco	/dev_flash/vsh/module/avc_plugin.sprx
avc2_text_plugin	/dev_flash/vsh/resource/avc2_text_plugin.rco	/dev_flash/vsh/module/avc2_text_plugin.sprx
sacd_plugin	/dev_flash/vsh/resource/sacd_plugin.rco	/dev_flash/vsh/module/sacd_plugin.sprx
eula_cddb_plugin	/dev_flash/vsh/resource/eula_cddb_plugin.rco	/dev_flash/vsh/module/eula_cddb_plugin.sprx
strviewer_plugin	/dev_flash/vsh/resource/strviewer_plugin.rco.	/dev_flash/vsh/module/strviewer_plugin.sprx
edy_plugin	/dev_flash/vsh/resource/edy_plugin.rco	/dev_flash/vsh/module/edy_plugin.sprx
print_plugin	/dev_flash/vsh/resource/print_plugin.rco	/dev_flash/vsh/module/print_plugin.sprx
newstore_plugin	/dev_flash/vsh/resource/newstore_plugin.rco	/dev_flash/vsh/module/newstore_plugin.sprx
deviceconf_plugin	/dev_flash/vsh/resource/deviceconf_plugin.rco	/dev_flash/vsh/module/deviceconf_plugin.sprx
dlna_plugin	/dev_flash/vsh/resource/dlna_plugin.rco	/dev_flash/vsh/module/dlna_plugin.sprx
np_trophy_plugin	/dev_flash/vsh/resource/np_trophy_plugin.rco	/dev_flash/vsh/module/np_trophy_plugin.sprx
kensaku_plugin	/dev_flash/vsh/resource/kensaku_plugin.rco	/dev_flash/vsh/module/kensaku_plugin.sprx
regcam_plugin	/dev_flash/vsh/resource/regcam_plugin.rco	/dev_flash/vsh/module/regcam_plugin.sprx
idle_plugin	/dev_flash/vsh/resource/idle_plugin.rco	/dev_flash/vsh/module/idle_plugin.sprx
filecopy_plugin	/dev_flash/vsh/resource/filecopy_plugin.rco	/dev_flash/vsh/module/filecopy_plugin.sprx
wboard_plugin	/dev_flash/vsh/resource/wboard_plugin.rco	/dev_flash/vsh/module/wboard_plugin.sprx
checker_plugin	/dev_flash/vsh/resource/checker_plugin.rco	/dev_flash/vsh/module/checker_plugin.sprx
hknw_plugin	/dev_flash/vsh/resource/hknw_plugin.rco	/dev_flash/vsh/module/hknw_plugin.sprx
poweroff_plugin	/dev_flash/vsh/resource/poweroff_plugin.rco	/dev_flash/vsh/module/poweroff_plugin.sprx
eula_hcopy_plugin	/dev_flash/vsh/resource/eula_hcopy_plugin.rco	/dev_flash/vsh/module/eula_hcopy_plugin.sprx
videoeditor_plugin	/dev_flash/vsh/resource/videoeditor_plugin.rco	/dev_flash/vsh/module/videoeditor_plugin.sprx

It's a big list I know, but what's important is that the ability to send commands to these modules is extended to .XML files with the function "x-xmb/module-action", and that function is available for every category. You may remember that we already use this with website links using the "webbrowser_plugin" module. And there are quite a few interesting modules which we should look into, such as the "filecopy_plugin", "download_plugin" and "nas_plugin" modules to name a few. We could have a proper pkg downloader, or file coping abilities. This also gives the potential to create our own modules, imagine a SELF loader module, which would load the ps1 emulator, you could play PS1 CD-R backups from the XMB.

Also you may recognise the "explore_plugin" being used many times throughout the OFW .xml files, that is because that is how Sony locks the XMB in Kiosk FWs. The majority of kiosk XMB restrictions involve using parts of .XML files that contain XMB items which look like real XMB items but are actually commands to send to the explore_plugin to display the "Cannot be used in demonstration mode" message when clicked on.

Also the found in the XMB Modules is a list of acceptable "terms" useable in .XML files:

View id
Items
Item
Query
key
class
attr
src
type:
clsid:
Attributes
Table key
include
Pair key
String
GET

Some things we haven't seen before huh.

[aldostools]

removed post

[dragoangel]

Hey Gays you saw that now every body can use hes CEX console in DEX mode (full Debug)

[ps3hen]

Added Samson's Webtools and Webradio XMBM+ additions to the GIT

[XiorgON]

@XMBM TEAM

I have i new idea again !!

Is to reintegrate a basic option that have dissapear from the Rebug Package manager to XMBM+

This option is - Install ALL pkg on selected device !!

what to you think is a good idea to reintegrate it ??

OTHER SUBJECT:

If a CFW 3.60 Arrive do you think it will be easy to convert XMBM+ 3.55 to 3.60 ??

[aldostools]

removed post

[sandungas]

From what I have found (in relation to the XMB)...

Ps3hen, thanks for this new page you did in the wiki, keep the good work
http://www.ps3devwiki.com/wiki/XMB_XML_Coding

Now i see this page was completly needed... is like the "main page" related with XMB XML's... (the others andreus wrote are dependant of yours... is good if you make links between all them)
You have also the "discussion" pages... can be used to take notes... or speculation like a shared workplace.... the info can be moved later when verifyed to the main page

There are anothers .XML's btw... inside .rco's
RCOmage represents the extracted "info" files as .XML's.... but internally (inside the .RCO) im not sure if are XML's (probably are not)
Either way... this is not 100% accurate, but i think its needed some explain of them
Yesterday i thought maybe is needed another page "RCO_XML_Coding"... but by now i have nothing to add (im still learning, and this new page you wrote helped a lot)... maybe a section in your page is enought... or some data added to the tables... dont worry by now, not much important

But this info texts inside RCO's are usefull to identify the functions availables for each module (SPRX) or to know how works
I will help to edit this pages (yours and andreus) later, thanks again

[ps3hen]

Ps3hen, thanks for this new page you did in the wiki, keep the good work
http://www.ps3devwiki.com/wiki/XMB_XML_Coding

Now i see this page was completly needed... is like the "main page" related with XMB XML's... (the others andreus wrote are dependant of yours... is good if you make links between all them)
You have also the "discussion" pages... can be used to take notes... or speculation like a shared workplace.... the info can be moved later when verifyed to the main page

There are anothers .XML's btw... inside .rco's
RCOmage represents the extracted "info" files as .XML's.... but internally (inside the .RCO) im not sure if are XML's (probably are not)
Either way... this is not 100% accurate, but i think its needed some explain of them
Yesterday i thought maybe is needed another page "RCO_XML_Coding"... but by now i have nothing to add (im still learning, and this new page you wrote helped a lot)... maybe a section in your page is enought... or some data added to the tables... dont worry by now, not much important

But this info texts inside RCO's are usefull to identify the functions availables for each module (SPRX) or to know how works
I will help to edit this pages (yours and andreus) later, thanks again

Well it's not finished yet, I had a draft I wrote a while ago for the wiki sitting on my hdd. I plan(ed) to add more examples, and instructions/methods to use XML code outside of the dev_flash. But with the 3.55 CEX module intercom list, I thought I had enough to put on the wiki for now. Hopefully with the progress of time, it becomes more comprehensive. I also plan to link the XMBM+ SDK on the page, as it simplifies greatly, external XMB XML code setup process.

[sandungas]

Well it's not finished yet, I had a draft I wrote a while ago for the wiki sitting on my hdd. I plan(ed) to add more examples, and instructions/methods to use XML code outside of the dev_flash. But with the 3.55 CEX module intercom list, I thought I had enough to put on the wiki for now. Hopefully with the progress of time, it becomes more comprehensive. I also plan to link the XMBM+ SDK on the page, as it simplifies greatly, external XMB XML code setup process.

Even if is not very detailed... this was very usefull to understand the basic structure, and as i said before, you can use the "talk" pages like a "shared noteblock" to write speculations, brainstorming or whatever (i did in ohter pages... sometimes is the only way to document a bit something that is unknown)... the only thing that needs to be taken in consideration is to mark this notes with an "unknown" "speculation" or whatever (are temporal notes that needs to be moved or erased later)

I like this table with the relationship with modules ---> http://www.ps3devwiki.com/wiki/XMB_X...#Module-Action
Do you mind if i order the rows alphabetically ? (for me is much more intuitive when comparing this table with the files in pc... both ordered alphabetically)
And this table can be expanded with more info (if not this table... other like this one with the complete list)
-It can be added a column for "FIRMWARE" (this ones you listed are fro 3.55... but modules was added in different firmwares)
-Another column for the "XMB messages" related with this module (contained in the ENGLISH.xml inside .rco's)... this is an "easy" way to identify the functions of each modules

Also... i see a "problem"... the table actually contains the same names in the columns e.g:

playlist_plugin                 /dev_flash/vsh/resource/playlist_plugin.rco                      /dev_flash/vsh/module/playlist_plugin.sprx

What changes is the path and the file extension... (the name is the same), and the path and file extension is common for all the others rows (what changes in other rows is the name)... so hmmm, seems not the better way to make this table small, but right now i dont see a simple way to reduce his size

[ps3hen]

@sandungas:
"Even if is not very detailed... this was very usefull to understand the basic structure, and as i said before, you can use the "talk" pages like a "shared noteblock" to write speculations, brainstorming or whatever (i did in ohter pages... sometimes is the only way to document a bit something that is unknown)... the only thing that needs to be taken in consideration is to mark this notes with an "unknown" "speculation" or whatever (are temporal notes that needs to be moved or erased later)" I'm glad someone is finding it useful.

"I like this table with the relationship with modules ---> http://www.ps3devwiki.com/wiki/XMB_X...#Module-Action
Do you mind if i order the rows alphabetically ? (for me is much more intuitive when comparing this table with the files in pc... both ordered alphabetically)" You can if you think it will make it more useful. But FYI, the order you see is the same as in the XMB_Plugin.sprx.

"-It can be added a column for "FIRMWARE" (this ones you listed are fro 3.55... but modules was added in different firmwares)" That's a good idea. Perhaps having another column for DEX firmware might be relevant, now users can install DEX firmwares.

"-Another column for the "XMB messages" related with this module (contained in the ENGLISH.xml inside .rco's)... this is an "easy" way to identify the functions of each modules" I think that would need another page IMO

"Also... i see a "problem"..." No that's not a problem. Think of it like this, the XML file calls plugin "X" and the XMB_Plugin.sprx maps "X" to "X.sprx" and "X.rco". Most of the time the module reference has the same name(as the .sprx and .rco), but not always, there are some cases where they are different.