Java Code Generation
The text box labelled "Directory" shows where the files will be generated.
To change this either type the name of the directory directly into the text
box or press the "Browse" button and use the File Selection dialog.
Only files which are selected (or highlighted) will be
generated. To select or deselect a file, click over it. Use the Shift
key modifier to extend the selection list and the Control key modifier
to add individual files to the selection. For more details on the
files listed in this dialog, see below. The X-Designer manual explains
how to compile and run the generated code.
The button labelled "Options" displays the general code generation
options dialog where you may change the name of the application class
and indicate where you wish resources to be generated.
The button labelled "Java Options" displays a dialog containing options
which are relevant to Java code generation.
The files which you can generate are:
- ApplicationClassName.java. This is the principal code
file for the application which is a class defining the
application. One method of this class is the "main" procedure. The
name of the file is determined by the name of the application class -
by default "XApplication". You can change this in the Code Options
Dialog.
- ApplicationClassNameLinks.java. This is the file containing
code to implement the dynamic links between widgets. You do not need
this file if you have not made any links.
- ApplicationClassNamePixmapObjects.java. If you have
specified any pixmap objects, they will appear in a separate file.
- ApplicationClassNameFontObjects.java. If you have specified
any font objects, they will appear in a separate file.
- ApplicationClassNameColorObjects.java. If you have
specified any colour objects, they will appear in a separate file.
- ApplicationClassNameStringObjects.java. If you have
specified any string objects, they will appear in a separate file.
- WidgetClassName.java. Every widget you have designated as
a Java class (from its Core Resource Panel), must have its own code
file containing the class definition. There will, therefore, be as
many of these files as there are classes in your design. Unless you
have a good reason for ignoring one of the widgets in your design, you
will always need to generate these files.
See also: