-
|
«
|
March
2010
|
»
|
| Su |
Mo |
Tu |
We |
Th |
Fr |
Sa |
| 1 | 2 | 3 | 4 | 5 | 6 |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 | | | |
|
Build System
Single or Project, Incremental or Full Rebuild
|
|
When developing, updating and testing applications, your developers can choose how many files need to be built or compiled. 'HydraStudio' gives them the following options:
|

|
|
individual file compilation
|

|
|
incremental project compilation
|

|
|
full project rebuild
|
Application Build Failure
|
|
If an application fails to build because of a coding or linking error, the corresponding project modules will be shown with a red cross, over their icons in the project tree. 'HydraStudio' should also produce an error message within the corresponding source code.
|

|
Failed Forms Won’t Stop Application Build
|
|
'HydraStudio' 4.2 does not stop building the executable just because a form file fails to compile. The build will continue, and 'HydraStudio' will display an orange check mark against the program icon in the project tree.
|

|
Target Database Selection for Build Validation
|
|
When you are ready to compile your programs, you can chose which target database is to be used for the validation. The list is created by 'HydraStudio' from all the database installations that it recognizes on the local machine.
|

|
‘.def’ Files Auto-Generated for Command Line Builds
|
|
If you prefer, or need, to build your projects with ‘make’ files, at the command line in a Unix/Linux environment, 'HydraStudio' can generate and export ‘make’ files for you.
Right-click your program name in the project tree and select ‘Export .def File’ from the menu. Enter a file name in the dialog box and click the OK button to create a .def file. You can then use the .def file to compile your program using 4make.
|
|
All the 4GL compiler option flags can be set in the 'HydraStudio' graphical interface, including an Informix 4GL compatibility mode.
|

|
Form Compiler Flags for fmpc
|
|
In the same way as for 4GL files, flags for compiling form files can be set in a graphical interface.
|

|
Release & Debug Mode, Debug Communication Log File
|
|
Switching 'HydraStudio' into Debug mode creates an application log file, which records the details of communication between the client and the server, including original source SQL and translated target database SQL. You will also have to make an entry of "QXDEBUG" in the environment. Here are the two most commonly used values of QXDEBUG: '!' = Gui trace 'UuBbSe' = SQL trace
|


|
Application Launch in 'HydraStudio'
|
|
Once it is built, 'HydraStudio' can deploy your current program to the application server. You are then given a choice of client on which to run your application. Just double-click the program name in the project tree, then select your client from the dialog box.
|

|
|
If you need to run the same program again, using the same client, simply click the Re-Run Last Program icon in the 'HydraStudio' menu.
|

|
Save Command Line Arguments
|
|
When you select one of your programs in the project tree, an Arguments field is displayed in the Properties region. You can save command line arguments for your program by entering them into the Value field for Arguments in the Property list. These arguments are saved with the project.
|

|
|
|
«
|
March
2010
|
»
|
| Su |
Mo |
Tu |
We |
Th |
Fr |
Sa |
| 1 | 2 | 3 | 4 | 5 | 6 |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 | | | |
|