[KITCHEN][06.05.2010]Manila CMD Kitchen Environment

[12aon]

When I first started on this project, this kitchen existed of 5 script each containing few lines of code, only able to handle one LUA script at a time. I had just helped out on the first ever manila 2.0 VGA port and I could see the use of a kitchen that did most of the manual labour automatically. At that time my understanding of what needed to be done to successfully edit script was limited. As I tried to add more features to the script I learned more about LUA, the handling and decompiling of the scripts. I chose to make the kitchen do as much for you on first run. The kitchen got more mature after I met hilaireg who knew a lot more about batch scripting than I did and who's perfectionist style made the kitchen what it is today.

After we teamed up we started a little manila group and got into contact with co0kiemonster. He's the one who created\updated most of the tools on which the script relies, and so not only optimizing manila handling but also pushing it's boundaries. We put in the applications that best handle manila files and connected these via the script. Since our last update co0kie kept developing the tools and they became a lot better. A batch script isn't really the way to handle this but until we get a real manila GUI, we decided to give the script one last update. Since this will likely be the last big project hilaireg will be presenting here, this last version is dedicated to him.



Workstation/System Requirements:

The Manila Kitchen environment can run on a Windows XP, Windows Vista, and Windows 7 platform providing the following requirements are met:


Microsoft .NET 3.5 SP1 (M9Editor)
Elevated priviledges
Windows XP/Vista/Seven




Kitchen Contents:

ROOT


MANILATOOL.CMD by hilaireg & 12aon
Manila Kitchen Guide
Revision History
_SOURCE folder
_TOOLS folder
Shortcuts to tools



TOOLS


LUATOOL.EXE by Co0kiemonster
M9EXT.EXE by Co0kiemonster
MANILANAMES.EXE by Co0kiemonster
M9EDITOR.EXE by 6Fg8
CFC_GUI.EXE by Chainfire
NOTEPAD2.EXE by Florian Balmer, Compiled by Co0kiemonster
MANILAHASH.EXE by NisseDILLIGAF
XVI32.EXE by Christiaan Maas
RAPICOPY.EXE, RAPIPROC.EXE, RAPISTART.EXE by Scott Seliman
GREP.EXE by Tim Charron




Current Version (Attached Files)

Manila Kitchen 5.05.06, 4.7 MB (06/05/2010)



Previous Versions

Manila Kitchen 5.04.23, 4.7 MB (23/04/2010) (http://www.4shared.com/file/D86-JJ60/Manila_Kitchen_50423_FINAL.html)
Manila Kitchen 5.03.04, 4.1 MB (04/03/2010) (http://www.4shared.com/account/file/236807295/c4e49b33/Manila_Kitchen_50304_FINAL.html)
Manila Kitchen 4.10.16, 9.3 MB (16/10/2009) (http://www.4shared.com/account/file/234139672/d4e5c6c0/Manila_Kitchen_41016_FINAL.html)
Manila Kitchen 4.10.02, 7.7 MB (02/10/2009) (http://www.4shared.com/account/file/233539643/d6f9d90d/Manila_Kitchen_41002_FINAL.html)


Credits:

Special thanks to the following folks for sharing their knowledge and expertise. If I missed someone, it's purely accidental – send me a note and I will add your name to the list.

6fg8
chainfire
co0kiemonster
sztupy

[12aon]

The Manila Kitchen is an automated environment that includes tools (utilities) to perform decompilation, editing, and recompilation of HTC Manila OEM files.

Instructions are passed to the MANILATOOL command script which in turn, initiates various executables to perform the necessary actions required on the HTC Manila OEM files.

Some of the tools used by MANILATOOL were written by 6fg8, chainfire, co0kiemonster, and sztupy. As such, some of these tools are not compatible with excessively long path names or paths that contain spaces or brackets. To avoid issues, place the Manila Kitchen in a relatively short path that does not contain spaces or brackets such as: C:\XDA\Manila_Kitchen

The Manila Kitchen provides the following benefits:


Consolidated Tools

All of the tools required to perform Manila related activities have been incorporated. These include decompilation, comparison, recompilation, .CAB creation, direct deployment to mobile devices, updating Mode9 Editor reference index, and backing up. The executables are initiated with the appropriate command parameters and in the correct sequence by MANILATOOL thus eliminating the "guess work" typically required.


Improved Resiliency

The activities required to manage HTC Manila OEM files are complex in nature. In some cases, a Manila file may fail to be decompiled or cause one of the initiated executables to generate and error as a result of an unexpected condition. The MANILATOOL command script will attempt to recover from such errors when possible so as to complete the command that was initiated.


Command Line Help and Version Information

Wondering what command parameters are available in the MANILATOOL command script? Simply append -HLP to the end of the MANILATOOL command script to display a summary of parameters available. To determine the version of the MANILATOOL command script in use, append -VER to the end of the MANILATOOL command script.


Enhanced File Recovery

Accidentally changed a file and need the previous version? The MANILATOOL command script performs a backup before any critical operation making it easier to retrieve a previous version of a file.


Enhanced Script Diagnostics

Although a significant of amount effort has gone into the development of the Manila Kitchen, it is possible that a script logic error may occur. To assist in troubleshooting such errors, the MANILATOOL command script includes a comprehensive logging debugger.



Topic Index

Preparing the Kitchen Environment ....... 3 (http://forum.xda-developers.com/showpost.php?p=4555339&postcount=3)
Initializing the Kitchen
Decompiling Manila OEM Files ............ 4 (http://forum.xda-developers.com/showpost.php?p=5838819&postcount=4)
LUA Editing
Mode9 Editing
General Editing
Updating 'm9editor.names.txt'
Updating the Repository
Working with Manila Files ............... 5 (http://forum.xda-developers.com/showpost.php?p=5838820&postcount=5)
Initializing the Kitchen
Recompiling Manila OEM Files ............ 6 (http://forum.xda-developers.com/showpost.php?p=5844290&postcount=6)
Recompilation
Testing the Manila OEM File Changes ..... 7 (http://forum.xda-developers.com/showpost.php?p=5844294&postcount=7)
Installer .CAB Method
Direct to Device Method
Reference Web Links ..................... 8 (http://forum.xda-developers.com/showpost.php?p=5844297&postcount=8)

Frequently Asked Questions (FAQ) ........ 9 (http://forum.xda-developers.com/showpost.php?p=5838821&postcount=9)

[12aon]

The Manila Kitchen environment must be initialized prior to initial use. During the initialization phase, all MANILATOOL command script parameters are enabled and the contents of following folders, sub-folders, and files are removed and recreated:


_backup
_queue
Decompiled
Release
Repository
Workspace


The following configuration files will be reset to their initial settings:


m9editor.cfg .\_TOOLS\M9Editor
notepad2.ini .\_TOOLS\Notepad2
xvi32.ini .\_TOOLS\XVI32


The following applications shortcuts will be reset to their initial settings:


CFC_GUI.lnk
M9Editor.lnk
manilaHASH.lnk
Notepad2.lnk
HexEdit32.lnk


The following Manila Mode9 reference index will be reset to their initial settings:


m9editor.names.orig.txt .\_TOOLS
mnf_m9paths.orig.txt .\_TOOLS
m9editor.names.orig.txt .\_TOOLS\M9Editor




Initializing The Kitchen

The following procedure will initiate the Manila Kitchen initialization process. All HTC Manila OEM files found in the .\_SOURCE folder will be copied to the .\_queue folder.

Currently, there are two versions of Manila reference index names; one for pre-Manila 2.5 and one for post-Manila 2.5. It is possible to set the initial Manila reference version during the kitchen initialization procedure. For example, if the .\_SOURCE folder contains a specific version of HTC Manila OEM files, specify the Manila version as part of the parameter. If the kitchen will contain a mix of pre-Manila 2.5 and post-Manila 2.5 files, an incomplete set of Manila files, or an unknown Manila file, specify 0.0 as the kitchen version.

The following procedure will initiate the Manila Kitchen initialization process.

► To initiate a Manila Kitchen reset and specify Manila version 1.3

Place a copy of the original (untouched) HTC Manila OEM files or packages in the .\_SOURCE folder.
Double-click (launch) the Command Prompt shortcut found in the root of the kichen folder.
At the prompt, type the following command: manilatool.cmd -oem:1.3
Press ENTER.


► To initiate a Manila Kitchen reset and specify Manila version 2.5

At the prompt, type the following command: manilatool.cmd -oem:2.5
Press ENTER.


► To initiate a Manila Kitchen reset and specify a mix, small set, or unknown Manila files

At the prompt, type the following command: manilatool.cmd -oem:0.0
Press ENTER.

[12aon]

HTC Manila OEM files must be decompiled before changes can be made to them. The decompilation of HTC Manila OEM files occurs on files that are found in the .\_queue folder. Use the Manila Kitchen initialization process to copy the HTC Manila OEM files from the .\_SOURCE folder to the .\_queue folder before attempting to decompile files.

As files are processed, they are removed from the .\_queue folder and placed in a .\Processed folder. Once completed, decompilation mode will be disabled so as to prevent accidental loss of work to decompiled Manila files. The Manila Kitchen must be initialized in order to enable decompilation mode.



Decompilation

The decompilation process passes each manila file found in the .\_queue folder to the LUA processor (luatool.exe) tool. During the decompilation process, the LUA processor (luatool.exe) tool validates the decompilation and produces additional output files if the decompilation was not successful.

Additionally, the decompilation process will extract a copy of embedded Manila (Mode 9) scripts, initiate the LUA processor (luatool.exe) tool to decompile the extracted script, and validate that the decompilation occurred successfully.

Upon completion, a decompiled version of the Manila file will be found in one of the following folders - which are determined by the results of the decompilation process:


Completed: .\Workspace\_lua (successfully decompiled)
Incomplete: .\Workspace\_lua (partially decompiled)
Error: .\Workspace\_lua (failed decompilation)
InternetPortal: .\Workspace (XML files)
Manilapages: .\Workspace (XML files)
Mode9: .\Workspace (Mode9 files)
PNG: .\Workspace (Image files)
QTC: .\Workspace (Image files; in Graphics folder)
SQLite: .\Workspace (Database files)
TTF: .\Workspace (True Type Font files; in Graphics folder)
XML: .\Workspace (XML files)
Unknown: .\Workspace (Unknown files)



The following procedure will initiate the Manila Kitchen decompilation process.

► To initiate HTC Manila OEM file decompilation

Ensure desired HTC Manila OEM files are present in the .\_queue folder once the kitchen initialization has completed.
Double-click (launch) the Command Prompt shortcut found in the root of the kichen folder.
At the prompt, type the following command: manilatool.cmd -dec
Press ENTER.

[12aon]

Once the HTC Manila OEM files have been decompiled, changes may be made as required. The Manila Kitchen provides a single work area for Manila file editing; this is:


Workspace



Workspace

This workspace contains all of the decompiled Mode9 files, graphics, and other Non-LUA files that are typically manipulated using the M9Editor, Notepad2, and/or CFC_GUI.


Workspace\_lua

This area of the workspace contains all of the decompiled LUA files. Use a standard UTF-8 compatible editor such as Notepad2 to make changes to the files.



LUA Editing

Files that have failed to decompile during the initial decompilation process typically need to be manually edited so as to address the cause of the failure. Editable *.lua Manila files reside in the .\Workspace\_lua folder and may be change with a text editor such as Notepad2.

Once the Manila file has been fixed, initiate the the LUA Comparison (luatool.exe) tool to validate that the changes made to the file are correct.

The LUA Comparison process will compare the changes made to the decompiled Manila file against the original Manila file. If successful, the Manila file will be moved from the .\Incomplete or .\Error folder to the

.\Completed folder.

The following procedure will initiate the comparison process.

► To initiate Manila file comparison

At the prompt, type the following command: manilatool.cmd -cmp
Press ENTER.




Mode9 Editing (Mode 9, Graphics, PNG)

M9Editor is a tool for editing Manila files; nearly all aspects of a Mode9 LUA file can be viewed, changed, and saved. Mode 9 LUA Manila files are stored in the .\Workspace\Mode 9 folder and are changed with from within the M9Editor.

Additionally, the M9Editor tool provides graphics import/export capabilities as well as Chainfire File Compression (CFC) support. Lastly, the M9Editor tool includes a folder (directory) viewer which displays information specific to Manila files.

Although it is possible to decompile Manila files with the M9Editor tool, the current version (3.0.03) utilizes a deprecated version of the LUA Decompiler (luadec.exe) which is not supported by this Manila Kitchen.

► To initiate the M9Editor tool

Navigate to the Manila Kitchen folder.
Double-click the M9Editor shortcut.




General Editing (InternetPortal, Manilapages, QTC, PNG, SQLite, TTF, XML)

Some of the Manila files found in the .\Workspace folder may also be changed by other tools such as Notepad2 and CFC_GUI.

► To use an other tool to edit certain Manila files

Launch the desired tool (ex: Notepad2, CFC_GUI, etc.)
Select the Open file option from within the tool.
Navigate to the .\Workspace folder.
Select the Manila file to change.




Updating 'm9editor.names.txt'

From time to time, HTC adds new Manila files or updates the names of existing ones. To update the M9Editor Reference Index file, initiate the Manila name scan process using the MANILATOOL command script. The Manila Name Finder (mnf.exe) tool will iterate through the HTC Manila OEM files found in the .\_SOURCE folder and obtain the new names.

Updating the m9editor.names.txt reference index file ensures that the M9Editor tool is able to display the friendly Manila file name making it easier to work with Manila files - instead of the compiled Hash name used by HTC. Currently, there are two versions of Manila reference index names; one for pre-Manila 2.5 and one for post-Manila 2.5.

The Manila name scan process supports the following Manila versions: 2.5, 2.2, 2.1, 2.0, 1.3, 1.2, 1.1, and 1.0. Specifying a Manila version other than 2.5 will initiate the Manila Name Finder (mnf.exe) tool in pre-Manila 2.5 scan mode. The MANILATOOL command script determines which scan mode to use by first querying the 'kitchen-ver' file - if the value is 0.0; the mode specified in the command parameter is utilized.

Use one of the following procedures to initiate the appropriate M9Editor reference index update process.

► To initiate a pre-Manila 2.5 reference index update

At the prompt, type the following command: manilatool.cmd -mnf:2.1
Press ENTER.


► To initiate a Manila 2.5 reference index update

At the prompt, type the following command: manilatool.cmd -mnf:2.5
Press ENTER.




Updating the Repository

Updating the .\Repository folder ensures that a recent backup copy is available in the event that a change to *.lua must be reversed. During the repository update, decompiled *.lua files found in the .\Workspace\_lua folder are copied to the .\Repository\_lua and a hierarchy (by unhashed names) is created in the .\Repository\windows folder.

The .\Repository\windows folder hierachy displays shortcut links to the Manila files that correspond to a Manila feature. For example, navigate the hierarchy and double-click the shortcut link that corresponds to the file that requires modification - the appropriate tool will be launched.

The following procedure will initiate the repository update process.

► To initiate a repository update

At the prompt, type the following command: manilatool.cmd -lib
Press ENTER.

[12aon]

Once editing is complete, the Manila files must be recompiled before they may be used on a mobile device.

Should an error be encountered during recompilation, the MANILATOOL command script will create a Manila LUA error log file in the .\Release\_error folder and continue recompiling Manila LUA files. In the event of a "hard" recompilation error, the contents of .\Release\_lua folder will be removed and the previous successful recompilation will be restored.



Recompilation

The recompilation process occurs on files that found in the .\Workspace\_lua\Completed folder. Once completed, the files are ready for deployment to a mobile device that is directly connected to a workstation or via an installer .CAB file.

The following procedure will initiate the recompilation process.

► To initiate Manila file recompilation

At the prompt, type the following command: manilatool.cmd -rec
Press ENTER.

[12aon]

The Manila Kitchen environment provides additional tools for testing a final work product. Manila files can be distributed to mobile devices using one of the following methods:


Installed .CAB
Direct to Device


The quickest method of distributing recompiled Manila files is via an installer .CAB file. The direct to device method of distributing recompiled Manila files is via ActiveSync over a USB/Serial connection - this method is
quickest during development activities.



Installer .CAB Method

The MANILATOOL command script provides a parameter to automatically create a redistributable .CAB file. The installer .CAB can be copied to the mobile device and launched using the device File Explorer. Alternatively, the installer .CAB file may be installed via ActiveSync. Should an installer .CAB fail to install on a device, it is likely that policy restrictions are in effect.

The following procedure will initiate the .CAB creation process.

► To initiate the CAB Wizard tool

At the prompt, type the following command: manilatool.cmd -cab
Press ENTER.




Direct to Device Method

The MANILATOOL command script includes a parameter to automatically stop the mobile device Manila executable (manila.exe), transfer a copy of the Manila files, and restart the mobile device Manila executable.

The copy operation may fail on a device where policy restrictions are in effect. Additionally, the Manila executable may not restart in such cases.

The following procedure will initiate the comparison process.

► To initiate RAPI Copy tool

At the prompt, type the following command: manilatool.cmd -dep
Press ENTER.

[12aon]

Manila 3D Kitchen
http://winmo.sztupy.hu/manilakitchen.html
http://forum.xda-developers.com/showthread.php?t=487331


Manila Tutorial
http://forum.xda-developers.com/showthread.php?t=399212


LUA Decompiler
http://forum.xda-developers.com/showthread.php?t=568281


LUA 5.1 Decompiler
http://winmo.sztupy.hu/luadec.html
http://forum.xda-developers.com/member.php?u=1433290
http://forum.xda-developers.com/showthread.php?t=479910


LUA Decompiling Tutorial
http://winmo.sztupy.hu
http://winmo.sztupy.hu/manilakitchen/rhodium2_manila_wvga_src.zip


TF3D Manila Mode9 Editor
http://forum.xda-developers.com/showthread.php?t=464984


MNF - Manila Name Finder
http://forum.xda-developers.com/showthread.php?t=546820


CFC - The Manila/TF3D Image Editor
http://forum.xda-developers.com/showthread.php?t=437777


TouchFLO/Manila/SenseUI
http://forum.xda-developers.com/group.php?groupid=131


Co0kie's Beta Testing and Development
http://forum.xda-developers.com/group.php?groupid=192


Max Sense Testers
http://forum.xda-developers.com/group.php?groupid=185


GT7 Sense 2.1 Theme Beta Testers
http://forum.xda-developers.com/group.php?groupid=202


Leaked Full EXT/Manila 2.5 Packages-latest official sprint tp2
http://forum.xda-developers.com/showthread.php?t=642817

[12aon]

What types of files can be placed in the '.\_SOURCE' folder?

Any type of file may be placed in the .\_SOURCE folder. The MANILATOOL command script will only copy files that contain the word "manila" in them to the .\_queue folder.



I accidentally specified the wrong version of Manila files during the kitchen initialization; is there a way to change it without initializing the kitchen again?

The default Manila file version is stored in the kitchen-ver file. Use a standard text editor such as Notepad2 to edit file. The file must contain a three characters equivalent to the version - valid versions are: 2.5, 2.2, 2.1, 2.0, 1.3, 1.2, 1.1, 1.0, and 0.0 (Unknown/Custom)



What is the '._BACKUP' folder used for?

Before most operations occur, a backup of files that will be changed or removed from/in a given folder is performed. This ensures that previous functional files remain available in the event that a "rollback" is required.



What is the difference between the "Incomplete", "Error", and "Completed" (successful) LUA folders?

Manila files that are successfully decompiled are will appear in the "completed" folder - 100% comparison result. Manila files that are decompiled but do not pass the comparison validation (less than 100%) are placed in the "incomplete" folder. Manila files that report a 0% decompilation result are placed in the "error" folder.



What is the difference between the files in the '.\Release\_lua', '.\Release\_error', '.\Release\CAB', and '.\Release\DEVICE' folders?

The .\Release_error folder will only appear when unexpected errors were encountered during Manila LUA file recompilation. The folder will contain logs detailing the problem that was encountered with a Manila LUA file. The folder is removed and recreated at each recompilation.

The .\Release\_lua folder contains the recompiled versions of the Manila LUA files that are found in the .\Workspace\_lua folder. These are the files can be distributed directly to a device or via CAB file.

The .\Release\CAB folder contains the recompiled versions of the files found in the .\Release\_lua folder. These are the files can be installed via ActiveSync or a Storage Card.

The .\Release\DEVICE folder contains the recompiled versions of the files found in the .\Release\_lua folder. These are the files can be installed via ActiveSync or a Storage Card.



What is the difference between the files in the '.\Processed', '.\Workspace', and '.\Repository' folders?

The .\Processed folder contains the HTC OEM Manila files that were copied to the .\_queue during the Manila Kitchen initialization process. During the decompilation process, the files are moved from the .\_queue folder to the appropriate folder - which is determined by the LUA Comparison tool results.

The .\Workspace\_lua folder contains decompiled versions of the HTC OEM Manila files - these are the files that are typically modified and recompiled. The remainder of the folders in the .\Workspace folder contain various non-LUA files.

The .\Repository\_lua folder contains a duplicate copy of the decompiled Manila files. The repository serves a form of backup.



What are the extra .TXT files that appear in the partially decompiled LUA script folders?

The *.error.txt file contains the STDOUT error that was generated by the LUA Decompiler. When this file appears, there is a logical error in there script, which makes it impossible to run the script. The file will usually contain the approximate (line number) location where the problem was encountered.

The *.log.txt file contains the compared disassembly output from the orignal Manila file and the decompiled LUA version - which appears in the folder. When this file appears, it is an indication that the script will function but it does not match the original Manila file.

The *.dis.txt file contains the raw (full) disassembly of the original Manila file and may be used to resolve the decompilation issue.

The *.status.txt file contains the decompilation result - 0% to 100%.


Visit the following website to obtain more information in troubleshooting a failed decompilation:
http://winmo.sztupy.hu



Is the disassembly output always correct?

Yes. Even though the some of the events may be not be displayed in the disassembly output, the correct sequence of events will be provided.



The M9Editor tool provides a built-in decompiler, why not just use that?

The internal LUA Decompiler (luadec.exe) provided with the M9Editor tool is an earlier version. This internal version does not provide the extra files required to resolved decompilation errors.

The M9Editor should be used when editing Mode9 files and attach extracted embedded LUA script back to their original Mode9 files.



There are strange errors such as '.\documents and settings\<profilename>\eee' errors, what is the solution? (Only in older versions)

One of the Manila Kitchen tools is in an unknown state or temporary files are locked and cannot be freed. Note the path location of the .\eee folder, restart the workstation, and manually delete the folder, sub-folders, and files.



An error message is displayed when attempting to delete a file or folder, what is the solution?

A running process is preventing the file or folder from being removed. Restart the workstation and manually delete the file or folder.



Can Error Reporting be disabled so as to not have to click the Close button every time the LUA Decompiler and/or LUA Comparison tool generate an application error?(Only in older versions)

As previously noted, some Manila files cause the LUA Decompiler (luadec.exe) and/or LUA Comparison (compare.exe) tool to generate an application error. Visit the following website(s) for more information on how to suppress the Error Reporting message box.

Windows XP
http://www.windowsnetworking.com/articles_tutorials/Disable-Error-Reporting-Windows-XP-Server-2003.html (http://www.windowsnetworking.com/articles_tutorials/Disable-Error-Reporting-Windows-XP-Server-2003.html)


Windows Vista/Seven
http://thehiddenguide.com/how-to-disable-error-reporting-in-windows-vista (http://thehiddenguide.com/how-to-disable-error-reporting-in-windows-vista)

[hilaireg]

Although a significant of amount effort has gone into the development of the Manila Kitchen, it is possible that a script logic error may occur. To assist in troubleshooting such errors, the MANILATOOL command script includes a comprehensive logging debugger.

The logging debugger can provide basic, expanded, or verbose (full) logging. To enable the logging debugger, append -DEB:[1-5] to the end of the MANILATOOL command script. For example, to set the logging debugger level to 1, type the following command at the Command Prompt:

manilatool.cmd -hlp -deb:1


Processing activities are displayed in the Command Prompt window and are recorded in the ManilaTool_Log_#.##.##.txt file. The log file will include the version of MANILATOOL command script and the command parameters that was requested. The following logging debugger levels are available:

Level 0: Default. The MANILATOOL command script typically operates at this level.

Level 1: Provides slightly more details on the script processing activities. Specifiy this logging level to view the results of actions performed on a Manila file.

Level 2: Provides comprehensive details on the processing activities performed on a Manila file. Specify this logging level when trying to determine why a Manila file may have failed to be processed. Choosing this logging level on a large number of Manila files will increase the time it takes to complete Manila file processing.

Level 3: Developer verbose level 1. Specify this logging level to view the script routine names that are invoked during operation as well as the variables that are dynamically set. Choosing this logging level on a large number of Manila files will greatly increase the time it takes to complete Manila file processing.

Level 4: Developer verbose level 2. Specify this logging level to view the script routine names that are invoked during operation as well as the dynamic and common variables that are set. Choosing this logging level on a large number of Manila files will drastically increase the time it takes to complete Manila file processing.

Level 5: Developer verbose level 3. Specify this logging level to view the script routine names that are invoked during operation, display all script variables. Additionally, this logging level will create a .\_debug folder which will contain a copy of the files that are normally removed during a script routine operation. Choosing this logging level on a large number of Manila files will significantly increase the time it takes to complete Manila file processing.


The following log files are generated during MANILATOOL command script processing:

ManilaTool_Log_#.##.##.txt
ManilaTool_FileCopyLog_#.##.##.txt
ManilaTool_LUAFilesLog_#.##.##.txt
ManilaTool_MNFLog_#.##.##.txt
ManilaTool_Mode9Log_#.##.##.txt
ManilaTool_NonLUAFilesLog_#.##.##.txt

[bilbobrian]

Very nice work as always 12 :)

[conflipper]

Very nice work on this, I am around now, So I can start to help out more, haha

[kinnyfaifai]

Forgive me for being an utter dumbass.

I've got your kitchen and was trying it out. However, what files do I need to drop into folder 01_manila? I've tried dropping just the manila file into it, the extracted *.luac scripts but I keep getting errors saying no files found.

Kindly point me in the right direction?

Thanks.

KF

[12aon]

Forgive me for being an utter dumbass.

I've got your kitchen and was trying it out. However, what files do I need to drop into folder 01_manila? I've tried dropping just the manila file into it, the extracted *.luac scripts but I keep getting errors saying no files found.

Kindly point me in the right direction?

Thanks.

KF

Yes sure, That's the reason I included the m9editor as well, for it's abilty todifferentiate between different kinds of manila files. Copy only the Lua files (unchanged) to the 01_manila folder. There is a checkbox in the m9editor and if you will check it, it allows copying of multiple files. After that you are good to go and you can run the 01_Decompile.bat, 12

[MRFERRARI23]

That's whats up!

@MRFERRARI23

What I think that going wrong with you is that your files are not called xxxxxxxx_manila make sure they are name that way or the cab creation script won't recognize them.

One other thing I noticed is that the path to the kitchen contains names with spaces like "mr vizziato". This can throw the kitchen off. To test this put the kitchen directly in you C:\ folder or in any rate not in the folder with spaces in in their names, and check back with me, 12

the 2 files I have in there now just look like this 18c01b6d_manila and 72ac571f_manila so I think they are in there right

as for running the program im doing so right from my desktop screen cause when I try to run it from c drive an I go to name the cab It doesnt give me that black pop screen it goes to this white page with info that doesnt allow me to do anything!

EDIT: how do I eliminate that space between mr vizziato?? I cleared the space by going to the start menu an going to my name but idk still nothing

[serg635]

12aon, Please, help me. I can`t decompilled file from manila 2.1 "53cc1e4f_manila",
if you can do this - help me please.
291480

[12aon]

Hey man, I am currently on a trip in the USA and I do not have the means to help you decompile at the moment. If you want it decompiled right away you can check out stupy's threads and tutorials (I have links in my first post) but I warn you this is kinda hard, good luck, 12

[serg635]

Hey man, I am currently on a trip in the USA and I do not have the means to help you decompile at the moment. If you want it decompiled right away you can check out stupy's threads and tutorials (I have links in my first post) but I warn you this is kinda hard, good luck, 12

Ok, I will wait )))), and when you will be able to do this?

[muttim86]

Thanks, really useful that you did! ;)

[Co0kieMonster]

Man, this is seriously awesome :D
Extremely helpful tool, thank you very much :)

[Co0kieMonster]

Very nice work with v3. Finally got some free time to give it a spin. Decompiled both Manila 2.1 and 2.5 scripts:
2.1.38680.1 - automatically decompiled 357 of 534 scripts.
2.5.duttysR1 - automatically decompiled 422 of 649 scripts.

Goes a long way toward making work with Manila easier and faster, thanks again.

[12aon]

Very nice work with v3. Finally got some free time to give it a spin. Decompiled both Manila 2.1 and 2.5 scripts:
2.1.38680.1 - automatically decompiled 357 of 534 scripts.
2.5.duttysR1 - automatically decompiled 422 of 649 scripts.

Goes a long way toward making work with Manila easier and faster, thanks again.

Yes This is about as much as I can do with the decompiler as it is right now. But if you you have feature request, I'd be happy to try to implement them :), 12

[rotastrain]

there is a new problem
the decompiler gives a output of 99%
the error.text has no errors in it:confused:
i have attached the files here in a zip.please help me out!!

291481

cheers

[12aon]

there is a new problem
the decompiler gives a output of 99%
the error.text has no errors in it:confused:
i have attached the files here in a zip.please help me out!!

220499

cheers

Did you fix this? I decompiled the script but the error.txt was deleted (as it should when it's empty). What do you mean by the 99%? 12

[jmckeejr]

Ok 12,
I am not sure if this is the right place to ask as I dont know if the files that need changed are lua or whatever. Maybe you can help me out.
Seems SSmaHo isnt working with a lot of these new builds of 6.5.1 and I would really like to change a few things.
1)I want to make world clock open G-Alarm instead. Does anyone know which files need edited and how I can edit them? I mean if you have it done already feel free to share, but I would still like a little more info on how to edit these.
2)On people tab I would like to open Resco Contacts from "all people". I know you did some of these mods for 2.0 manila so maybe you can help out here with very minimal effort
3)I would like to make Showaco's all program tab tweak with the grid instead of the long list for manila 2.1. I think this is a mode9 file, and I was able to look at it with mode9 editor and found the changes I "think" I need to make, but am not sure how to update the manila file.

[12aon]

Ok 12,
I am not sure if this is the right place to ask as I dont know if the files that need changed are lua or whatever. Maybe you can help me out.
Seems SSmaHo isnt working with a lot of these new builds of 6.5.1 and I would really like to change a few things.
1)I want to make world clock open G-Alarm instead. Does anyone know which files need edited and how I can edit them? I mean if you have it done already feel free to share, but I would still like a little more info on how to edit these.
2)On people tab I would like to open Resco Contacts from "all people". I know you did some of these mods for 2.0 manila so maybe you can help out here with very minimal effort
3)I would like to make Showaco's all program tab tweak with the grid instead of the long list for manila 2.1. I think this is a mode9 file, and I was able to look at it with mode9 editor and found the changes I "think" I need to make, but am not sure how to update the manila file.

Think I can help you with the first two and I can assist with the third, working on the kitchen right now, be in touch, 12

[jmckeejr]

Thanks 12. So what I did was tried to edit the mode9 file for programlauncher and I dont know how to make the changes. I mean I edited the file: 22bb3b19_manila_tree.txt which I think will hold the key to changing all programs tab. I dont know how to actually apply the changes to the manila file :(

[12aon]

Thanks 12. So what I did was tried to edit the mode9 file for programlauncher and I dont know how to make the changes. I mean I edited the file: 22bb3b19_manila_tree.txt which I think will hold the key to changing all programs tab. I dont know how to actually apply the changes to the manila file :(

Hmmm, it sound like you got sidetracked :). The changes need to occur in the m9editor UI. Just double click on the the file in the explorer window and you'll see the entire tree inside the UI. Then if you need to compare that mode9 files to showaco's there is a function that does that incorporated in the m9editor. You can also just open the one file in one instance of the m9editor and that open the other one in another one. Than you can just copy the changes you need over to to the other file and save if the changes are right, 12

[jmckeejr]

Hmmm, it sound like you got sidetracked :). The changes need to occur in the m9editor UI. Just double click on the the file in the explorer window and you'll see the entire tree inside the UI. Then if you need to compare that mode9 files to showaco's there is a function that does that incorporated in the m9editor. You can also just open the one file in one instance of the m9editor and that open the other one in another one. Than you can just copy the changes you need over to to the other file and save if the changes are right, 12

haha, your right. I was editing the txt file I got from compare or something.

[jmckeejr]

12,
I think tis is the file for changing all people softkey to resco contact manager or whatever(same as 2.0 manila). Also, I included the edited script, but I get error when trying to compile and import :( Hope it makes it easy for you to help me. Or tell where I messed up to get the error"end expected near local at line 77"(or similar).. Are you using 2.1?
Also attatching trial of resco contact manager in case you need to test.There are actually diiferent command lines(install the software and look at the lnk for the exact ones. Is it possible to use these? To go directly to contacts instead of built in resco dialer?

Still looking for the world clock files. Not sure if there is an easier way, I might have to go through one at a time ? This is the one that really matters to me too :(

[12aon]

12,
I think tis is the file for changing all people softkey to resco contact manager or whatever(same as 2.0 manila). Also, I included the edited script, but I get error when trying to compile and import :( Hope it makes it easy for you to help me. Or tell where I messed up to get the error"end expected near local at line 77"(or similar).. Are you using 2.1?
Also attatching trial of resco contact manager in case you need to test.There are actually diiferent command lines(install the software and look at the lnk for the exact ones. Is it possible to use these? To go directly to contacts instead of built in resco dialer?

Still looking for the world clock files. Not sure if there is an easier way, I might have to go through one at a time ? This is the one that really matters to me too :(

Ok, I'll see what I can do. Just for the info, some files won't we fully decompiled by my kitchen that's why you get the error messages. For the files to recompiles you need to first fix those errors before you do your custom edits. You did change the right line :), 12

[jmckeejr]

Ok, I'll see what I can do. Just for the info, some files won't we fully decompiled by my kitchen that's why you get the error messages. For the files to recompiles you need to first fix those errors before you do your custom edits. You did change the right line :), 12

Is it odd that the file from 2.0 decompiled correctly, but 2.1 did not? Or maybe I just decompiled your icontact version from 2.0, cant remember. Would it then decompile correctly if it was already decompiled and fixed?
Thanks for the help and the good info. Maybe one of these days I'll be decomiling and compiling like a pro LOL

If you are able to fix the errors can you also attatch the script so I can get a look and maybe it will make something stick for me :)
Any idea how to find the WorldClock lua? Looking at the name list I wish I could put a "face" with the names :(

Thanks 12, you the man :)

[12aon]

Is it odd that the file from 2.0 decompiled correctly, but 2.1 did not? Or maybe I just decompiled your icontact version from 2.0, cant remember. Would it then decompile correctly if it was already decompiled and fixed?
Thanks for the help and the good info. Maybe one of these days I'll be decomiling and compiling like a pro LOL

If you are able to fix the errors can you also attatch the script so I can get a look and maybe it will make something stick for me :)
Any idea how to find the WorldClock lua? Looking at the name list I wish I could put a "face" with the names :(

Thanks 12, you the man :)

Well the problem is the decompiler and the fact that htc doesnt use a single style of scripting, since the scripts are made a bunch of different parties. So the decompiler does about fifty of the decompiling right. If its not right you gotta do the rest by hand. This makes decompiling a bit difficult.

As for the checking of the files look for an app called manilaHASH by Nissedilligaf. Take care, 12

[jmckeejr]

cAN YOU SEE IF THIS IS THE ONE i NEED FOR REMAPPING WORLD CLOCK? Sorry bout the cap lock :(

[hilaireg]

cAN YOU SEE IF THIS IS THE ONE i NEED FOR REMAPPING WORLD CLOCK? Sorry bout the cap lock :(

Wrote that from ur phone didn't ya?

;)

[12aon]

cAN YOU SEE IF THIS IS THE ONE i NEED FOR REMAPPING WORLD CLOCK? Sorry bout the cap lock :(

Nope that's not it, the file you send is a mode9 fine and the three scripts I extracted from it don't have any reference to any link. I'm looking myself but I think I'll be closer to the home tab lua files. As for decompiling of the of the that people tab lua, I'm going to need more time since it's completely different from the old one I have.

Hilaireg and I are rewriting the kitchen (most credit goes to him) but in this kitchen mode9 lua scripts will automatically be extracted and decompiled on first run. you'll be able to check through most of the scripts. I you want I can post my the library of successfully decompiled files for you to look through, 12

EDIT: try this one, and recompile

[jmckeejr]

OK, thanks. Will try that. I was able to get the grid in all programs tab(I know someone did it, but I want with original program tab 3 icons per ROW). But I need to resize the shortcut links in program tab because they are smaller now. Not sure if you are using 2.1 GenY or not, but here are the files. Can you maybe tell me what is needed to change the size? If not, I'll just start playing with the values and see what happens. Sorry to be so needy :o Dont worry if you dont have time to look. I know how it is. I spent 6 hours yesterday trying to fix my kitchen which was making unbootable ROMs :(

[12aon]

OK, thanks. Will try that. I was able to get the grid in all programs tab(I know someone did it, but I want with original program tab 3 icons per ROW). But I need to resize the shortcut links in program tab because they are smaller now. Not sure if you are using 2.1 GenY or not, but here are the files. Can you maybe tell me what is needed to change the size? If not, I'll just start playing with the values and see what happens. Sorry to be so needy :o Dont worry if you dont have time to look. I know how it is. I spent 6 hours yesterday trying to fix my kitchen which was making unbootable ROMs :(

Ill take a look as soon as I finish up the stuff i need to do for manila kitchen v4. I installen your rom to help out but I need to find a touch pro keyboard changer :o, take care 12

[jmckeejr]

Ill take a look as soon as I finish up the stuff i need to do for manila kitchen v4. I installen your rom to help out but I need to find a touch pro keyboard changer :o, take care 12

Look under settings>Administrative tools :) There is ProFuze keyboard selector in there.

So I edited this file you posted and it has to be the right file, because now when I click clock it doesnt do anything. I put in same type of line as for the all people button:
ShellNavigateTo("\\Program Files\\ageye\\G-Alarm\\GAlarm.exe","")

Is this not correct? Do I need the second set of quotes there? Or is that for like parameters or command line? I'll try without now. Thanks

[12aon]

Yeah thats for commandline settings. Are you sure the you have the right exe. I remember ther being more than one link in in the file. Can try changing it to something more simple line and an exe you know will run. Ill check when I get back home, 12

ps I did search for that...:o

[jmckeejr]

If you cant get to it under "start menu>settings>System>Administrative tools", then you can also get to the folder in windows. Or I can just give u the reg entries if you still need :) Thanks, I'll look some more after the kids go to bed :)

[Fredz]

Your kitchen is really great. Thanks for your job.:)

[jmckeejr]

Yeah thats for commandline settings. Are you sure the you have the right exe. I remember ther being more than one link in in the file. Can try changing it to something more simple line and an exe you know will run. Ill check when I get back home, 12

ps I did search for that...:o

OK, so I tried notepad in windows just to check and it does the same, when I press clock it gets selected, but nothing opens at all :( Must be missing another file possibly. Anyway, seems SSmaHo is finally working angain with these newer builds, so I can deal with that for now. Although it would be nice to have this ability without relying on aniother program. Thanks for the help. Hope you enjoy(ed) the ROM :)

[12aon]

OK, so I tried notepad in windows just to check and it does the same, when I press clock it gets selected, but nothing opens at all :( Must be missing another file possibly. Anyway, seems SSmaHo is finally working angain with these newer builds, so I can deal with that for now. Although it would be nice to have this ability without relying on aniother program. Thanks for the help. Hope you enjoy(ed) the ROM :)

Sorry for the late reply, been busy (with V4 also (MAD receptc to hilaireg) might be in the mode9 if it's not controlled in the lua or the might be another line in the same lua. Try look it up a bit more when I have some time, 12

[jmckeejr]

Thanks for the reply 12, I heard from Hilaireg that the kitchen should be finished soon, so that is good. I will take another stab at this once I get the new kitchen :) What have you found the best way to search for the correct files? Will file locator pro read the _manila files and search for certain text? Or is decompiling necessary first? Sorry, if you havent tried File Locator Pro here (http://www.mythicsoft.com/Page.aspx?type=filelocatorpro&page=home) is a link :)

[hilaireg]

Thanks for the reply 12, I heard from Hilaireg that the kitchen should be finished soon, so that is good. I will take another stab at this once I get the new kitchen :) What have you found the best way to search for the correct files? Will file locator pro read the _manila files and search for certain text? Or is decompiling necessary first? Sorry, if you havent tried File Locator Pro here (http://www.mythicsoft.com/Page.aspx?type=filelocatorpro&page=home) is a link :)

Should be able to search through any decompiled Manila files. I'm working on the User Manual as I type ... yes, at the same time ;)

[12aon]

Should be able to search through any decompiled Manila files. I'm working on the User Manual as I type ... yes, at the same time ;)

Like:

Faq:... yes,... will... at... this... the... kitchen... same... be... time... able... ;) to.... :p

[12aon]

After a lot of hard work Hilaireg and me are proud to present to you, the new and improved "Manila Kitchen". Come forth and be amazed (and have fun),

H & 12

Edit: I seemed to have uploaded the wrong package, contained some development rudimentaries (so those 4 who dl know). Fixed!

[Captain_Throwback]

This looks impressive, and extremely useful for anyone who uses Manila (on any device). This is sticky-worthy :).

[12aon]

This looks impressive, and extremely useful for anyone who uses Manila (on any device). This is sticky-worthy :).

Yeah only thing this baby needs is a better decompiler, anybody here knows C++ and help us out of our misery, contact hilaireg (because he likes to do the hard work).....

or me

[jmckeejr]

Any chance somone can make some simple .bat files like the old kitchen(or shortcuts)? I do not like to use DOS, and am actually terrible with it. I was able to initialize the kitchen and all, but I liked how the previous kitchen worked simply dropping my file into 01_MANILA folder and double clicking decompile. Think it would be much more user friendly if it did not rely on knowledge of DOS and command prompts :( Also would be a timesaver as double clicking a link is so much easier than trying to find the right command and syntax. Luckily I typed "manilatool.cmd -dec" and all worked

[12aon]

Any chance somone can make some simple .bat files like the old kitchen(or shortcuts)? I do not like to use DOS, and am actually terrible with it. I was able to initialize the kitchen and all, but I liked how the previous kitchen worked simply dropping my file into 01_MANILA folder and double clicking decompile. Think it would be much more user friendly if it did not rely on knowledge of DOS and command prompts :( Also would be a timesaver as double clicking a link is so much easier than trying to find the right command and syntax. Luckily I typed "manilatool.cmd -dec" and all worked

Takes some time getting used too, but you must realise that every single script uses the same parameters now because are taken from the same pool. We made a pretty explanatory help function. Also this kitchen has a lot more features.

I do have a tip for you and other who do not like to write a lot. Use the "TAB" function for word completion. just type "m" and hit tab three times. That should save you some time.

BTW have you gotten my PM?,

12

[hilaireg]

Any chance somone can make some simple .bat files like the old kitchen(or shortcuts)? I do not like to use DOS, and am actually terrible with it. I was able to initialize the kitchen and all, but I liked how the previous kitchen worked simply dropping my file into 01_MANILA folder and double clicking decompile. Think it would be much more user friendly if it did not rely on knowledge of DOS and command prompts :( Also would be a timesaver as double clicking a link is so much easier than trying to find the right command and syntax. Luckily I typed "manilatool.cmd -dec" and all worked

I'm confused ...

There's a Command Prompt shortcut in the root of the kitchen that you can double-click. As per the first post of this thread, you can then type:

manilatool.cmd -hlp


... to obtain a list of available parameters. Lastly, I took the time to put a User Guide together which walks folks through decompilation of manila files to recompilation ... essentially, end-to-end.

Either you're going too fast and trying to "cut corners" and getting caught ;) Or you're using an entirely different kitchen. :rolleyes:

BTW, all the tools where intended to run at a command prompt in the past. 12aon built early generations of the kitchen to semi-automate the handling of the parameters for the tools - Manila Kitchen 4.0 ensures that decompilation results are consistent.

If you're having issues figuring out how to pass a parameter to MANILATOOL.CMD from a Command Prompt, send me a PM or MSN me directly and I'll help you get sorted out.

:)

[12aon]

Mod edit: keep every relevant kitchen question in the thread so that other may benefit :p

[jmckeejr]

I'm confused ...

There's a Command Prompt shortcut in the root of the kitchen that you can double-click. As per the first post of this thread, you can then type:

manilatool.cmd -hlp


... to obtain a list of available parameters. Lastly, I took the time to put a User Guide together which walks folks through decompilation of manila files to recompilation ... essentially, end-to-end.

Either you're going to fast and trying to "cut corners" and getting caught ;) Or you're using an entirely different kitchen. :rolleyes:

BTW, all the tools where intended to run at a command prompt in the past. 12aon built early generations of the kitchen to semi-automate the handling of the parameters for the tools - Manila Kitchen 4.0 ensures that decompilation results are consistent.

If you're having issues figuring out how to pass a parameter to MANILATOOL.CMD from a Command Prompt, send me a PM or MSN me directly and I'll help you get sorted out.

:)

hmm.. well in Manila Kitchen 3.00.06 it just seemed easier to use from an enduser POV. I would drop my _manila file into 01_MANILA folder then doubleclick on 01_Decompile.cmd to decompile. Then I could make my changes in the decompiled files found in "Manila_Kitchen\02_DECOMPILED\Successxxx" folder and then double click on 03_RECOMPILE.cmd. I know there is a command prompt shortcut in the kitchen, but as I said it just seemed easier when there was no need for use of command prompt. I'm not having probs with the parameters, but thinki it would save a considerable amount of time if the parameters were made into shortcuts or .bat files which can easily be ran from the kitchen. So, instead of helping me figure how to pass the parameters using the command prompt maybe you could show me how to make a shortcut which passes the parameters or .bat or whatever would be needed to do the same thing without need of cmd prompt :)
All that being said, I would like to commend both of you on your work with this kitchen. I am a total newb to editing manila files, but was able to make some changes and even made my own programs tab with grid for "all programs" using the older kitchen and other mods as reference. Once I figure out this new kitchen environment I hope to mod the home clock to open G-Alarm(yes, 12 I am still trying to figure that one out. I found the file you had referenced me, but I could not extract the embedded scripts or even view them with m9editor :( ) If you get bored, maybe you could help me out more and we could post some modded manila files in this thread for everyone to enjoy and learn from :)

[hilaireg]

hmm.. well in Manila Kitchen 3.00.06 it just seemed easier to use from an enduser POV. I would drop my _manila file into 01_MANILA folder then doubleclick on 01_Decompile.cmd to decompile. Then I could make my changes in the decompiled files found in "Manila_Kitchen\02_DECOMPILED\Successxxx" folder and then double click on 03_RECOMPILE.cmd. I know there is a command prompt shortcut in the kitchen, but as I said it just seemed easier when there was no need for use of command prompt. I'm not having probs with the parameters, but thinki it would save a considerable amount of time if the parameters were made into shortcuts or .bat files which can easily be ran from the kitchen. So, instead of helping me figure how to pass the parameters using the command prompt maybe you could show me how to make a shortcut which passes the parameters or .bat or whatever would be needed to do the same thing without need of cmd prompt.

The previous scripts were error prone and gave a false sense of completion in some cases.

IMO, the new kitchen folder structure is much more intuitive. Folks know which files require M9Editor and which files can simply be edited via Notepad2.

Although I don't recommend this approach, create a shortcut to MANILATOOL.CMD and append the desired parameter to the properties of the shortcut. I suggest also appending the debug parameter and elevating the logging to 1 or 2.

HTH,

[12aon]

hmm.. well in Manila Kitchen 3.00.06 it just seemed easier to use from an enduser POV. I would drop my _manila file into 01_MANILA folder then doubleclick on 01_Decompile.cmd to decompile. Then I could make my changes in the decompiled files found in "Manila_Kitchen\02_DECOMPILED\Successxxx" folder and then double click on 03_RECOMPILE.cmd. I know there is a command prompt shortcut in the kitchen, but as I said it just seemed easier when there was no need for use of command prompt. I'm not having probs with the parameters, but thinki it would save a considerable amount of time if the parameters were made into shortcuts or .bat files which can easily be ran from the kitchen. So, instead of helping me figure how to pass the parameters using the command prompt maybe you could show me how to make a shortcut which passes the parameters or .bat or whatever would be needed to do the same thing without need of cmd prompt :)
All that being said, I would like to commend both of you on your work with this kitchen. I am a total newb to editing manila files, but was able to make some changes and even made my own programs tab with grid for "all programs" using the older kitchen and other mods as reference. Once I figure out this new kitchen environment I hope to mod the home clock to open G-Alarm(yes, 12 I am still trying to figure that one out. I found the file you had referenced me, but I could not extract the embedded scripts or even view them with m9editor :( ) If you get bored, maybe you could help me out more and we could post some modded manila files in this thread for everyone to enjoy and learn from :)

You do realise that we put a lot of effort in to make it work as propely as it does now. It used to be separate scripts not shortcuts and they were a lot buggier than you might think. I do not agree that it is easier to just double click on them even though I started out from that perspective.

Every command you used you can very easily use again by pushing the "up" and "down" buttons. Hilaireg put a lot of effort in the manual, you'll find that it will tell you everything you need to know, in an easy to read way.

To we did change some of the names to make it easier to understand for everyone (the ones already using it will have to adjust a bit). Decompiled now contains only the original scripts (very useful to me) and the all the editing is done in the workspace folders. So (1) You'll drop any folder that also contains manila files (like packages) or just the files in the Source folder (2) You'll do you editing in the workspace folders and (3) you'll see the result in the release folder. Pretty basic don't you think? Then there is the repository that has the scripts library (easier to search through by function). And the backup folder in with you may find the edits you thought you'd lost, but no the kitchen saved them for you :).

Now try the "TAB" button and the "Up" and "Down" button and you'll find this pretty easy to navigate (I speak from experience, as I'm not to great in dos either).

As for G-alarm check your PM's I think I send you the decompiled script that contained the values you needed,

12

[jmckeejr]

Sorry if I came off as ungrateful, I wasnt trying to seem so. I just thought I might be able to create a .lnk file like on ppc which would contain the parameters. ie ""c:\my-kitchen\manilatool.cmd"-dec" for frequent use of the same commands. If it is a big issue, I will stick to the command prompt or to the older kitchen if that becomes too much( I know your thinking" dude, this guy doesnt want to type a few letter? Holy sh@t. And after I did all this work!") I am only trying to think of ways to make it even easier:)
The script you pm'd me seems correct, the issue is that I cant get to the script in the file that you had quoted. It is mode9, and not lua so I was going to try to edit it with m9editor.exe but some of the scripts in the file will not even show. I was able to sucessfully edit the other files to open resco contacts from people tab, but the home page must be a bit more difficult. Its not a huge deal, I just thought it would be cool to open g-alarm without need for ssmaho(which doesnt work on some of the new com3 builds like 23053).
again, thanks for all your work here. I do understand the work required to do something like this for public use(I have been trying to make my custom ROM kitchen public friendly for a month now, but keep adding more and ending back at square one). Props go to you and Hilaireg for all the work put into it.

[hilaireg]

... ""c:\my-kitchen\manilatool.cmd"-dec" ...

Change it to:

"C:\My-Kitchen\manilatool.cmd" -dec -deb1


Make sure to run the -OEM parameter first as it resets the kitchen to "factory" settings - creates missing folders, copies source files, fixes shortcuts, fixes INI files, etc. Important, -OEM is destructive - it will clear out the kitchen of all files/folders that are not in .\SOURCE and .\TOOLS.

Also, you will only be able to run -DEC once per kitchen - until you reset the kitchen with -OEM. This was done to ensure that folks didn't accidentally attempt to decompile a second time ... destroying their work.

HTH,

[yozgatg]

I > Manila :cool:

[12aon]

Changelog 4.10.02

- Add 'delims=|' to most 'FOR /f %%' logic
- Updated m9editor.names.txt
- Updated mnf_m9paths.txt
- Updated m9editor.names.orig.txt
- Updated to Luadec 2.1! Thanks to Co0kiemonster
* Less scripts in crashing folder
* Better "Else" and "Elseif" handeling
* Added "break" handling
* Fixed conditional handling for some weird cases

[Fredz]

A better decompiler!
GREAT new:D.
Thanks 12. I try this ASAP.

[yozgatg]

well it's only going to get better
we might not reach 100%, but hey any improvement is welcome

it's not going to make a difference for me though since I'm already manually decompiling everything :p
anyway, in addition to a new version of my VGA port, I will also be releasing a full kitchen (every single script perfectly decompiled) when I have the new build (2.1.1919.????) from the offical HTC wm6.5 rom

[12aon]

well it's only going to get better
we might not reach 100%, but hey any improvement is welcome

it's not going to make a difference for me though since I'm already manually decompiling everything :p
anyway, in addition to a new version of my VGA port, I will also be releasing a full kitchen (every single script perfectly decompiled) when I have the new build (2.1.1919.????) from the offical HTC wm6.5 rom

Well where would be the sense in making a completely decompiling decompiler, us manual old-skoolers would become redundant :p

I was thinking of making a depot of all the manila's with all their scripts decompiled, but since I'm not as good as manually decompiling as you I'll wait just a bit for that

@ Fredz: good to see you are still up in the manila game :)

[morina]

i'm a noob to the manila kitchen and would like to ask if this kitchen can be used for manila 2.5

thanx in advance

[hilaireg]

Yes, supports 2.1 and 2.5 manila ... take a moment to review the guide included in the kitchen.

Cheers,

[morina]

i've been wndering if it is possible to display column with the full path of the file

due to my lack of knowledge in manila file names, i need the full path to be able to understand the files correctly

thanx again

[hilaireg]

This kitchen simply extracts/compiles the manila files using existing tools created by other developers.

You could look at using this approach:

- Look at M9Editor names file for the path
- Paste the path into ManilaHASH to determine the filename
- Use M9Editor to change files found in the WORKSPACE_MODE9 folder


Ideally, what's required is an actual Manila GUI Kitchen environment similar to what chefs use to build ROMs for devices. The kitchen should include ALL of the functionality required to:

- Decompile
- Verify
- Edit ALL manila resources (xml, lua, images, etc.)
- Recompile
- Create CAB
- Copy to device
- Archive (backup)


The M9Editor and XMLGUI is the closest we have to a GUI-like environment at the moment. If we could coordinate the efforts of all the devs who are passionate about Manila, I bet we could create an excellent Manila GUI Kitchen and avoid having to use cr@ppy CMD scripts for stuff ... or Command Prompts for that matter.

;)

[morina]

you are more than right

but since i couldn't find anything like that, i'm trying to use this tool to see if there are chances to modify the manila interface

i'm happy with what there already is, but it's time consuming if i have to revert to a txt file and do a seach for each file in the scripts.

there is already a name resolution to the files, the full path is present in the names.txt, the only thing i miss right now is a separate column to display the full path name. or on the other hand to have the same column that shows the file names, to have it show in full path format.

then it would be much easier to look at the scripts and make necessary modifications, further development ........

in any case, i thank you for your reply

[12aon]

From what I understand you would like to have the full manila path name inside the lua files as well? That is not something that can be done by modifying the our tool. Luckily for you we have a great guy working on LuaDec right as we speak (he's the one responsible for LuaDec 2.1). I'm sure he'd agree that it would be a neat feature to add.

http://forum.xda-developers.com/showthread.php?t=568281

So I guess so far so good?

12

[morina]

sorry for the missunderstanding :(

i'm a noob to this, probably that's why i'm not able to explain it correctly.

in m9Editor there are 3 main windows:
top for the mode9
bottom left for the files
bottom right the preview

so, in the bottom left windows there are columns, one of the column shows a translated manila file name. so here i'd like to see the rest of the path for the file. just as it is in the list of file names provided with the tool

it would be great if the path is placed on a new column in front of the filename

this way when you lookup the mode9 file and there is reference to that file like this: "..\..\..\..\products\manila\Deploy\HTC\Home\Assets \Images\Home\VGA\home_background.png", you can identify which manila file is the string about :)

this way will enable even noobs like me do some work around the layout

thanx again

PS: this issue whas important before i read the hilaireg's signature ;) about not working with a full package at a time... now it's much easier with separated packages but still i think it would be a good idea

[12aon]

sorry for the missunderstanding :(

i'm a noob to this, probably that's why i'm not able to explain it correctly.

in m9Editor there are 3 main windows:
top for the mode9
bottom left for the files
bottom right the preview

so, in the bottom left windows there are columns, one of the column shows a translated manila file name. so here i'd like to see the rest of the path for the file. just as it is in the list of file names provided with the tool

it would be great if the path is placed on a new column in front of the filename

this way when you lookup the mode9 file and there is reference to that file like this: "..\..\..\..\products\manila\Deploy\HTC\Home\Assets \Images\Home\VGA\home_background.png", you can identify which manila file is the string about :)

this way will enable even noobs like me do some work around the layout

thanx again

PS: this issue whas important before i read the hilaireg's signature ;) about not working with a full package at a time... now it's much easier with separated packages but still i think it would be a good idea

I see now that tool is the m9editor and although it is part of the kitchen and we tweaked it just a bit to work better with our kitchen, it's entirely the creation of 6Fg8 and there's not much we can do about that.

http://forum.xda-developers.com/showthread.php?t=464984

That's the thread were it was released,

12

[morina]

I see now that tool is the m9editor and although it is part of the kitchen and we tweaked it just a bit to work better with our kitchen, it's entirely the creation of 6Fg8 and there's not much we can do about that.

http://forum.xda-developers.com/showthread.php?t=464984

That's the thread were it was released,

12

i noticed that m9editor was created by 6Fg8, but since i read this (http://forum.xda-developers.com/showpost.php?p=4104630&postcount=566) i was discuraged to post there

that's why i saw it fit to post here.

sorry, and thanks again

[neofral]

hi,

first of all i'd like to thank u guys for this magnificent tool

hapy to see that it can work with manila 2.5 files

i edited a lua script file after it was decompiled with the manilatool. i woked on the file based in the folder workspace_lua

after that according to the instructions ran the tool with -cmp

when i tried to create a cab for that file i get the following:

Windows CE CAB Wizard
Error: Section [SourceDisksFiles] or [SourceDisksFiles.ManilaKitchen] is required


help please

[hilaireg]

@neofral:

I'm going to assume that you ran MANILATOOL in this order:

-CMP -> compare
-REC -> recompile
-CAB -> make CAB


If so, run the -REC and -CAB parameters again with debug logging enabled.

MANILATOOL.CMD -REC -DEB:4
MANILATOOL.CMD -CAB -DEB:4


Make sure to rename the log (ex: ManilaTool_Log.txt -> ManilaTool_Log_REC.txt) before running the next command and post both logs here for us to look at.

Cheers,

[12aon]

-cmp = Compare
Use this when you have a lua file that is not successfully decompiled, trying to make it so.
-rec = Recompile
Use this to recompile you lua file into a luac file that can be used on your device.
-cab = Create cab
Create a cab file from the recompiled files

The reason you are not getting anything is because there are no files in the release folder too create a cab from.

Read the manual in the root of the kitchen, it's all pretty well documented,

12

Edit: hilaireg beat me too it, but you must understand that the -cmp is anly needed if the files are not placed in the success_<manilaname> folder. If they are not in the success_<manilaname> folder you need to do some manual decompiling because the decompiled script is not the same as the original lua file. Until the files are placed in the success_<manilaname> folder you can't use the -rec option.

[neofral]

@neofral:

I'm going to assume that you ran MANILATOOL in this order:

-CMP -> compare
-REC -> recompile
-CAB -> make CAB


If so, run the -REC and -CAB parameters again with debug loggin enabled.

MANILATOOL.CMD -REC -DEB:4
MANILATOOL.CMD -CAB -DEB:4


Make sure to rename the log (ex: ManilaTool_Log.txt -> ManilaTool_Log_REC.txt) before running the next command and post both logs here for us to look at.

Cheers,

sorry for that,

i guess i missread the instructions. there was no explanation about the -rec command

the manilatool_log_rec.txt doesn't show the error i get on the dos prompt screen, which is:
MANILATOOL.CMD by 12aon, hilaireg
Version: 4.10.02

:Manila file recompilation requested
LVAC.EXE: 22E41977_manila.lua:14: '=' expected near 'error'
:Manila file recompilation completed



i also attached the manila_log_rec.txt

[neofral]

-cmp = Compare
Use this when you have a lua file that is not successfully decompiled, trying to make it so.
-rec = Recompile
Use this to recompile you lua file into a luac file that can be used on your device.
-cab = Create cab
Create a cab file from the recompiled files

The reason you are not getting anything is because there are no files in the release folder too create a cab from.

Read the manual in the root of the kitchen, it's all pretty well documented,

12

sorry for this but i did and after i saw this i ran a search just in case i've missread but there is no explanation. i attache the file, see for yourself :)

i uploaded the file in zip format, exciding the limit for file type :o


respond to your edit: the file was successfuly decoded and it was in a folder with the success_ prefix

[12aon]

sorry for this but i did and after i saw this i ran a search just in case i've missread but there is no explanation. i attache the file, see for yourself :)

i uploaded the file in zip format, exciding the limit for file type :o


respond to your edit: the file was successfuly decoded and it was in a folder with the success_ prefix

It indeed seems you have found an error of hilaireg's :D

I will upload the corrected version later but the -cmp in the recompilation piece must be -rec

You can always type: manilatool.cmd -hlp to see the options again,

12

[neofral]

It indeed seems you have found an error of hilaireg's :D

I will upload the corrected version later but the -cmp in the recompilation piece must be -rec

You can always type: manilatool.cmd -hlp to see the options again,

12

that was not my intention in any way :)

but i thank you guys for your support on this

i hope somebody is making a visual kitchen so it'll be easier to edit the graphics, and mode9 scripts all in one place :D

too bad that Hilaireg discontinued his support on the m9editor. i really love it and doesn't much more work to be "one stop shop" for editing manila, but on the other hand we are all depend on availability so.....

thanks you again

[hilaireg]

@neofral:

#1 - User Guide Structure

-OEM: Preparing the Kitchen Environment

-DEC: Decompiling Manila OEM Files

-CMP: Working with Manila Files
-MNF: Working with Manila Files

-REC: Recompiling Manila OEM Files

-CAB: Testing the Manila OEM File Changes
-DEP: Testing the Manila OEM File Changes



#2 - Upload Your Kitchen As-Is

Please RAR/ZIP your entire kitchen as-is and send PM to 12aon with a download link.



#3 - Logging

Your log indicates that you did not run MANILATOOL in debug logging mode; please see the Appendix in the guide. Run MANILATOOL.CMD from a command prompt with these parameters:

MANILATOOL.CMD -rec -deb:4

[hilaireg]

It indeed seems you have found an error of hilaireg's

How to say this ... Oh right, don't think so.

I suspect the new LUADEC may have introduced an issue that LUAC.EXE can't handle. See below:

"LUAC.EXE: 22E41977_manila.lua:14: '=' expected near 'error'"



If it was an error in the script, we would not see the following:

MANILATOOL.CMD by 12aon, hilaireg
Version: 4.10.02

: Manila file recompilation requested
: Manila file recompilation completed

[12aon]

@neofral:

#1 - User Guide Structure

-OEM: Preparing the Kitchen Environment

-DEC: Decompiling Manila OEM Files

-CMP: Working with Manila Files
-MNF: Working with Manila Files

-REC: Recompiling Manila OEM Files
-CAB: Testing the Manila OEM File Changes

-DEP: Testing the Manila OEM File Changes



#2 - Upload Your Kitchen As-Is

Please RAR/ZIP your entire kitchen as-is and send PM to 12aon with a download link.



#3 - Logging

Your log indicates that you did not run MANILATOOL in debug logging mode; please see the Appendix in the guide. Run MANILATOOL.CMD from a command prompt with these parameters:

MANILATOOL.CMD -rec -deb:4




@12aon:

Suspect LUADEC may have introduced an issue that LUAC.EXE can't handle.

Nah, buddy just an error in the guide (you and your rigorous problem solving mind) check the recompilation piece (especially the command line) ;)

@Neofral:

So you are producing cabs now? It was actually 6Fg8 who created the m9editor :)

[hilaireg]

that was not my intention in any way :)

but i thank you guys for your support on this

Don't consider finding an issue bad. When a problem occurs, it's expected to see a post about it.


i hope somebody is making a visual kitchen so it'll be easier to edit the graphics, and mode9 scripts all in one place

The current iteration utilizes tools written by various XDA members.


too bad that Hilaireg discontinued his support on the m9editor. i really love it and doesn't much more work to be "one stop shop" for editing manila, but on the other hand we are all depend on availability so

I didn't write M9EDITOR. I wrote the MANILATOOL.CMD wrapper script that invokes various tools.

Ideally, I would much prefer putting the time to building a proper GUI application. As with others, my time is limited, so it would have to be a joint effort.

Cheers,

[hilaireg]

@neofral:

IMPORTANT:

#2 - Upload Your Kitchen As-Is

Please RAR/ZIP your entire kitchen as-is and send PM to 12aon with a download link.

[12aon]

@ neofral

Ok, after a long discussion with hilaireg, I figured out what's wrong. The edit's you made to the script are not valid. Check line 14 and skip uploading the kitchen :),

12

[neofral]

i utmostly thank you guys for your support.

i had to leave office for a trip and now i'm back so couldn't reply any eralier.

indeed the error was in line 14. i corrected it and successfuly recoded and made a cab. although the script crashed on me (due to inexperience i guess) :(

in about a week or so there will be a thread with my work and will not forget to thank and post links to the tools i've used.

right now there is a lot of things i have in mind on modding manila 2.5. after we've done some checking, cooking, testing, i'll certainly share all the scripts and everything i've created with the tools on the kitchen i downloaded in this thread's post 1

so, patience and i promise to share since that's the only way i can truly say thank you guys since i'm not able to create a paypal account and make appropriate donations ;)

thank you again

[neofral]

hi,

so, i'm working on manila 2.5 landscape

the only tool i'm using for that so far is the se of tools provided on post 1 of this thread.

all the credit goes to all the people infovolved and mentioned in post 1.

i ran a problem decoding a file which anyways i'm cona try to recode it as is but i'm affraid it's not gona be good enough :(

so far this is the first problem decoding with manilatool.cmd -dec

i attached the zip of the file info at WORSKPACE_LUA folder, and the source file as well

maybe i'm posting this in the wrong thread, so please feel free to correct me

[muttim86]

thanks 12, great work! ;)

[12aon]

New & Last release uploaded and ready!

Changelog 5.03.04

- Mode9ScriptExtractor 1.0 (M9EXT)
- LuaTool 1.2.2beta (LUATOOL)
- Manila Name Finder 1.5 (MNF)
- Manila Names Builder 1.0 (MANILANAMES)
- CFC 0.60 & CFC GUI 0.60.35 (CFC & CFC_GUI)
- Update user guide
- Prefix 'TOOLS' and 'SOURCE' folders with underscore (_)
- Consolidate workspaces down to one
- Force '-MNF' pre-requisite at kitchen initialization
- Fix 'File Not Found" message during manila file copy phase in '-OEM'
- Added reporting to '-DEC'

[meltwater]

New & Last release uploaded and ready!

Excellent work, this has been a huge help in getting to grips with manila.

One thing I have noticed is running "manilatool -oem:2.5" etc doesn't always reset the kitchen properly (previous 4.10.02 with -oem, worked fine) , it doesn't seem to find new source files in the source folder when you try to compile. Not a major issue for me since, deleting and unpacking the kitchen again resets everything anyway.
I'll post the exact messages when it next happens.

Also, I wonder if there would be a way to have multiple workspaces/repository/releases etc so you can work on several packages at once without mixing up all the files. Perhaps by supporting subfolders in source and transferring the structure to each of the key folders. Then specify which one (or all) you want to dec / cmp / rec etc.
Clearly that is a big job, but perhaps something which can be done in time. It would mean I'd be able to keep all the source files and decompiled files in the kitchen and work exclusively in that folder (at the moment, I keep source and decompiled copies of the packages separate, and only work with a few files in the kitchen).

EDIT: Ok last version...so scrap that! Although fix to reset the kitchen would be nice...

Anyway, as I said, superb stuff and I would have been lost without it!

[hilaireg]

One thing I have noticed is running "manilatool -oem:2.5" etc doesn't always reset the kitchen properly (previous 4.10.02 with -oem, worked fine) , it doesn't seem to find new source files in the source folder when you try to compile. Not a major issue for me since, deleting and unpacking the kitchen again resets everything anyway.
I'll post the exact messages when it next happens.

RAR/ZIP up your "_SOURCE" folder and make it available for download - here or in the 'Manila CMD Kitchen' development thread in the Social Group.

Remember to use -OEM:0.0, if you're working with a small set of Manila files or a mixture of Manila files from different versions. Also, the sequence of the kitchen was intended to be as follows:

-OEM:#.#
-MNF:#.#
-DEC


You can "cheat" and run -MNF:#.# first; if the kitchen needs to be reset, -OEM will run with and then -MNF would run. Once -DEC has run once, it is disabled to prevent further running.

Also, I wonder if there would be a way to have multiple workspaces/repository/releases etc so you can work on several packages at once without mixing up all the files. Perhaps by supporting subfolders in source and transferring the structure to each of the key folders. Then specify which one (or all) you want to dec / cmp / rec etc.
Clearly that is a big job, but perhaps something which can be done in time. It would mean I'd be able to keep all the source files and decompiled files in the kitchen and work exclusively in that folder (at the moment, I keep source and decompiled copies of the packages separate, and only work with a few files in the kitchen).

The Manila CMD Kitchen is intend to run on a single group (set) of Manila files. If you're working with several versions of Manila (ex: 2.1.x, 2.5.x, 2.5.y, etc.), they should be in separate kitchens.

A GUI Manila kitchen could easily support loading workspaces ... similar to loading projects in development studios.


HTH,


* EDIT *

If you're comfortable or want to learn batch scripting, enable the Logging Debugger (http://forum.xda-developers.com/showpost.php?p=5838824&postcount=10). The script is fairly well commented to make it easy to troubleshoot: PARSE, PREP VARS, VALIDATE, MAIN, PARAMETER FUNCTIONS, CALL ROUTINES, SUB ROUTINES, ERROR, DONE SCRIPT

[meltwater]

Typically it isn't doing it now.:D
Thanks though.

EDIT: My best guess at the moment is that something was open and probably stopped key files/folders being cleared. If so then, no problem.

[hilaireg]

LOL ...

No worries, next time it happens; RAR/ZIP the entire kitchen up and upload for me to have a look at.

Cheers,

[pp18]

One thing I have noticed is running "manilatool -oem:2.5" etc doesn't always reset the kitchen properly (previous 4.10.02 with -oem, worked fine) , it doesn't seem to find new source files in the source folder when you try to compile.

dunno whether we encountered the same issue. it also took me some time to deal with the "Source files not found" error. it turned out to be a simple solution in my case:
just to use "attrib -s" and "attrib -h" commands to make the *_manila files visible to the tool. :P

[hilaireg]

That's odd; I run an ATTRIB on the '_SOURCE' as part of the -OEM function. Was this the first time you ran the kitchen on the files in '_SOURCE' or had you run the previously run the kitchen and you were resetting the kitchen?

Cheers,

[meltwater]

That's odd; I run an ATTRIB on the '_SOURCE' as part of the -OEM function. Was this the first time you ran the kitchen on the files in '_SOURCE' or had you run the previously run the kitchen and you were resetting the kitchen?

Cheers,

I might have dropped some new source files in perhaps. Haven't had the same issue for a while now.

[hzggz]

thanks for the good work

[pp18]

That's odd; I run an ATTRIB on the '_SOURCE' as part of the -OEM function. Was this the first time you ran the kitchen on the files in '_SOURCE' or had you run the previously run the kitchen and you were resetting the kitchen?
Cheers,

i'm a newbie in manila mod. it was my first time to reset the kitchen when encountering the "source files not found" error, right after extracting the package and copied a couple manila files.


ps. the link to Lua_Decompiling_Tutorial under the FAQ section is dead. any other source available? the weathergizmo script was decompiled at 99% only, and i'm now a bit lost in how to fix it. :(

[hilaireg]

i'm a newbie in manila mod. it was my first time to reset the kitchen when encountering the "source files not found" error, right after extracting the package and copied a couple manila files.

A "Source Files Not Found" error usually indicates that MANILATOOL.CMD could not find Manila files in the '_SOURCE' folder. Next time you reset your kitchen, use the following parameters as indicated in the documentation:

MANILATOOL.CMD -OEM:[#.#] -DEB:2


If you encounter the error, post the log file to the thread.


ps. the link to Lua_Decompiling_Tutorial under the FAQ section is dead. any other source available? the weathergizmo script was decompiled at 99% only, and i'm now a bit lost in how to fix it. :(

Looks like the site is gone; have removed the link. There are a Social Groups (SG) you can join; you will find them in the Reference Web Links (post #8).

[etoy]

hi guys,i downloaded the manila kitchen,put the source files,decompiled,etc..everything fine but i can't manage running m9editor.exe. everytime i try to run it, it crashes,before even showing up. i'm using win7 x64 and i already got .net framework 3.5.1 installed. my user account is already administrator. am i missing something else? please let me know,thanks!

[hilaireg]

hi guys,i downloaded the manila kitchen,put the source files,decompiled,etc..everything fine but i can't manage running m9editor.exe. everytime i try to run it, it crashes,before even showing up. i'm using win7 x64 and i already got .net framework 3.5.1 installed. my user account is already administrator. am i missing something else? please let me know,thanks!

Try setting compatibility mode on the m9editor EXE.

HTH,

[etoy]

Try setting compatibility mode on the m9editor EXE.

HTH,

already tried all compatibility modes available but no luck. had to start a windows xp mode (virtualization) to run the m9editor.. :(

[pp18]

A "Source Files Not Found" error usually indicates that MANILATOOL.CMD could not find Manila files in the '_SOURCE' folder. Next time you reset your kitchen, use the following parameters as indicated in the documentation:

MANILATOOL.CMD -OEM:[#.#] -DEB:2


If you encounter the error, post the log file to the thread.


attached please find the log file at debug levels 2 and 3 respectively. after manually running "attrib -s" on the manila files, the initialization process succeeded.

[12aon]

attached please find the log file at debug levels 2 and 3 respectively. after manually running "attrib -s" on the manila files, the initialization process succeeded.

To me these aren't very conclusive but Hilaireg is the man to talk to about debugging. But what You are saying is the 'system' attribute wasn't removed by the kitchen?

[hilaireg]

Added missing ATTRIB in :OEM_CREATE_DIRECTORIES section

[programatix]

Hi,

I did a quick search but couldn't find what I'm looking for... maybe I'm not familiar with the keyword that should be used for searching.

Anyway, I'm trying to figure out how to reinsert the compiled LUA file back to mode9. I tried the attach menu in m9editor and it report that the file must be in the script folder. If I tried the import menu, it seems like nothing happened. Further more, offset shown in m9editor doesn't match the one in the name of the LUA file (I'm guessing that one of the hex in the file name is the offset).

Thanks in advance.

[meltwater]

Hi,

I did a quick search but couldn't find what I'm looking for... maybe I'm not familiar with the keyword that should be used for searching.

Anyway, I'm trying to figure out how to reinsert the compiled LUA file back to mode9. I tried the attach menu in m9editor and it report that the file must be in the script folder. If I tried the import menu, it seems like nothing happened. Further more, offset shown in m9editor doesn't match the one in the name of the LUA file (I'm guessing that one of the hex in the file name is the offset).

Thanks in advance.
I think this is right, but I'm sure it'll be corrected if I'm wrong.

The LUA files or luac scripts, are handled by decompiling and recompiling via the ManilaTool command-line. The scripts contain the code which defines the behaviour. Eg:
OnNavigateOut = function(l_1_0)
_request.NavigateOutTo:disconnect(OnNavigateOut)
_application.OnVisibilityChanged:disconnect(Handle VisibilityChanged)
machineStatus.TwentyFourHourTime.OnValueChanged:di sconnect(HandleTimeChange)
if g_DialogRequest then
g_DialogRequest.MenuItemExternalProperty:disconnec t(OnMenuItemTypeCallback)
g_DialogRequest.QueryDynamicChildren:disconnect(Qu eryDynamicChildren)
g_DialogRequest.OnExit:disconnect(DialogMenu_Callb ack)
g_DialogRequest = nil
end
PeopleEmailObj:Destroy()
EmailGroup.onKeyUp:disconnect(HandleKeyUp)
Transition(l_1_0, "Out")
if PeopleFBLinkCheckObj ~= nil then
PeopleFBLinkCheckObj:Destroy()
end
end

The mode9 files, have to be edited directly in the mode9editor (via the treeview), these files define the objects used. Eg:
<Object>Type="GLESMask"
<Property> Name=Instance Name Value="Mask"
<Property> Name=Rectangle Value="PosX1=240 PosY1=488 PosX2=480 PosY2=888"
<Group>
<Object>Type="SequentialListView"
<Property> Name=Indicator Border Width Value=""
<Property> Name=IndicatorColor Value="??"
<Property> Name=Instance Name Value="SummaryListView"
<Property> Name=Position Value="PosX=0 PosY=-50 PosZ=0"
<Property> Name=EnableIndicatorBar Value=""
<Property> Name=Viewport Value="PosX=480 PosY=542 Width=0"
<Property> Name=Auto Hide Indicator Bar Value=""
<CharacterReference> LibraryName=facebook.mode9 Value="2"
<Object>Type="Group"

The other type of file you will find is a graphic file, i.e. png file which are coded in different ways or as normal graphic files.

So depending on the type of file the course of action is different. The luac files are re-compiled via the command line tool, the mode9 object files are edited directly in the Mode9editor and the graphic files (not too sure about the different types/compression etc) but should be handled in the Mode9editor.

[programatix]

I think this is right, but I'm sure it'll be corrected if I'm wrong.

The LUA files or luac scripts, are handled by decompiling and recompiling via the ManilaTool command-line. The scripts contain the code which defines the behaviour. Eg:
OnNavigateOut = function(l_1_0)
_request.NavigateOutTo:disconnect(OnNavigateOut)
_application.OnVisibilityChanged:disconnect(Handle VisibilityChanged)
machineStatus.TwentyFourHourTime.OnValueChanged:di sconnect(HandleTimeChange)
if g_DialogRequest then
g_DialogRequest.MenuItemExternalProperty:disconnec t(OnMenuItemTypeCallback)
g_DialogRequest.QueryDynamicChildren:disconnect(Qu eryDynamicChildren)
g_DialogRequest.OnExit:disconnect(DialogMenu_Callb ack)
g_DialogRequest = nil
end
PeopleEmailObj:Destroy()
EmailGroup.onKeyUp:disconnect(HandleKeyUp)
Transition(l_1_0, "Out")
if PeopleFBLinkCheckObj ~= nil then
PeopleFBLinkCheckObj:Destroy()
end
end

The mode9 files, have to be edited directly in the mode9editor (via the treeview), these files define the objects used. Eg:
<Object>Type="GLESMask"
<Property> Name=Instance Name Value="Mask"
<Property> Name=Rectangle Value="PosX1=240 PosY1=488 PosX2=480 PosY2=888"
<Group>
<Object>Type="SequentialListView"
<Property> Name=Indicator Border Width Value=""
<Property> Name=IndicatorColor Value="??"
<Property> Name=Instance Name Value="SummaryListView"
<Property> Name=Position Value="PosX=0 PosY=-50 PosZ=0"
<Property> Name=EnableIndicatorBar Value=""
<Property> Name=Viewport Value="PosX=480 PosY=542 Width=0"
<Property> Name=Auto Hide Indicator Bar Value=""
<CharacterReference> LibraryName=facebook.mode9 Value="2"
<Object>Type="Group"

The other type of file you will find is a graphic file, i.e. png file which are coded in different ways or as normal graphic files.

So depending on the type of file the course of action is different. The luac files are re-compiled via the command line tool, the mode9 object files are edited directly in the Mode9editor and the graphic files (not too sure about the different types/compression etc) but should be handled in the Mode9editor.

Some mode9 files contain lua script, not? manilatool seems to extract the LUA out, but I don't find a way to attach them back.

[meltwater]

Some mode9 files contain lua script, not? manilatool seems to extract the LUA out, but I don't find a way to attach them back.

No (again sorry if I have this wrong), the xxxxxxxx_manila files are various different file types, with mode9 being one of them. Another type are in fact language files in xml, which you can view/edit directly.

Oh forgot the mode9editor can extract the luac scripts, I recommend you use command line manilatool for that since it uses a newer decompiler (I suggest you read the Manila Kitchen Guide as it explains it a little more). You don't need to attach them back, they are separate files to the mode9 objects.

You will find within the mode9 object files, that they will reference the luac scripts.
<Object>Type="Behavior"
<Property> Name=Script File Value=".\Scripts\People\PeopleUpdatePage.luac"
The path and file name is referenced within the files, but when sense uses it, it will look for a file which matches the HASH name. The HASH name is like a checksum of the path & name, so you can only generate it if you know the full path and name, and unfortunately takes a little guess work to find.
0de73b01_manila \windows\htc\people\Scripts\People\peopleUpdatePag e.luac

This is how all the files are referenced to each other, the manilaHASH program allows you to find the files but the full path can be hard to work out (the manilatool command also helps with this since it uses a list of the common ones to help expand those references).

Hope that sheds some light on it, it's an odd system (sense that is) but you can just about work with it. Have a look at my tutorials in my sig, not totally complete but might get you started off.

[hilaireg]

Some mode9 files contain lua script, not? manilatool seems to extract the LUA out, but I don't find a way to attach them back.

AFAIK, there aren't provisions in the current kitchen tools (incl. M9Editor) to rebuild (reform) the pieces that make up a mode9 file.

Cheers,

[programatix]

No (again sorry if I have this wrong), the xxxxxxxx_manila files are various different file types, with mode9 being one of them. Another type are in fact language files in xml, which you can view/edit directly.

Oh forgot the mode9editor can extract the luac scripts, I recommend you use command line manilatool for that since it uses a newer decompiler (I suggest you read the Manila Kitchen Guide as it explains it a little more). You don't need to attach them back, they are separate files to the mode9 objects.

Thanks for the explaination, but I believe mode9 can also contain lua script.

mode9 content of 1a6d7b0d_manila
<Property> Name=Script Value="{binary, offset=478, pcodelen=598}"

extracted lua script

1a6d7b0d_manila_00_0004ac
1a6d7b0d_manila_01_0008fe
1a6d7b0d_manila_02_000fe8
...



AFAIK, there aren't provisions in the current kitchen tools (incl. M9Editor) to rebuild (reform) the peices that make up a mode9 file.

Cheers,

Hi,

Can it be done manually? If yes, would be great if I could get a link to it, or is there any documentation on mode9 format? Maybe I can try to write an editor for it.

Thanks in advance.

EDIT: I've managed to import lua script into mode9 file using m9editor.

[meltwater]

Thanks for the explaination, but I believe mode9 can also contain lua script.

mode9 content of 1a6d7b0d_manila

Right you are, I've only focused on the files I needed for my work so not looked into that. I stand corrected! :o

[hilaireg]

Can it be done manually? If yes, would be great if I could get a link to it, or is there any documentation on mode9 format? Maybe I can try to write an editor for it.

Thanks in advance.

EDIT: I've managed to import lua script into mode9 file using m9editor.

Glad you found a way to get it done.

Would be really nice to kick off a project to build a full GUI kitchen that has M9Editor functionality built in.

Great work on both your stuff btw :)

[programatix]

Glad you found a way to get it done.

Would be really nice to kick off a project to build a full GUI kitchen that has M9Editor functionality built in.

Great work on both your stuff btw :)

Would prefer to create a command line tool to extract and reattach the lua files. Would also be greatful if I can get my hand on mode9 file format. Currently I know nothing of its format, thus can't do much.

[hilaireg]

Would prefer to create a command line tool to extract and reattach the lua files. Would also be greatful if I can get my hand on mode9 file format. Currently I know nothing of its format, thus can't do much.

Send 6Fg8 a PM to see if she has any information. If you create a command line tool to reassemble the Mode9 files, I can add a function in MANILATOOL.CMD.

Cheers,

[programatix]

Send 6Fg8 a PM to see if she has any information. If you create a command line tool to reassemble the Mode9 files, I can add a function in MANILATOOL.CMD.

Cheers,

Ok, thanks.

[Co0kieMonster]

Hi,

I did a quick search but couldn't find what I'm looking for... maybe I'm not familiar with the keyword that should be used for searching.

Anyway, I'm trying to figure out how to reinsert the compiled LUA file back to mode9. I tried the attach menu in m9editor and it report that the file must be in the script folder. If I tried the import menu, it seems like nothing happened. Further more, offset shown in m9editor doesn't match the one in the name of the LUA file (I'm guessing that one of the hex in the file name is the offset).

Thanks in advance.

I see you've already managed to work everything out. But just a little clarification: When the kitchen does it's '-dec' run, it extracts embedded scripts using m9ext.exe and not m9editor.exe (it doesn't have cmd line support). So that's why the offset is a little different. If you manually export from m9editor it will give you the same offset as indicated in the app.

On a side note: If you plan on editing that script in the future, I suggest you convert it to an external script:

<Object>Type="Behavior"
<Property> Name=Script File Value=".\Scripts\script_name.luac"

It's far easier to work with and more reliable (I've had a case or two where the embedded script got corrupted on export/import).

[programatix]

I see you've already managed to work everything out. But just a little clarification: When the kitchen does it's '-dec' run, it extracts embedded scripts using m9ext.exe and not m9editor.exe (it doesn't have cmd line support). So that's why the offset is a little different. If you manually export from m9editor it will give you the same offset as indicated in the app.

On a side note: If you plan on editing that script in the future, I suggest you convert it to an external script:

<Object>Type="Behavior"
<Property> Name=Script File Value=".\Scripts\script_name.luac"

It's far easier to work with and more reliable (I've had a case or two where the embedded script got corrupted on export/import).

Thanks for the tip. I'm actually new in working with manila files. So to do as what you've suggested I'll need to:

Let say I have a lua script named, "script_name.lua"
Run manilaHASH.exe and enter ".\Scripts\script_name.luac" to get "2FC9597B_manila"
Compile "script_name.lua" as "2FC9597B_manila"
Edit the said mode9 file to have the property as the given example.


Am I correct?

Another question for Co0kieMonster, I'm porting the Home tab to VGA and I would like to increase/decrease the number of shorcuts generated by the shortcut view. I found calls to GetCount() function in the script. Increasing/decreasing it doesn't do anything much. Am I missing something?

Thanks in advance.

[j4n87]

Hi at all =)

I want to remove the weather/location of the compact flip clock from Cookie...after some request in the thread with no answesr I wanted to try it on my own =)

So I downloaded the source of cookie and found this:


HL.Clock.layoutFunctions[2] = function() -- compact layout
ClockLayoutCommon(false)

FlipClock._visible = true
AnalogClock._visible = false
ClockBackground.Size.height = 125
ClockBackground.Size.width = 421
ClockBackground.Position.value = Vector3(-210, 339, 0)
ClockBackground.Opacity.value = 100

FlipClock.Scale = Vector3Property(Vector3(0.55, 0.55, 0.55))
FlipClock.Position.x = -103
FlipClock.Position.y = 184

WeatherGroup._visible = true
WeatherGroup.Position.y = 200
Home_Weather.Scale = Vector3Property(Vector3(0.42, 0.42, 0.42))
Home_Weather.Position.x = 175
Home_Weather.Position.y = 132
Condition.MultiLine = true
Condition.HorizontalAlignment = 0
Condition.Size.width = 138
Condition.Position.x = 205
Condition.Position.y = -17
CityName.MultiLine = false
CityName.HorizontalAlignment = 0
CityName.Size.width = 200
CityName.Position.x = 0
CityName.Position.y = -17
temperature.Position.x = 275
temperature.Position.y = 80
HLable.Position.x = 347
LLable.Position.x = 347
HValue.Position.x = 345
LValue.Position.x = 345
WeatherHitArea.Position.x = 240
WeatherHitArea.Position.y = 280
WeatherHitArea.Size.width = 200
WeatherHitArea.Size.height = 125

AdjustWeatherText = function()
local testHeight = TextHelper_GetStringHeight(Condition, Condition.String)
if testHeight > 24 then
testHeight = 44
Condition.Position.y = 0
else
Condition.Position.y = -17
end
Condition.Size.height = testHeight
end
AdjustWeatherText()
end


I extracted the cab with WinCE Cab analyser to get the manile files.
The code above is in the 782FB565_manila file.

decompiled the manila file with the kitchen, cmd say then:


MANILATOOL.CMD by 12aon, hilaireg
Version: 5.05.06

: Manila file decompilation requested.
Datei nicht gefunden
: Preparing decompilation summary report.

: Total Files in Queue: 1
: LUA Complete : 0
: LUA Incomplete: 1
: LUA Error : 0


: Manila file decompilation completed.


: It is recommeded to initiate MANILATOOL.CMD with
: the '-mnf' parameter to update 'M9EDITOR.NAMES.TXT'.

: For additional help, initiate MANILATOOL.CMD with
: the '-hlp' parameter.


: Disabling '-dec' mode.

: Enabling '-mnf' mode.

C:\Users\JanD\Desktop\Manila_Kitchen>

thouht, that i could place that file in the completed folder and then recomplie it, but without success.


how edited the lua file, to remove weather and location:


HL.Clock.layoutFunctions[2] = function() -- compact layout
ClockLayoutCommon(false)

FlipClock._visible = true
AnalogClock._visible = false
ClockBackground.Size.height = 125
ClockBackground.Size.width = 421
ClockBackground.Position.value = Vector3(-210, 339, 0)
ClockBackground.Opacity.value = 100

FlipClock.Scale = Vector3Property(Vector3(0.55, 0.55, 0.55))
FlipClock.Position.x = -103
FlipClock.Position.y = 184

WeatherGroup._visible = false
WeatherHitArea.Position.x = 240
WeatherHitArea.Position.y = 280
WeatherHitArea.Size.width = 200
WeatherHitArea.Size.height = 125


greetz jan

[hilaireg]

@ALL:

I'd like to keep this thread specific to Manila CMD Kitchen functionality issues. If at all possible, please post these types of questions in one of the Social Groups below ... it's where all of the k00l kids hang out. :)

TouchFLO/Manila/SenseUI
http://forum.xda-developers.com/group.php?groupid=131

Co0kie's Beta Testing and Development
http://forum.xda-developers.com/group.php?groupid=192


Cheers,

[cnzqy1]

Another question for Co0kieMonster, I'm porting the Home tab to VGA and I would like to increase/decrease the number of shorcuts generated by the shortcut view. I found calls to GetCount() function in the script. Increasing/decreasing it doesn't do anything much. Am I missing something?


All I know about this is that you need to hex edit the HomeService.dll, but I'm not an expert, maybe Co0kieMonster can help you.

[Laurentius26]

Hi 12aon, Hilaireg, Co0kie, Meltwater, and all other people involved in Manila project.

Thank you for sharing this wonderfull work. :)

Maybe a bit late but I'm reading a lot about Manila atm and wonder where to start.
I've followed the tutorial about decompiling Manila and so far so good. :D

But now I'm stuck as I have 2 Manila files with an error in 'Workspace/_lua/error/

* 15b7fd35_manila.dis.lua
* 15b7fd35_manila.lua

The errors:

LuaDec: D:\Manila_Kitchen\_queue\15b7fd35_manila.lua:519: 'end' expected (to close 'function' at line 506) near '='

LuaDec: ...\Manila_Kitchen\Workspace\_lua\Error\15b7fd35_m anila\15b7fd35_manila.lua:519: 'end' expected (to close 'function' at line 506) near '='
Files match: 0%

The Manila packages I've decompiled are stock Manila_Core_2_5_20181527_0 coming from RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2. 15.50.14_LEO_S_Ship

Can someone please help/explain me how to fix this?
I'm a total newby and realy have no idea what I need to do to get this fixed LoL :D;)

Probably a very nOObish question. :o

Grtz,


LUA Editing

Files that have failed to decompile during the initial decompilation process typically need to be manually edited so as to address the cause of the failure. Editable *.lua Manila files reside in the .\Workspace\_lua folder and may be change with a text editor such as Notepad2.

Once the Manila file has been fixed, initiate the the LUA Comparison (luatool.exe) tool to validate that the changes made to the file are correct.

[12aon]

Hi 12aon, Hilaireg, Co0kie, Meltwater, and all other people involved in Manila project.

Thank you for sharing this wonderfull work. :)

Maybe a bit late but I'm reading a lot about Manila atm and wonder where to start.
I've followed the tutorial about decompiling Manila and so far so good. :D

But now I'm stuck as I have 2 Manila files with an error in 'Workspace/_lua/error/

* 15b7fd35_manila.dis.lua
* 15b7fd35_manila.lua

The errors:



The Manila packages I've decompiled are stock Manila_Core_2_5_20181527_0 coming from RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2. 15.50.14_LEO_S_Ship

Can someone please help/explain me how to fix this?
I'm a total newby and realy have no idea what I need to do to get this fixed LoL :D;)

Probably a very nOObish question. :o

Grtz,

Hi It's been a while since I visited this topic, and I did not think it would be ever be used. The files you are seeing apart from the <manila hashed name>.lua files are files generated when decompilation is unsuccessful.

The message you are seeing means a conditional statement wasn't closed by an 'end' statement (If condition Then code End (if)). What you need to do is try to spot these missing end statements (somewhere around line:506) and then use the COMPARE command to recheck the decompiled lua file the original (to find out if they are the same). Keep doing so until no other errors appear and you have successfully decompiled that particular lua file.

It can be a very tedious task if you run into a one of the files that the decompiler has trouble with, but it does a very good job on most. Once the file is at least partially decompiled (> 0%), you could check if they part you need decompiled right. The compiler has the ability to insert only a function, but that is an advanced topic for now. Good luck!

[Laurentius26]

@12aon,

Thank you fo the explanation. :)
When putting 'End' (without the quotes) to the 506 line in '15b7fd35_manila.dis.lua' and run 'manilatool.cmd -cmp' to compair I'm getting more lua files in the error map. :o

505) 9 [-]: GETTABLE R1 R1 K5 ; R1 := R1["OnNavigate"]
506) 10 [-]: SELF R1 R1 K6 ; R2 := R1; R1 := R1["disconnect"]
507) 11 [-]: GETGLOBAL R3 K7 ; R3 := HandleOnNavigate

I've did like this:

506) 10 [-]: SELF R1 R1 K6 ; R2 := R1; R1 := R1 End["disconnect"]

But this is just quesing.

After restoring the error file to previous settings (removing 'End') and run compair one more time I asumed the new error files would dissapear but they don't.

Do you have any other suggestions what I could learn to understand this coding?

[12aon]

I skipped the part about the disassembly file (<manila hashname>.dis.lua) because I though it might confuse you more, than it would help you.

First let me help you out, you are editing the wrong file :) only the real lua file is compared. You need to add an 'end' there (15b7fd35_manila.lua).

The disassembly file gives you an overview of the original lua's logic. You could compare it to following a route by checking the signs along the road, it isn't detailed but it gives you the general information. The same is true for the disassembly file, it tells you which code block goes where. It is always right, but hard to understand and not as detailed.

Going further into it, you can check this (http://luadec.luaforge.net/) and this (http://luadec51.luaforge.net/). You'll have to grit your teeth to get through this still a bit more ;)

[Laurentius26]

@12aon,

Thanks again, at least I understand now.

The beautifull part is that Notepad2 shows in colour if a code is placed on the right spot if I'm not mistaking.

Great, I will figure this out I think.

Not much time today anymore but hopefully I can fix it later. :)

I will start reading your suggested webpages as well. :)

[12aon]

@12aon,

Thanks again, at least I understand now.

The beautifull part is that Notepad2 shows in colour if a code is placed on the right spot if I'm not mistaking.

Great, I will figure this out I think.

Not much time today anymore but hopefully I can fix it later. :)

I will start reading your suggested webpages as well. :)

That version of notepad2 was compiled by co0kiemonster with a lua scheme ;)