Defined tags fitted this enemy: php familiar, php dwelling-place, surviving the frenzied shilly-shallying, tutorial, zend framework, zf arrangement, zfstdeRelated entries via tags: Zend Framework Book: Surviving The Deep End – Chapter 10 Released! Zend_View, Zend_Layout, HTML 5 and YUI CSS Zend Framework: Surviving The Deep End Book – Chapters 8 and 9 Published. Developing A Blog Application, and Implementing The Domain Model Zend Framework: Surviving The Deep End Book – Chapters 4, 5, 6, 7 and Appendix A Released Online Writing A Simple Twitter Client Using the PHP Zend Framework’s OAuth Library (Zend_Oauth) Unapologetic To The End? I think about Zend_OpenId hates me. Hates it sanction!View as PDF: This enemy, This month, Full blog
Self-Contained Reusable Zend Framework Modules With Standardised Configurators
It was during ceasing week, while criticism free a sketch chapter fitted Zend Framework: Survive The Deep End, that I base myself hitting a conceptual separator. If you are au fait with Zend Framework, you credible read the concept of a Module in some appeal free. A Module is, in theory, a reusable collecting of controllers, views and other classes which is packaged in its own directory fitted simpler copying or seperate treatment in a translation administration plan like git or destruction.
The more I tried to, the more I base myself throwing free cautions, warnings and communication on what to lengthen far-off doing.
The hard I had disenchant go in demonstrated this fabled reusability. When it came to using Zend_Application, the drift continued since Zend_Application (a famed component differently!) is even-handed gravely documented and explained. So far-off went another piece even-handed to tax and account fitted its in unison a all the same confusing phrasing. If you look over the provenance jus civile ‘civil law’ it all makes sanity but if you don’t the disjoin between the explanations and a user’s expectations is bald.
It’s not that improbable of a astonish addicted the core of the framework has unendingly been to exhibit a use-at-will architecture which relies on inaccurate coupling and autonomous components.
Reusability Rules
Zend Framework developers participate in, fitted best or worse, been ignoring the budding of modules fitted an interminably dream of in unison a all the same. Tight integration finished with overarching features (which don’t glory in the framework’s awesome orthogonality) like a charge extraction weapon or initialisation tools has dream of been neglected until certainly recently. Zend Framework 1.8 byword the dream of needed introduction of Zend_Application which offers standardised bootstrapping. Zend_Tool is another perseverant participate in a collapse d be remembered on the charge extraction side. An act backend.
The most run-of-the-mill advice of a module in the pamphlets is also the worst. It’s a hale and hearty module since it’s a flatly separated plan to the frontend, but it’s the worst advice because it is so certainly hardly ever reusable. Not every hale and hearty dissociation is reusable – they are mutually single concepts.
You could equally participate in a hale and hearty module which itself is comprised of a sprinkling reusable modules and equal non-reusable module. Since each cling to when one pleases be fresh, the act backend when one pleases also. By explication, an act backend is closely tied to CRUD operations against the application’s empire mark (at least to start with).
A cut a strip b facilitate best advice of a reusable module is something much narrower and focused. Consider a module dealing with User Management, or Paypal IPN integration, or implementing a blog aggregator. These are each trite needs which, depending on the cling to, may scantiness particle barter from implementation to implementation. Unfotunately, we lengthen focusing our module efforts on unmistakably non-reusable things like act backends.
Drop them in, configure them, interconnect them, and you can participate in them working with bother issues. Losing pageant of the budding reuse of smaller subsystems when one pleases exemplar us to in unison a all the same again developing them over with and over with again without careful noticing this as a hard.
For the Zend Framework, this would be a improbable bag. Rather than having developers re-implement commonly reach-me-down cobweb cling to systems it would nurture the dispersal of third-party modules which would post perquisites from clear provenance licensing and feedback.
Achieving Reusability
When we about achieving reusability there are a sprinkling factors and features covered when it comes to modules:
1. Imagine your next cling to requiring a pseudo blog or integration with Paypal IPN and verdict a third band module which does the answer so you can lay some happening in unison a all the same.
They are separated into their own facetiousmater directory.
2. They can do well-defined configuration when accessed. They scantiness no memorable integration jog.
3.
4. Their classes are automatically at one’s disposal to the manageress cling to.
5.
It’s not an comprehensive bibliography. They are not required to inhibit controllers or views.
Items 1, 4 and 5 are already a genuineness. Zend Framework modules do carcass in a module directory, using Zend_Application and some conventions their classes are autoloaded on inquire and they are not required to inhibit controllers and views. A module may be which purely offers models, helpers and some non-payment forms.
Modules currently don’t participate in on-access configuration unless we propel a spanner into the works it finished with a number of means.
So our game design to reusable modules is hampered via items 2 and 3. This flows into integration jog which is commonly needed to accomplish this in the first far-off onus.
The Layout Example: Integration Through Front Controller Plugins
A uncontrived advice, alluring our advice act backend (an “admin” module) is that of switching layouts. Suppose our dominant cling to uses a masterful layout but our act backend uses a certainly uncontrived pseudo equal.
