Organizing projects

Considerations when organizing your project, its nodes, and its files.

Application and library nodes

Whether you have a single application node or multiple application nodes will depend on what you set for the Language property.
  • If the Language property is set to Genero:

    With the language Genero, where should you store your module source? If you plan to reuse a module, place it in a library; otherwise, keep the module in the application node.

  • If the Language property is set to Genero (no link):

    When using the Genero (no link) language, you create only p-code modules; you do not create program files (.42r) or p-code libraries (.42x). This is because modules use IMPORT FGL to reference (and import) variables and functions that reside in those modules, which would otherwise reside in libraries.

    Since program files (.42r) or p-code libraries (.42x) are not created, the Genero Studio project does not require multiple application or library nodes. You can put all source modules (.4gl) under a single application node. To further organize the files, consider using virtual folders within the single application node.

    Using Genero (no link) requires a full understanding of the IMPORT FGL statement, its options, and how it allows you to build a Genero application without linking. To gain a full understanding of IMPORT FGL and how to use it in your Genero application, go to the IMPORT FGL topics in the Genero Business Development Language User Guide.

    Note:

    It is recommended to simplify the structure as much as possible!

Source code management

For information about source code management for your project, see Source Code Management (SCM).

Organizing BAM projects

For guidelines on organizing BAM projects, see BAM Projects.