I'm studying Zend with renewed interest recently, and am grappling with an
architecture decision for building dynamic content on my pages. It appears
that I have a couple of options for setting up my views, but lack the
experience to analyze my options well. I'm open to all of your ideas,
experiences, and preferences.
My main landing page is made up of a number of discrete modules. While the
entire page could be generated from a single view or layout, there are
filtering elements that let the end user update/filter the individual
modules from the browser. Therefore, it makes sense to me to create
individual controllers for each module.
However, for the initial loading of the page, I'm getting confused with the
use of Zend_Layout and Zend_View and how they work together.
Should I be using a Zend_Layout pattern that proxies partials somehow? Do
these go through the respective controllers via indexAction()? Do I call
view scripts for individual modules? This pattern isn't clear to me in the
docs.
Should I be using a Zend_View pattern that assigns the results of individual
view renders into the index view? Something like this...
$eventView = new Zend_View();
$this->view->eventfeed = $eventView->render('path to view script');
// repeat for each module
echo $this->view->render('index.phtml'):
I've found that the Zend documentation for individual framework modules is
very good, but there is gap when you combine modules or look at higher level
architecture strategies.
I look forward to your advice.
--
View this message in context:
http://zend-framework-community.634137.n4.nabble.com/Understanding-where-Zend-Layout-meets-Zend-View-tp3400302p3400302.html
Sent from the Zend Framework mailing list archive at Nabble.com.
--
List: [email protected]
Info: http://framework.zend.com/archives
Unsubscribe: [email protected]
