Quote:
Originally Posted by m-land
Really nice work! I have a question: from where you know what is possible in XML files/how to create them? I'm trying to find some clue how to use all these style, cutout and so on stuff...
|
Hi, m-land!
Glad you like it.
But sorry to say that I did what you already wrote:
Quote:
Originally Posted by m-land
I have several questions regarding PRS+ developement. I'm able to find some information reading PRS+ sources, but....
XML file items. Is somewhere documentation of this file content? OK, I can simply 'modify' some working XML but most probably I'll never find a lot of stuff that could be done in XML.
script methods Is somewhere list/description of methods that are available? Once again I can go current .js files one by one but for sure there is much more methods available...
|
As I wrote in the starting post, i haven't found the philosopher's stone to FSK, instead I just read, and re-read and search all available code, guessed, made assumptions and tried and tried again. (See the crippled code in DictoLauncher, and guess why there is this KILL-FSK.BAT
)
Valuable sources are especially the XML-Files in PRS-505 FSK.img (new_opt.img), the files in the Sony-Firmware-Updater and at least the Reader-Library Files.
Regarding methodes and properties, scan the "defsk-ed" *.xsb, *.xso and *.so files.
If you don't have it by now and can't finde Igorsk "deFsk0.2", as I can't find the link right in the moment, ask and I will post it for you.
What's possible in XML / JS can be found by try and error, or by using prs+ core dumpingcode "dumpToString" as integrated in the "dictionary.js"
If a, fully qualified methode dumps as "a function" you can call it form XML or JS, even if the parent object is dumped as "object with no propertys", if the dump says "undefined" we have bad luck and can't use the function directly.
But on the PRS-505 with PRS+ the way over soGetValue and calling the retrieved function should be possible.
I also din't start XML files form the scratch, but started to modify existing ones, with a plain code editor like JEdit (as recommended by kartu) or EditPadPro, which is used by me. Both are capable of saving the code in UTF-8, if configured correctly.
Regarding this style, skin and cutout-stuff, this all reminds me, the one and other way, to plain old HTML-coding. Examine the code of the games, play with it in this simulator, and see what happens.
I also found that assumptions often works well.
In the original updater code a <noGrowBorder> is defined.
In "connectAssets.xml" there is a style and skin "growBorder",so I simply tried the <growBorder> Tag and it works.