[Windows Mobile Software Development] Co0kieMonster:
I'm hoping this will be helpful to anyone looking to modify Manila.

Manila 2.5 has all new file paths so the file lists from older versions don't apply. I searched the forums but couldn't find any info on new file names, so I decided to try to put together a new list and this is the result.

This should be a solid base, and I hope that we can build up from here. Anyone who finds new file names please post your findings so we can get a more complete general reference as well as keep it up to date in case of any later changes to Manila.

[APP] Manila Name Finder:

This started out as just some scripts to help me search for names, but has evolved into a proper little program. It can search decompiled mode9 and lua scripts for manila names as well as reconstruct names from localization xmls.

It's not really the most user friendly thing, but it works. The included ReadMe.txt has some basic instructions for use. This tool is also included as part of this Manila Kitchen and that really is the best and easiest way to use it.

I'm also posting the source code. If a future version of Manila breaks the naming scheme again like Manila 2.5, this finder will need to be updated. I'll probably update it but in case I'm MIA someone will hopefully find this source code useful.

Download:

Manila Name Finder v1.0

MNF v1.0 source code (C++)

[REFERENCE] NAME LISTS: Manila 2.5 and 2.1: (a bit outdate right now - will update soon)

You can just paste the lists into m9editor's m9editor.names.txt to get the manila names displayed in m9editor or any manila kitchen which uses on the same m9editor.names.txt for manila names.

Note: Only the file list in the lower left corner of m9editor is affected by adding the new names to the list. The hashed names that appear when you mouse over a file in the editor window aren't affected by this. See the guide below to learn how to get hashed manila names from mode9 files.

Current status of Manila 2.5 list (stats based on Manila 2.5 from Duttys Leo R1 ROM)

mode9: 69 of 69 ....100.00%
luac: 297 of 318 .....93.39%
qtc: 925 of 1216 .....76.06%
xml: 1220 of 1239 .....98.46%

Current status of Manila 2.1 list (stats based on Manila 2.1.38680)

mode9: 51 of 51 ....100.00%
luac: 225 of 234 .....96.15%
qtc: 711 of 813 .....87.45%
xml: 1076 of 1081 .....99.57%

Note: Both name lists actually have more files then the stats show. The stats only count the names that translate to valid *_manila names.

Download:

Manila 2.5 Name List (8-Aug-09)

Manila 2.1 Name List

[GUIDE]: Manila 2.5 file names - what changed compared to 2.1 and earlier

The hash algorithm that was used in earlier Manila versions is unchanged in Manila 2.5. What has changed is the directory structure.

In Manila 2.1 all the mode9 files were located in \windows\htc\ (e.g. \windows\htc\home.mode9, \windows\htc\email.mode9), all the images in \windows\hts\assets\images and lua scripts in \windows\htc\scripts.

Manila 2.5 changes this by breaking it up into subdirectories. So home.mode9 is now located in \windows\htc\home\home.mode9. The same \windows\htc\home\ directory is shared by related mode9 files, such as citypicker.mode9 and worldclock.mode9 (full paths: \windows\htc\home\citypicker.mode9, \windows\htc\home\worldclock.mode9). Other mode9 files have different subdirectories e.g. calender.mode9 and calendar_picker.mode9 are located in \windows\htc\calendar\, while email.mode9 is \windows\htc\email\email.mode9 etc.

Now, any files referenced in the mode9 (images and scripts) are also in the same subdirectories. Because Manila uses relative paths, you'll see something like .\assets\images\%imagefilename%.qtc in a mode9 files.

The ".\" is the current directory. If you're editing \windows\htc\home\citypicker.mode9 then the current directory is \windows\htc\home\, so the full path of the image is \windows\htc\home\assets\images\%imagefilename%.qtc.

You might also see this: ..\common\assets\images\%imagefilename%.qtc. "..\" is up one directory. So again if you're editing \windows\htc\home\citypicker.mode9 up one dir from there is \windows\htc\, and the full image path becomes: \windows\htc\common\assets\images\%imagefilename%.qtc

Now that you have the full path you can use this small tool by NisseDILLIGAF to get the hashed name: http://xdaforums.com/show...&postcount=271

2.5 vs. 2.1 compared - example:

Manila 2.1: \windows\htc\email.mode9

Manila 2.5: \windows\htc\email\email.mode9

In both versions the mode9 has a reference to .\Assets\Images\Email\envelopeback.qtc, but the current directory ".\" is different between 2.5 and 2.1, so that:

Manila 2.1 .\ = \windows\htc\

Manila 2.5 .\ = \windows\htc\email\

So the full file names are:

Manila 2.1: \windows\htc\Assets\Images\Email\envelopeback.qtc

Manila 2.5: \windows\htc\Email\Assets\Images\Email\envelopebac k.qtc

And after the hash:

2.1: 77FB7FAD_manila

2.5: 5C5B9C11_manila