Icon Compiling Applications

When you compile an application, the Elevate Web Builder uses the project's compiler search paths along with the component library search paths to determine where to look for units and control interface files. Please see the Modifying the Project Options and Modifying Environment Options topics for more information on modifying these search paths.

Elevate Web Builder compiles the application source code (Object Pascal) into a 100% JavaScript application that will run in any modern browser. During compilation of an application, the compiler emits the following files:

Image

The HTML loader file contains all of the control interface files, form files, and database files in special tags in the header of the file.

An Elevate Web Builder application is typically loaded in a web browser via a URL that includes the HTML loader file for the application. Once the loader file is loaded in the web browser, the following steps occur:
  • The HTML loader file loads the application's .js (JavaScript) file, which causes the browser to compile the JavaScript and prepare the execution environment.


  • A special JavaScript loader function is called that initializes the application and starts execution.


  • Any control interfaces are loaded from the special tags in the HTML loader file.


  • Any auto-create forms and/or databases are created. During creation, the associated form or database files are loaded from the special tags in the HTML loader file.


  • If the web browser navigates away from the current URL, or if the web browser refreshes the current URL, then a special JavaScript unloader function is called that cleans up all allocated resources and terminates the application.
Elevate Web Builder applications are designed to be loaded and then stay loaded until they are exited. They are not "page-oriented" like many web application or general web sites. You can, however, display HTML pages within an application by using the TBrowser control that is provided as part of the component library.

The JavaScript file that is emitted by the compiler can be compressed, making the size of the resultant application much smaller. As a side-effect of the compression, the resultant JavaScript source code is also heavily obfuscated and virtually unreadable, which is desirable for many applications that wish to protect their source code. Please see the Modifying the Project Options topic for more information on compression.
Image