This lesson will walk you through creating your first application using the GLX application framework.
When you open the glxApplicationProperties stack and no "application" stack is in memory then this screen is displayed.
You can use the Choose button or drag a folder onto the fields to specify where you would like the application to be created.
The application framework stack does not need to be stored in the same folder. For example, you might store your executable in one folder and store all application support files in a ./components folder. The application framework stack must be stored in a subfolder of the application folder however.
Click the Create New Application button to create the application files.
After creating the application it will be loaded into the Revolution IDE and the property configuration screen will be displayed.
The following files will be created in the application folder:
1) launcher.rev - This file is used to build the application executable using the Revolution Standalone Builder.
2) glxapp_framework.dat - The application framework stack which is used as a library stack.
3) application.dat - The stack that stores all application properties that you can configure. You can also store supporting libraries, etc. as substacks of this stack.
4) program.dat - The stack that contains the UI of the application. This is the stack that you can start designing your program with.
The application stack (1) is where the framework stores all application properties. This stack has a few substacks which are templates for the error dialog that appears when uncaught execution errors happen at runtime and the dialog that appears when checking for updates and an update is available. You can modify these templates to fit your needs.
The glxappLauncher stack (2) is the stack that you build an executable of using the Revolution Standalone Builder (File->Save As Standalone Application...). This stack contains no program logic.
The glxaApplicationFramework stack itself consists of one main stack and a few substacks (3). The framework will also insert one frontscript (4) which watches certain engine messages.
The program stack (5) is just a template to help you get started.
Comments (3)
If you're using the GLX2 Visual Application Browser (as I am usually), many of the stacks shown in the screen shot of the standard Application Browser do not appear.
Do you have "Show Open Stacks Only" checked in the VAB prefs? If so then the stacks that are loaded in memory but not loaded won't show up.
Yes, I did have that preference checked. Thanks for pointing it out!
Add your comment