Hi Deanna,
First of all thanks for your reply. Glad i got some response here.
Maybe i don't use the paradigm it was intended, so correct me is i am wrong:
The Layout is the actually the template of my webpages with a main content
area that is controlled by
module controllers. Besides the main content area it may have some other
included areas which may be
simple included views, or rather complex like partials or other custom view
helpers.
(This isn't a paradigm misuse, is it?)
The problem is that currently i see no other way of implementing complex
includes with their own logic (accept params, call model with params, pass
to view) and dedicated view files, widgets you may call them.
You may agree that this is better done in DRY mode, where you create a
helper/widget, and then just skin it with your views (tempates) and have it
all included in the final layout which is as you stated the final assembling
point of all other sections. You can imagine all the examples / use cases
for that.
So as you see i'm not using partials as a layout for everything. But try try
to implement a rather common thing. Using action stack is not an option for
the well-known reason of performance.
Will be glad to hear any further thoughts on the topic.
Good luck.
Dmitry.
--
View this message in context:
http://www.nabble.com/Placeholder-view-helpers-in-partials-don%27t-work-for-layouts--tp24042045p24050819.html
Sent from the Zend Framework mailing list archive at Nabble.com.
