Basic settings in main editor
The canvas of the main editor corresponds to the modeled application. Some basic settings should be defined here. We click on the canvas and see the options in the properties view.
The possible choices for the application type field are: Web, Native and Embedded. In version 0.5 this field is not yet used; it is intended for functionality that will be available in the future. The default value, Web, should be used.
The fields author and email store the name and the email address of the developer. Another field allows one to specify an interactive installation. This is deactivated by default, so that a normal installer is generated; one that does not require user interaction. The license field specifies under which license the application is developed. Here GPL is the default, but this is probably going to be changed to LGPL in future.
In the Model path field the file path to the mostapp model is stored. This is necessary for the generator to find the model to be processed. As long as the model has not moved, no changes are needed here. If one works with a foreign model, the path likely must be changed to get the generation process to succeed. The fields name and prefix define the name of the application as well as the prefix for the created database tables.
The next field allows other applications to be referenced by shortcuts. This is will be implemented in the future to enable calls to API functions of other applications. For now, it is not used. The project home page is stored in the URL field, and the version field defines the version number of the application.
After all basic data have been specified, typically the data model definition follows.
Tags
Comments
Graphical…
In future versions of ModuleStudio the graphical editors are going to grow further. This will make the management of… >read more
Using the generator
In order to use the generator there must be a model open in the main editor, and it must not have any validation… >read more
Connector
In the course of our work on a modular system for ecommerce applications , the need to import and export different… >read more
Describing the model
This screencast shows how one creates a model, which is the data layer for an application. With the model we define… >read more
Leisure facilities
The leisure places directory allows one to manage a catalog of facilities and institutions which can then be searched… >read more
Customise palette
The palette in ModuleStudio can be customised in several ways. This video points out the different possibilities. If… >read more
Creating…
Sometimes one wants to create multiple elements of the same type. In such cases, it is annoying having to go to the… >read more
ModuleStudio 0.5
It is finally here, the ModuleStudio 0.5 release! This version brings many visible and invisible innovations and has… >read more
Doctrine in…
The core version 1.3 of Zikula now ships the ORM layer called Doctrine . Because of this we completely overhauled… >read more
Zikula 1.3…
The Zikula Project is going to publish a great release with version Zikula Core 1.3. The new release frees the… >read more

No comments posted yet.
Only logged in users are allowed to comment. Register or log in.