informatique:php:zend_framework
Différences
Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédenteProchaine révisionLes deux révisions suivantes | ||
informatique:php:zend_framework [09/09/2009 18:09] – cyrille | informatique:php:zend_framework [06/11/2009 14:15] – cyrille | ||
---|---|---|---|
Ligne 37: | Ligne 37: | ||
* [[http:// | * [[http:// | ||
* PHP Performance Tips from Stas Malyshev: On his blog, Stas Malyshev (Core Contributor to PHP and Zend Employee) has posted a [[http:// | * PHP Performance Tips from Stas Malyshev: On his blog, Stas Malyshev (Core Contributor to PHP and Zend Employee) has posted a [[http:// | ||
+ | * [[http:// | ||
===== Plugins ===== | ===== Plugins ===== | ||
Ligne 69: | Ligne 70: | ||
On notera un objet de requête, un objet de réponse, un ensemble d' | On notera un objet de requête, un objet de réponse, un ensemble d' | ||
Notez que FC ne touche pas à l' | Notez que FC ne touche pas à l' | ||
+ | |||
+ | Controller Workflow Summary: | ||
+ | * Zend_Controller_Front - manages the overall workflow. | ||
+ | * Zend_Controller_Request*- accessors for controllers and actions (and status .. e.g. already dispatched) | ||
+ | * Zend_Controller_Router - exactly once per request, calculates correct controllers and actions based on environment in Zend_Controller_Request | ||
+ | * Zend_Controller_Dispatcher - transfers flow of execution to controllers and actions in request object (Zend_Controller_Request*). Process repeats until no more actions are scheduled. | ||
+ | * Zend_Controller_Action* - userland controller classes containing userland actions | ||
+ | * Zend_Controller_Response* - contains the output of the executed actions | ||
Le processus complet du MVC de Zend Framework peut être résumé à ce plan là : | Le processus complet du MVC de Zend Framework peut être résumé à ce plan là : | ||
Ligne 179: | Ligne 188: | ||
Doc Zend_Form [[http:// | Doc Zend_Form [[http:// | ||
+ | |||
+ | * [[http:// | ||
+ | * [[http:// | ||
=== Exemples === | === Exemples === | ||
Ligne 272: | Ligne 284: | ||
[[http:// | [[http:// | ||
> Zend_Form est un composant touffu, mais très puissant. Plus encore que d' | > Zend_Form est un composant touffu, mais très puissant. Plus encore que d' | ||
+ | |||
+ | === Using Zend_Form in Your Models === | ||
+ | |||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
=== Database backed Zend_Form elements === | === Database backed Zend_Form elements === | ||
Ligne 417: | Ligne 435: | ||
Use of [[: | Use of [[: | ||
- | * | + | * [[http:// |
Ligne 443: | Ligne 461: | ||
> That said, you will more than likely have to get the module directory from the front controller, then iterate that to find the modules. Once you have the modules, you'll have to find the *Controller.php files inside the controller directory of each module. After that, if you want the actions, reflection is the best way to go: looking for any methods that are public and end in ' | > That said, you will more than likely have to get the module directory from the front controller, then iterate that to find the modules. Once you have the modules, you'll have to find the *Controller.php files inside the controller directory of each module. After that, if you want the actions, reflection is the best way to go: looking for any methods that are public and end in ' | ||
+ | Solution dans http:// | ||
+ | |||
+ | Je me suis écrit une classe [[/ | ||
+ | |||
+ | ====ZF & ORM==== | ||
+ | |||
+ | You should take a look at **Doctrine 2**. As **Zend Entity** it implements the **JPA specification** and is a true data mapper with models decoupled from Database completly. | ||
+ | |||
+ | Sur cette page http:// | ||
informatique/php/zend_framework.txt · Dernière modification : 19/05/2012 00:18 de 127.0.0.1