Application
copy linkThe application object represents an application in Java or Microsoft .NET architecture. Depending on the type, it is represented by the following icons:
![]() |
Web desktop application |
![]() |
Mobile application |
![]() |
Batch service application |
![]() |
Web service application |
![]() |
Component application |
To create new applications, use the project object context menu.
Video course: Web application object
Properties
Name: represents the name of the application, as it will be identified within the Instant Developer project. It cannot be the same as the names of database objects or of other forms, because it is used (without spaces) to generate the names of the class files that will contain the source code.
Description: contains a meaningful description of the purpose of the application. The text entered will be used to compose the user manual.
Caption: represents the default value of the MainCaption property, used as a caption for the application's header and login form. It is normally left blank, in which case the Name property will be used.
Technology: This property specifies the target technology in which the application will be compiled, either Java or .NET.
Keep compatibility: If this flag is set, In.de allows use of the specific functions compatible between Java and .NET. All functions of the standard In.de library are compatible, so this flag is only used for extension of the library by the developer.
Enable offline mode: If this flag is set, the application is compiled to allow use in offline mode. In this mode, the entire application (the server and graphics engine) are compiled in Javascript and are downloaded onto the device where the application is run. For more details on developing offline web applications, refer to Chapters 1-5 of the Instant Developer book that covers mobile application development.
Architecture: represents the type of application. It is not possible to switch from one type to another.
Template directory: specifies which directory contains the template files for generating the application code. If the value starts with $ID, it means that the path starts with the In.de installation directory and the value will be automatically managed based on the technology and architecture chosen. Changing this setting is not recommended.
Custom directory: specifies which directory contains the files for customizing the template. Usually left blank, if the template is not customized, or if it contains a directory relative to the project file, such as ./custom.
Web application object video course
Output directory: specifies which directory should contain the application source files generated by In.de and then compiled into the target technology for testing the application. It usually specifies a path relative to the project file. The default value is automatically managed by In.de based on the technology and architecture chosen.
Help file: if the online manual is not created automatically by In.de, you can specify the path to an html file to open when the user presses F1 in the user interface and there are no forms open.
Start server session: Specifies whether it is necessary to automatically start an initial server session when the web server is started. This setting is normally used if the web application requires a "worker thread" common to all sessions used, e.g., as a communication channel between sessions or simply to perform tasks asynchronously.
Startup URL: For web applications, you can specify a startup URL different from the standard one calculated by In.de. You can also specify just a query string if the value of the property begins with ?, for example ?CMD=TEST launches the application from the standard URL immediately sending the TEST command.
Package: for component applications, you can specify the name of the namespace (for C#) or the package (for Java) that contains all the component's classes.
Export sources: If this flag is set, when the components are exported, In.de also inserts the source in the IDZ file generated during the export. This way, users of the component can see them and, if necessary, adapt them to their needs.
Path: a path specifying the physical location of the component. Is automatically set by In.de when the component is imported or exported. When importing, the path specifies the location of the IDZ file used for the import. When exporting, the path specifies where to export the component.
Version: allows you to specify the version of the component before it is exported. If left blank, the component has no version.
Demo: specifies whether the component is to be exported in Demo mode. Web applications that use components in Demo mode at any level are also opened in demo mode.
Both technologies: specifies whether the component should be exported in both technologies (C# and Java). If the flag is not set, In.de exports the component in the technology set at the time of export.
Menu type: specifies the style of the application's main menu. The possible values are:
- Side bar (left): the application's main menu appears as a vertical window docked to the left side of the browser (side bar).
- Side bar (right): the application's main menu appears as a vertical window docked to the right side of the browser (side bar).
- Menu bar (top): the application's main menu appears as a standard Windows-style drop down menu.
- Task bar (bottom): the application has a Windows-style taskbar. The main menu appears as the application's start menu.
Icon: represents the application icon that appears on the start page. This property is only used for mobile applications.
Visual properties: the following flags enable or disable standard buttons or features of the application bar:
- Show header: allows you to show or hide the entire caption bar of the application.
- Menu button: shows or hides the button to expand or collapse the main menu.
- Show icon: shows or hide an application icon.
- Show caption: shows or hides the caption of the application.
- Command field: shows or hides the field for inputting commands to the application.
- Close button: shows or hides the button to close the application.
- Help button: shows or hides the button to open the user's guide window.
- Debug button: shows or hides the button to open the debug window.
- Active icon: if set allows the user to click on the application icon which will receive the OnCommand event.
- Ajax indicator: shows or hides the communicating with server indicator.
- Show toolbar: shows or hides the entire commands toolbar.
- Show status bar: shows or hides the entire status bar.
Generate RTC data: specifies that for this application, the data relating to the runtime configuration module should be generated if the RTC module is enabled when compiling the application.
Generate user manual: specifies that during publication of the application, an automatic user manual will also be created.
Enable trace: specifies that during publication of the application, the Trace module should also be enabled.
Project name: represents the physical name of the project and is used as the name of the .aspx file and the solution in C# and of the webapp in Java.
Automatic: specifies that the project name is automatically calculated and made unique based on its logical name.
Shared instance: Valid for components, indicates whether an instance of component can be reused multiple times in a complex hierarchy of components in an application. Further information is available in this article.
Context menu
Add table: adds a new IMDB table to the application. A database table can also be dragged onto the application to create one in memory with the same structure.
Add procedure: adds a global procedure to the application, callable from all forms and classes. It is generally not a good idea to create too many global procedures. A better approach is to use static classes and functions to create function libraries that can be used anywhere in the application.
Add command set: adds a command set to the application. It will be displayed as part of the main menu or as a toolbar depending on the properties. If Task bar is selected as the menu type, then a toolbar command set will appear as a quick launch area in the task bar.
Add indicator: adds an indicator to the application status bar, usually displayed at the top, below the header. If Task bar is selected as the menu type, then the indicator will appear in the tray area of the task bar.
Add timer: adds a new timer to the application.
Add form: adds a new form to the application. You can also create forms by dragging and dropping the database tables or document-type classes onto the application while pressing Shift.
Add role: adds a new role (or application profile) to the application, at the base level.
Add class: adds a new class to the application. To create document classes, you can drag&drop the database tables onto the application while pressing Shift+Ctrl.
Add global variable: adds a global variable at the application level. To create global variables, you can also drag&drop database fields onto the application to create variables that are already linked to the value of the field.
Events: this submenu allows adding procedures to handle events raised by the application. For more information on the events available, refer to the Application library.
Wizards: this submenu can be used to activate wizards, in this case corresponding to the application. Here, the Configure parameters wizard allows you to change the various framework parameters.
Add folder: adds a folder inside the application, which will have no impact on the source code, but can be used to better organize the objects in the application.
Add task: creates a new task object linked to the application. It serves as a reminder for future changes or to manage group work.
Find derived objects: searches for all objects in the project derived from the application, including at multiple levels.
Find where used (object): searches for all points in the project where the application is directly referenced in any way.
Find where used (content): searches for all points in the project where the application or one of the objects it contains is directly referenced in any way.
Export component: exports the component to an appropriate file that can be used to import the component into other projects.
Recalculate layout: recalculates the layout of all the panels in the application.
Delete useless columns: analyzes all the application's queries and deletes unnecessarily selected columns, which optimizes performance and memory usage. This command is useful, because as the application grows, you may forget about columns selected in the query but no longer referenced.
Delete unused variables: analyzes all application code and deletes any local, global, and cursor variables created but no longer referenced.
Skip compiling: allows this application to be excluded from project compiling.
Enable compiling: allows this application to be included in project compiling.
An application can be dragged and dropped onto a/an...
Database, Application, Library: moves the application in the list of objects. It only serves to reorder items in the list, and has no effect on the application.
creates a copy of the application and positions it next to the target object.
Command Set: if the command set is of type toolbar and is contained in a form, dragging and dropping the application onto it sets it as the container. In other words, the toolbar will not be shown in the caption of the form, but as a toolbar of the application, displayed below the header.
Folder: if the folder is at the same level as the application, then the application will simply be moved inside the folder.
positions the application before the folder at the same level of the tree.
copies the application inside the folder.
Changed on: 15/12/2022 / From version: 8.5.3800