Click or drag to resize
Principle

The mobile engine is the next step of our framework : after creating a SQLite Engine website, it is possible to create a new mobile/Windows App.

Standard ZenengoMobile Application structure

The Zenengo mobile framework can be used as a full application, or be used as a Window/Activity/View in an existing application. But the following parts must be present to make the component work.

Database, Directories and Launching

The application must contains a full database with the standard Zenengo tables.

The website information are always stored in a special directory. The application must contain a procedure to copy on a shared directory into the device the XSL and web files.

Those steps are executed in a class implementing AbstractLaunchTask, which is most of the time created in an Activity/View/Form implementing the corresponding Abstract class.

In a standard ZenengoMobile Application, this class is used as a starting SplashScreen.

Main implementation

The next step of the application is the MainScreen, containing the special implementation of a Web Browser. The Main Screen is an implementation of a Zenengo Activity/Window/View.

The web application in itself contains all the other screens :

  • Synchronization Screens, explained in the synchronization part.

  • The application screens

Application creation steps

Before getting into the details of each steps, here is a summary of the creation steps

Website / synchronization creation

Creating a Mobile Zenengo application is at the beginning like creating a standard Zenengo WebSite.

The DoItYourself package available here, apart from the ZenengoMobilePack, contains a standard ZenengoWebsite on an SQLite database, that is pasteable to create a new ZenengoMobile application.

This site must fill the prerequisites explained in the next part.

The website must also contains the synchronization process, as explained in the synchronization part.

Parameter file creation

The next step is creating the param file, with one section per device type. The DoItYourself files contains also a file named AppParam.xml.

Since the parameters files contains all the information for each device, it's also the step when all the devicespecific information must be decided :

  • Application icons

  • Reference files

  • Device-specific C# projects to be added to the final solution

  • Assembly signing information

All the files mentioned in the configuration files must be accessible for the conversion Application.

Conversion

The conversion must be executed on an Intel MAC with OS 10 minimum. The only parameter given to the conversion Application is the parameter file.

When the conversion is done you obtain one solution per section.

Compilation and Test

The Conversion Application result is a solution for each device type. The solution contains :

  • The projects used in the first website

  • The specific projects for each device given in the configuration file

  • The main project containing the application

  • For the windows application, the installation project.

The last step is to test the application on each device and give it to the AppStore!