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:tutorial:application-creation [2006/09/20 15:45] – doubleface | en:tutorial:application-creation [2006/11/08 11:05] – (old revision restored) 127.0.0.1 | ||
---|---|---|---|
Line 33: | Line 33: | ||
set JELIX_APP_NAME=actu.org | set JELIX_APP_NAME=actu.org | ||
</ | </ | ||
+ | |||
Line 55: | Line 56: | ||
Check that the temp/ | Check that the temp/ | ||
+ | |||
+ | |||
+ | ===== Creation of a module ===== | ||
+ | |||
+ | Now that we have a skeleton of application, | ||
+ | |||
+ | The actions are grouped in distinct modules according to the domain, the fonction to which they are linked. We will for example create a module which will group the actions meant to display and manage the news. To do that, you have the createmodule command, which takes as parameter the name of the module that will be created. | ||
+ | |||
+ | <code bash> | ||
+ | php jelix.php createmodule news | ||
+ | </ | ||
+ | |||
+ | By typing this command, Jelix has created for you a module named news with all its tree structure and some mandatory files : | ||
+ | |||
+ | | ||
+ | news/ the directory of the module | ||
+ | module.xml | ||
+ | actions.xml | ||
+ | controllers/ | ||
+ | | ||
+ | classes/ | ||
+ | daos/ the object-relationnal mapping files | ||
+ | locales/ | ||
+ | en_EN/ | ||
+ | fr_FR/ | ||
+ | templates/ | ||
+ | zones/ | ||
+ | |||
+ | We are now ready to define the actions. | ||
+ | |||
+ | ---- | ||
+ | * Next : [[en: | ||
+ | * [[en: |