Trace:
Differences ¶
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| en:about [2006/09/01 14:41] – doubleface | en:about [2006/12/15 21:01] – laurent | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| + | ===== General ===== | ||
| Jelix is a framework for PHP5, whose objective is to contribute to the realization of applications or Web sites of any kind. | Jelix is a framework for PHP5, whose objective is to contribute to the realization of applications or Web sites of any kind. | ||
| Line 15: | Line 16: | ||
| - | ====== Features: ====== | + | |
| + | ===== Features ===== | ||
| ==== Original functions and characteristics ==== | ==== Original functions and characteristics ==== | ||
| Line 26: | Line 28: | ||
| * **Event system** allowing module-to-module communication. | * **Event system** allowing module-to-module communication. | ||
| * **Overload file** : it is possible to redefine some files of a module without changing the originals (DAO, templates, properties). Useful when a module is used by several applications at the same time, or to make easy the update of a third module. | * **Overload file** : it is possible to redefine some files of a module without changing the originals (DAO, templates, properties). Useful when a module is used by several applications at the same time, or to make easy the update of a third module. | ||
| - | |||
| ==== Modern functions and characteristics | ==== Modern functions and characteristics | ||
| Line 35: | Line 36: | ||
| * **Automatic system for URL generation and mapping** : no complete URL in Jelix. The framework has the responsibility to generate urls in the templates or elsewhere, according to the configuration of URL mapping defined nn actions (mod_rewrite & | * **Automatic system for URL generation and mapping** : no complete URL in Jelix. The framework has the responsibility to generate urls in the templates or elsewhere, according to the configuration of URL mapping defined nn actions (mod_rewrite & | ||
| * **PHP scripts for code generation** to execute in command liner, allowing fast creation of various files of a project (module, DAO, template, actiongroup etc) | * **PHP scripts for code generation** to execute in command liner, allowing fast creation of various files of a project (module, DAO, template, actiongroup etc) | ||
| - | * **Technical cache system** : almost all non PHP files of a Jelix project "are compiled" | + | * **Technical cache system** : almost all non PHP files of a Jelix project "are compiled" |
| + | |||
| + | |||
| + | |||
| + | ==== Traditional functions and characteristics | ||
| + | Functions which one finds in many frameworks: | ||
| + | * **The architecture of the core is MVC type** (Model-View-Controller). A coordinator handles the execution of an action according to the parameters in the URL. The possible actions are implemented in classes of jController type (controllers). | ||
| + | * **Database access abstraction layer**: jDb relies on PDO or its own classes (when PDO is not available) to reach the databases. | ||
| + | * **Localization**: | ||
| + | * **System of authentication and rights management**. | ||
| + | * Use of XML: declaration of the events, DAOs etc… That makes it possible to facilitate writing, generation and modifying these parts of a project by third-party tools, and thus to increase productivity. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ===== Your first application ===== | ||
| + | Read the [[en: | ||
