EiffelBuild: Code Generation
To generate Eiffel code representing your system, select Generate code from the Project menu or click on the main toolbar . The length of time taken to generate your code is dependent on the speed of the system you are running, and the size of your interface, but typically takes a couple of seconds. A progress bar is displayed during the generation of your system.
The code will be generated according to the options you selected in the project settings .
The generation of an EiffelBuild project causes the following files to be generated:
- A constants class and its respective implementation class. For example, if the constants class is named as "constants" in the project settings , two classes, CONSTANTS and CONSTANTS_IMP are generated.
- A class and implementation class for each window, dialog and "top level" widget in the system (each of which is contained in the widget selector ), named to correspond with the name attribute of the object. For example, for a window in the project named "main_window", the files MAIN_WINDOW and MAIN_WINDOW_IMP are generated.
- An optional file named "constants.txt" which contains definitions of all INTEGER and STRING constants. This is only generated if "Load constants from file" is selected in the project settings . The generated code loads the constants from this file, and allows simple modification for localization, i.e. for foreign languages provide a different version of this file with all strings converted.
For each "top level" widget class in the system (contained in the widget selector ), the following class hierarchy is generated:
If the "generate as client" option is selected for a particular object (changeable from the object editor , only for objects contained in the widget selector ), a client supplier relationship exists between the generated widget class and the EiffelVision widget, as illustrated below:
Project build type
If build type is selected as Project in the project settings , then all the classes listed above in "Generated classes" are generated, along with the following:
- A project configuration file called "build_project.ecf".
- An application class which launches the root window of the project.
The generated files comprise a complete project with a configuration file enabling you to compile and execute the generated system as is. The following diagram illustrates the hierarchy of the generated project, showing only the root window of the project:
Modifying code after generation
The choice to generate an interface and an implementation class for the windows and constants was to enable modification of the interface using EiffelBuild, once you had hand edited code. The rule is that the implementation classes are re-generated every time, but the interface classes are not. It follows from this that you should not add hand written code to the implementation classes (ending in _IMP), as any changes you make will be lost when re-generation takes place.
Using this mechanism, you can generate your initial system using EiffelBuild, and implement any event features that have been generated (in the interface) by EiffelBuild. If you then decide that you wish to modify the look and the feel of the interface, you can return to EiffelBuild, make the necessary adjustments and then re-generate the system.
Looking at a generated system, you will see that the events connected to your controls are defined as deferred in the implementation and actually implemented in the interface class. This means that if you return to EiffelBuild with a previously generated system, and add a new event to a control, then you will have to implement the definition in the interface class yourself (as the class interface class is not re-generated).