Fig. 126: Generating a java class
Per default, eva/3 Application Builder are saved in an xml format with the file ending .form.
Since eva/3 Application Builder version 1.4.59 forms can additionally be saved as java classes.
Is an eva/3 Application Builder application been started, the java class will be used privilegly
to load the form. There is also the possibility to write own code into the created class.
Hint: If the code should be every time created while saving a form, just
activate the option Generate Java Code (see System properties)
The java class will be created in a package which is named like the folders where the form file resides.
The created java class extends the class SFrame. If the form should be opened as a dialog, the extension
SFrame should be changed to SDialog.
The whole form setup are performed within the public void init() method. This method should not be edited because it is recreated any time the form is saved. All the other existing method can be edited without getting lost the code changes.
Own java code is protected and won't be overwritten by the code creation process excepting
the public void init() method. Own code can be placed
at different places:
The Methodpublic void afterLoading():
The super.afterLoading already existing should not
be changed. It's the best way to place yout code below this statement, because the
accurate form initialization could not be garanted otherwise.
The Constructor:
The constructor should always contains the method invoke statement public void init().
The method public static void main(String[] args):
This method can be used for starting the form directly but it will not be used by eva/3 Application Builder.
If you're using this method to start your application, this is also a good place to write some code.
To create java classes for several form files, the context menu can be used to start the creation process without opening the form designer. Several folders or form files can be selected. (s. fig. 126 )
Working with Forms