You are by no means tied to using one layout. You can switch which response segment the action
renders to, and even which layout script to use at any time in an actions execution process.
On 18/01/2009 11:43 PM, Cameron wrote:
Oh, well that sounds like what I'm looking for. I'll have a look
Hi guys,
I have an application that is growing piece by piece, table by table, and as
it grows, as do the number of view scripts the application needs. In order
to ease maintenance on these, I've managed to make the vast majority of the
views indentical across controllers, by just passing the
Action Helpers are really dependent upon what you are trying to do.
Something that's static I would render out using partials. However, if
you're doing a bit of output processing (nothing static), I would
recommend using an Action Helper. :-)
--
Chris Weldon
On Sun, Jan 18, 2009 at 11:17 PM,
wouldn't view partials still require the view script to exist? I was trying
to avoid having the actual files there too. Infact, the perfect solution
would be to override if the file does exist.
On Mon, Jan 19, 2009 at 3:32 PM, Chris Weldon ch...@chrisweldon.net wrote:
Action Helpers are really
Not necessarily. You can put one partial in a single location. I have
the following structure for my applications:
application/
layouts/
views/
scripts/
modules/
agency/
views/
scripts/
I have scripts located in both the layouts/, views/scripts, and
Oh, well that sounds like what I'm looking for. I'll have a look at view
partials too.
And Zend_Layout isn't going to work out, each view per action is quite
different. Ergh. I mean... maybe I could, but there'd be so much if-then
logic to accomodate the differences it'd rapidly turn in to a
