Design Deploy

How it works

One XML file, multiple results.

DesignDeploy tool takes an XML file (= the definition of your entity), uses a configuration file and renders files of différent kind for all your application. Many themes are available to produce fast your web app (ex: CodeIgniter PHP, MySQL) or mobile (ex : Android).

The main goal ofthis tool is to save time when creating your application, on repetitive tasks to the entities. Of course, CRUDs are generated, but not only.

The code is clean, maintainable ant scalable, as will do a single developer.

All themes are scalable, open to your imagination.

Themes

All themes are source-free and money-free.

Bootstrap-CI3

The new version of CodeIgniter 3 needs to have an other syntax on controlers declaration. This theme is based on the Bootstrap theme.

Bootstrap

The genrated code is ready for a web app in PHP, using the Codeigniter 3 Framework and a MySQL Database. This configuration is standard on usual web hosters.

For the Front part, the Bootstrap+jQuery stack is merged with other plugins to have a better user experiment (like autocomplete) The MVC paradigm is preserved, with a "service" layer, to group business rules.
At all, 24 files are generated per entity.

kivy-android-dark

The first theme for mobile apps!

It produces Python and SQLite scripts for the "Kivy" framework. You need to well know this Framework to understand dependencies between all files.

Rendez-vous on gitHub to view all themes.

Detail of generated files

Example of the Bootstrap theme.

XML files used to generate the code:

Album.xml : Entity to represent the comic book
LienAuteurAlbum.xml : Entity that defines th link between the comic book and the author
Auteur.xml : Entity to represent the author

These files are build manualy, or saved from a tool, like "specs" (see http://jc.specs.free.fr/).

Generated files ofer full features for the developer:

ZIP Archive of the application core, with CodeIgniter pre-configured. This file will save your time on the framwork installation. For example, a login page is already coded, (View and Controller), it remains to choose the entity that will be used to check authentication. For another example, the design of the unit test page result has been updated.
Database:
- cretab_album.sql for MySQL : the SQL script with foreign keys
- cretab_album.sqlite for SQLite3 : le SQL script for the test database
Views (a SELECT input or an autocomplete input is present to choose the related entoty ; file upload is available) :
- createalbum_view.php Object creation
- editalbum_view.php Object modification
- listalbums_view.php List of objects
- createalbum_fancyview.php Object creation with a fancy-box (code is not a sigle page, but HTML rendered into a DIV)
- createMultiselectLienAuteurAlbumFragment_view.php Portion of code to include, to add a multiselect input in a view, for the object creation
- editMultiselectLienAuteurAlbumFragment_view.php Portion of code to include , to add a multiselect input in a view, for the object modification
- jsonifyList_view.php Output in JSON of a list of objects
- jsonifyUnique_view.php Output in JSON of an object
Controllers :
- createalbum.php Controller of the object creation
- editalbum.php Controller of the object modification
- importalbums.php Controller of the mass import of objects
- listalbums.php Controller of the list of objects
Controllers in JSON (for Ajax calls or for WebServices) :
- createalbumjson.php Controller of the object creation, through a JSON call
- listalbumsjson.php Controller of the list of objects, through a JSON call
Javascript (grouping "client" features) :
- createalbum.js JS called in the object creation view
- editalbum.js JS called in the object modification view p
- listalbums.js JS called in the object list view
- createalbum.fancy.js JS called in the object creation fancy-box
Language files (i18n) :
- messages_album_lang.php Messages in your app
Helper (also called "services" in Java-like Frameworks, accessing to the database) :
- album_helper.php Helper CodeIgniter to access the database (MySQL and SQLite3)
Models ( also called "DAO", with NO business code) :
- album_model.php Model of the object
Unit Tests (Controller, called from a browser or wget, curl, etc.) :
- albumtest.php Controller of unit tests over one single entity

Example of screens :