Editing Talk:PlayStation 3 Theme (P3T)



===Standarizing "theme format" names===
The standarization of theme names used in the front page can be polemic and initially confusing, but after some brainstorming i realized we need to keep the sony standards naming and at the same time think in another way to name the different methods used with animated themes, and here is where the confussion starts because "the scene" has been using names that are limited in long term for his possible derivations e.g: "slideshow" "pro slideshow" "dynamic pro slideshow", etc... (big mention here to glowball for his experiments, cheers)

The point is if you take a "dynamic pro slideshow" as base and add to it a new 3d sphere + more semitransparent layers + etc + etc this is a "dynamic pro slideshow multilayer with a 3d object, etc..." ?... well, it sounds supercool (ironic) for a resume, but not even this long name defines how has been created, to make a list we need the "method" or "technique" used.

The big difference (that keeps the standard naming) is static doesnt use an script.js, and dynamic does... we will have problems to give a name to the "methods" but i think this way to focus is better, any idea or suggestion is welcome --[[User:Sandungas|Sandungas]] 11:01, 14 February 2013 (MSK)

===Backgrounds linked to clock time===
*[http://rghost.net/59623568 PS3 Themes background testkit v1.zip]
A collection of themes using the background examples explained in front page, the zip contains several example themes xml's and 24 numbered backgrounds + 2 special backgrounds with the text "win" and "failsafe" in both 4:3 and 16:9 aspect ratios for a total of 52 backgrounds, this background are intented to create special events and collisions (feel free to add more examples to the .zip, upload again, and replace the link by "testkit v2", v3, etc...)

*Notes
To see an interesting example of how backgrounds are linked to the system clock, compile "Test 15bg to seconds.xml" theme, then install and "apply", and... press "x" button again over "apply" repeatedly as faster as possible (lol), you will see how the background numbers increases 1 by 1. Now wait 3 seconds and press "apply" again and the number in screen has increased in +3. This means every time the theme is applyed (or everytime the PS3 boots) is readed the system clock, and a background is choosen based in the seconds of the clock. This is also a way to make a theme with (semi) random backgrounds that will be selected based in the time when the PS3 was turned on.

===p3t format, p3tcompiler, and p3textractor notes===

{{Boxframe1|content=
'''p3tcompiler'''
*p3t format uses several tables to store the "standard names of the files" without file extension (original names and file extensions of the files used to build the theme are lost)
*backgrounds lost his file names,, instead of the original name of the file is used the "standard" name... either "hd" and "sd" for static themes... or "anim" for dynamic themes
*backgrounds are stored in a table in the same order that are placed in the original "Theme Name.xml". There is no conversion to this .jpg files, the start position of static backgrounds can be found by looking for "FF D8 FF E0 00 10 4A 46 49 46 00 01 02 01 00 48 00 48 00 00" in the .p3t file in a hexeditor
*The original name of the .xml is lost (there is no place to store it, just his tags in a table)
*The order of items and tables in the p3t file is fixed and always the same (with a few exceptions). The compiler reorders the items to his convenience
*Items in the p3t file that respect the original order of the xml are all contents of: <icontable>, <bgimagetable>, <pointertable> ?
*Compiler version 2.00 with dynamic background ouput unrecognized attribut name "anim" for dynamic background and fail to make the p3t, when the 1.80 compile it.

'''p3textractor'''
*rename problems
**"notification" image is renamed to "src"
**if the theme contains multiple backgrounds, extracted backgrounds are not renamed in the correct order using "hd_1", "sd_2" etc... (but are correctly ordered in the p3t)
**png filextensions are duplicated (in the extraction process is needed to convert images to .gim then to png, the resulting files are renamed to "file.gim.png")
**png and .gim filenames are numbered by adding a "_1" at the end, but is not needed (is only needed in the backgrounds when there are several of the same type)
**"Theme Name.p3t.xml" instead of "Theme Name.xml"
*xml problems
**the order or items inside <info> and <icontable> in the extracted xml is different than the one contained in the .p3t
}}

---

{{Boxframe5|content=
'''p3t format, standard order of tags after compilation''' (based in the tags stored in the xml table inside the .p3t file)
{{Boxcode|content=<syntaxhighlight lang="xml">
<infotable>
	<info>
		comment
		previewsize	<!-- added by the compiler -->
		name
		author
		url
		authoriconsize	<!-- added by the compiler -->
		authoricon
		iconsize	<!-- added by the compiler -->
		version
		mtime		<!-- added by the compiler -->
		genre
		preview
		icon
	<localizedinfo>
<icontable>
<pointertable>
<notification>
<setable>
<bgimagetable>
<font>
<color>
</syntaxhighlight>}}
}}

==Maximum number of installed themes==
 Inside game_ext_plugin.rco/english.xml
 <Text name="msg_error_install_theme_over_delete_other_theme">The maximum number of themes that can be installed has been reached.
 To install this theme, you must delete an existing theme.</Text>

==Preinstalled themes resources==
<Mugi> the ones in the RCO's are used by the classic theme

<Mugi> the default theme uses the DDS icons from icontex.qrc

<Mugi> looks like i was wrong, the classic theme doesnt' use the icosn from the RCO either

<Mugi> maybe sony changed it since the last time i toyed with this, no clue

<Mugi> im sure it did at some point

==Navigation sounds location in firmware==
Inside [[system_plugin]].rco

{{Boxcode|content=<syntaxhighlight lang="xml">
<!-- This XML representation of an RCO structure was generated by Rcomage v1.1.2 -->
<RcoFile UMDFlag="0" rcomageXmlVer="1.1" type="ps3" minFirmwareVer="unknownId0x130">
	<MainTree name="system_plugin">
		<ImageTree>
			...
			..
			.
		</ImageTree>
		<SoundTree>
			<Sound name="snd_cursor" src="snd_cursor.ch*.vag" format="vag" channels="2" />
			<Sound name="snd_decide" src="snd_decide.ch*.vag" format="vag" channels="2" />
			<Sound name="snd_cancel" src="snd_cancel.ch*.vag" format="vag" channels="2" />
			<Sound name="snd_category_decide" src="snd_category_decide.ch*.vag" format="vag" channels="2" />
			<Sound name="snd_option" src="snd_option.ch*.vag" format="vag" channels="2" />
			<Sound name="snd_error" src="snd_error.ch*.vag" format="vag" channels="2" />
			<Sound name="snd_system_ok" src="snd_system_ok.ch*.vag" format="vag" channels="2" />
			<Sound name="snd_system_ng" src="snd_system_ng.ch*.vag" format="vag" channels="2" />
			<Sound name="snd_trophy" src="snd_trophy.ch*.vag" format="vag" channels="1" />
		</SoundTree>
		<TextTree>
			...
			..
			.
		</TextTree>
		<ObjectTree>
			...
			..
			.
		</ObjectTree>
		<AnimTree>
			...
			..
			.
		</AnimTree>
	</MainTree>
</RcoFile>
</syntaxhighlight>}}

All them are 2 channels stereo (except trophy sound that is 1 channel mono), every channel is a separated file with its name ending in 0 or 1... (for mono 0 is both channels... and for stereo 0 is left and 1 right ?), the complete list of files extracted raw without conversion from the .rco are:
 snd_cancel.ch0.vag
 snd_cancel.ch1.vag
 snd_category_decide.ch0.vag
 snd_category_decide.ch1.vag
 snd_cursor.ch0.vag
 snd_cursor.ch1.vag
 snd_decide.ch0.vag
 snd_decide.ch1.vag
 snd_error.ch0.vag
 snd_error.ch1.vag
 snd_option.ch0.vag
 snd_option.ch1.vag
 snd_system_ng.ch0.vag
 snd_system_ng.ch1.vag
 snd_system_ok.ch0.vag
 snd_system_ok.ch1.vag
 snd_trophy.ch0.vag

Only 5 of them can be remapped from an official theme
{{Boxcode|content=<syntaxhighlight lang="xml">
<theme>
<!-- Navigation sounds ------------------------------------------------------------------------------->
	<setable>
		<se id="se_cursor" 			src="se_cursor.vag"/>		<!-- Cursor movements: left, right, up, down -->
		<se id="se_optionmenu" 			src="se_optionmenu.vag"/>	<!-- Open/enter a options menu -->
		<se id="se_cancel" 			src="se_cancel.vag"/>		<!-- Close/exit a options menu -->
		<se id="se_decide" 			src="se_decide.vag"/>		<!-- Question -->
		<se id="se_system_ok" 			src="se_system_ok.vag"/>	<!-- Accept -->
	</setable>
</theme>
</syntaxhighlight>}}