Hi!

There a lot of kitchens avaialable for ROM building. Now this one is to ease TouchFlo3D building.

This kitchen uses the knowledge and works of 6Fg8, D-MAN666, xboxmod, chainfire and many others who are involved in Manila hacking.

If you use this kitchen and/or any of the decompiled scripts then be so kind and share back the source code of your modified scripts too!

This kitchen (v1.5) has the following utilities included:

• 6Fg8's mode 9 editor (v3.3.0.1)
• sztupy's mode9 converter (v1.0)
• chainfire's CFC compressor (v0.46)
• MKT: a tool for batch converting/compressing/compiling mode9,qtc,png,xml,lua files (v1.1)
• LuaDec (2.0)
• A work in progress lua and xml IDE
• And various other tools

• split hased _manila files back to their original filenames
• join a bunch of files in a directory back to their hashed form
• mass decompile mode9 files back to xml and save their lua scripts
• mass convert qtc files to/from png files
• mass compile lua files

mkt split

to split the hashed files back into their filenames. (For this conversion it uses the same table as m9editor uses.)

You will get a "bin" directory. This will hold all "compiled" stuff, so here you will find all the files that don't need more preprocessing, and can be hashed/installed to the device

Next you want to get some editable files out from the luac, mode9 and qtc files, so use:

mkt -x bin frommode9

To decompile mode9 files back to XML (it will also extract the scripts out of the package)

Next:

mkt -c d,qp fromqtc
or
mkt fromqtc

Will convert all qtc files to png files. (the first type will work on cfc compressed qtc files, the second will work on non cfc compressed files)

After this only the scripts are remaining. Unfortunately these can't be decompiled easily, so grap the decompilation of someone (like me ), and put these files into the "insrc" directory. After this run

mkt -d insrc -o src split

so all the hashed _manila files will be converted back to their original filenames to ease searching through them.

After this you're ready with your prepared kitchen. These things were already done with the Rhodium manila so you might use that package to start manila modding.

Compiling

You can use tomode9, compile and toqtc commands to compile these files back to their binary counterpart. Alternatively you can use:

mkt -c pq,c,p make

to run this three command after each other. It's like a Makefile, so it will only compile things that have changed. Of course you might want to 'make all':

mkt -a -c pq,c,p make

This will build all files from the "src" directory into the "bin" directory

Creating the package
After you're done you can use

mkt -o outdir join

to hash all files from the bin directory back to hashed form, and put it into the 'outdir' directory. Next add the binaries and you're ready to flash

Alternatively I included createpkg that will create a cab package from the OEM apckage found in the 'pkg' directory

Download and other stuff: http://winmo.sztupy.hu/manilakitchen.html

Sounds great! Downloading now. Thanks sztupy!

Yeah, good job sztupy, this will be a great addition.

nice...gotta buy a bigger house...so many kitchens

Originally Posted by pcarvalho  

nice...gotta buy a bigger house...so many kitchens :d

roflcopter

Originally Posted by pcarvalho  

nice...gotta buy a bigger house...so many kitchens

what you need is a microwave :P

Originally Posted by sztupy  

Missing functionality / bugs:

• Embedded decompiled scripts can't be re-embedded into mode9 files automatically (this would need a command line mode9 editor

I can help you out with that. Not that it's already done but copying the relevant parts from m9editor together isnt the big deal.

Originally Posted by 6Fg8  

I can help you out with that. Not that it's already done but copying the relevant parts from m9editor together isnt the big deal.

I hoped so

unfortunately it's hard to tell a command line tool where to inject the scripts... An XML export/import function would be cool (export it to XML, without the binary scripts, then add the decomp'd scripts, and the importer would do its job esolving everything), but I know that won't be possible until you resolve the mode9 files completely...

Originally Posted by sztupy  

I hoped so

unfortunately it's hard to tell a command line tool where to inject the scripts... An XML export/import function would be cool (export it to XML, without the binary scripts, then add the decomp'd scripts, and the importer would do its job esolving everything), but I know that won't be possible until you resolve the mode9 files completely...

hm, didnt do much with xml, but i think i can figure that out. mode9 is almost done, there's only one bytegrave at the end of a mode9 file still unknown to me.

Originally Posted by 6Fg8  

hm, didnt do much with xml, but i think i can figure that out. mode9 is almost done, there's only one bytegrave at the end of a mode9 file still unknown to me.

your visualization of the m9 files look like xml, that's why I thought about that (but yaml could be a good serializator too). But this is just an idea, if you can tel me an easy way to tell a command line script where to inject a script that would be fine

And a command line CFC compressor is also needed