Outline and Essential Particulars
From the patch version of February 2012, Server Compile method is changed to Local Compile method for compiling speed enhancement. That means, compiling was conducted in Server previously but is conducted in Client (PC) from the patch version. The existing Server Compile method transfers *.xadl and *.xfdl to be compiled in UX-Studio to Server and Server Compile Module compiles the transferred files and creates *.js files in Server. However in the changed Local Compile method, UX-Studio calls XjaxCompiler.exe, the Local Compile Module and this module compiles *.xadl and *.xfdl and creates *.js files in Client. Local Compiled file names are identical to those of Server Compile method.
Essential Particulars related to Local Compile can be organized as below.
There is no alternation in a method to compile in UX-Studio using HTML5 menu.
File name for Actual Local Compile Execution Module is XHTML5ompiler.exe.
When compiled in UX-Studio, the actual compile is not carry out by UX-Studio but by XHTML5ompiler.exe.
Yet, XHTML5ompiler.exe must be in the identical folder when UxStudio92.exe is located in, that is, it must be in “C:\Program Files\TOBESOFT\XPLATFORM\9.2\” in order to make compile available in UX-Studio.
Folder where compiled files shall be located is set in UX-Studio > Tools > Options > HTML5 > Compiled Path.
Compiled file names are identical to those of the existing Server Compile method.
Yet, as compiled output such as *.js is saved in Client, the output must be manually moved to a location where execution in web server is available. If the web server works in Client, make output location identical to web server path in UX-Studio. This will be automated in the future.
Files to be compiled | Compiled Files | Description |
---|---|---|
LaunchProject.jsp | Initial HTML file to be run in WebBrowser | |
QuickView.jsp | HTML file to be run when QuickView is executed. | |
*.xadl | *.xadl.js | ADL file |
*.xadl.debug.js | ADL file for debugging | |
/Service /*.xfdl | /Service /*.xfdl.js | FDL(Display) file |
/Service/*. xfdl. debug.js | FLD(Display) file for debugging | |
__theme__/…/*.css | __theme__/…/*.css.js | CSS file of theme |
__theme__/…/*.png,… | __theme__/…/*.png,… | Image Files, file name remains the same when compiled |
How to use XHTML5Compiler.exe
XjaxCompiler.exe can be directly used in a consol by using options illustrated in table below.
XHTML5ompiler.exe Options
Options Below can be used regardless of input sequence.
Option | Description |
---|---|
-A (ADL) | Option for setting save path of XADL file of the project compiled. ※ This option must be input. |
-O (Output) | Option for setting save path of files for compiled product. If path entered with ‘-O’ option does not exist, the option shall be created automatically during compile process. ※ This option must be input. |
-P (Project) | Option for setting title of project compiled. Name entered with ‘-P’ option is applied additionally to entry value of ‘-O’ option and decides save location of compiled file. If ‘-P’ option is not input, the title shall be saved automatically as XADL file name entered with ‘-A’. |
-R (RootPath) | Option for setting root path of project compiled. If the entire project compile is conducted, compile object files are searched based on standard of a path entered with ‘-R’. And save path for compile output files are also saved in relative path of ‘-O’ option according path entered with ‘-R’. If ‘-R’ option is not entered, the path will be set as XADL file path entered with ‘-A’. ※ Entry Value of ‘-R’ option must be identical to XADL file path entered with ‘-A’ or be entered as a upper path. |
-S (ServiceID) | Service ID option to be used in case entering a specific service path of project compiled. Service ID entered with ‘-S’ can necessarily use Service ID defined in TypeDefinition. ※ ‘-S’ option is an additional compile option and cannot be used together with ‘-F’ option. |
-F (Files) | Option to be used in case compiling only specific files in project compiled. It can be multiply entered by diving with ‘,’ or with ‘ ‘. |
-L (Log) | Options for saving compile progress process as a log file. In case using ‘-L’ option, required compile time can be somewhat increased. |
-H (Help) | Help option that informs options supported in XHTML5ompiler.exe. Help is generated in a consol window only. ※ As ‘-H’ option is applied preceding all the other options, compile action is not performed when the option is sued with another option. |
Examples of using XHTML5ompiler.exe
Incase compiling the entire project with a specific XADL file
Classification | Usage Example |
---|---|
Case Example | Compiling the project with a standard of ''C:/HTML5Project/Compiled.xadl' file and output in 'D:/ResultCompile' |
Consol Input | ./XHTML5Compiler.exe -A 'C:/HTML5Project/Compiled.xadl' -O 'D:/ResultCompile' |
Output Result | D:/ResultCompile/Compiled/Compiled.xadl.js D:/ResultCompile/Compiled/… |
In case that the entire project must be compiled with a specific XADL file but the project title has to be changed as the compiling XADL file is additionally created from the project
Classification | Usage Example |
---|---|
Case Example | Compiling the project with a standard of ''C:/HTML5Project/CompiledAddition.xadl' file and output in 'D:/ResultCompile'. Yet, the project is compiled in the same way above. |
Consol Input | ./ XHTML5ompiler.exe -A 'C:/HTML5Project/CompiledAddition.xadl' -O 'D:/ResultCompile' -P 'Compiled' |
Output Result | D:/ResultCompile/Compiled/CopiledAddition.xadl.js D:/ResultCompile/Compiled/… |
In case the entire project must be compiled with XADL file but the compiling XADL file does not exist on root path of the project
Classification | Usage Example |
---|---|
Case Example | Compiling 'C:/HTML5Project' project with a standard of 'C:/HTML5Project/XADL/Compiled.xadl' file and output in 'D:/ResultCompile'. |
Consol Input | ./ XHTML5ompiler.exe -A 'C:/HTML5Project/XADL/Compiled.xadl' -O 'D:/ResultCompile' -R 'C:/HTML5Project' |
Output Result | D:/ResultCompile/Compiled/XADL/Compiled.xadl.js D:/ResultCompile/Compiled/… |
In case that compiling specific service path of the project only with a standard of a certain XADL file
Yet, when services are assigned project info including XADL, TypeDefinition, and Global Variable are not compiled.
classification | Usage Example |
---|---|
Case Example | Compiling ‘Base’ service of the project only with a standard of 'C:/HTML5Project/Compiled.xadl' and output in 'D:/ResultCompile'. |
Consol Input | ./ XHTML5ompiler.exe -A 'C:/HTML5Project/Compiled.xadl' -O 'D:/ResultCompile' -S 'Base' |
Output Result | D:/ResultCompile/Compiled/Base/… D:/ResultCompile/Compiled/Base/….. |
In case that compiling specific files of the project with a standard of a certain XADL file.
Yet, when specific files are appointed, project information such as XADL, TypeDefinition, and GlobalVariables shall not be compiled.
classification | Usage Example |
---|---|
Case Example | Compiling 'Base/Form01.xfdl' and 'Base/Form02.xfdl' only with a standard of ''C:/HTML5Project/Compiled.xadl' file and output in 'D:/ResultCompile'. |
Consol Input | ./ XHTML5ompiler.exe -A 'C:/HTML5Project/Compiled.xadl' -O 'D:/ResultCompile' -F 'C:/HTML5Project/Form01.xfdl', 'C:/HTML5Project/Form02.xfdl' |
Output Result | D:/ResultCompile/Compiled/Base/Form01.xfdl.js D:/ResultCompile/Compiled/Base/Form02.xfdl.js |