On Fri, 17 Jan 2003 03:12, you wrote: > >This idea has been thrown around before by Rafal Krzewski: > >------------------ > > Some time ago, an idea crossed my mind, that we might want to > > introduce another layer of templating, namely Page template. It > > would contain the common elements of all Layout templates used in > > conjuncion with VelocityOnlyLayout class. An application will use > > precisely one Page template, the same way as it uses single Page > > class now. This would bring us back to the separation between head > > and body parts of the page we had with ECS, but with template > > driven customization of head elements available to the developer. > >------------------ > > I do like that idea too for the sake of a general purpose solution. > It makes sense to me that the Page would be responsible for the > "busy-work" of the HEAD and BODY elements. However wouldn't that > make it more difficult for different template types to serve out > different types of content?
Hmmm, good point... you're right... it would only work well for generating one type of content, unless you had conditional logic in your page template, which is ridiculous now that I think about it. While you're thinking about embedding layouts within layouts and portal style applications, you should probably take a look at Jetspeed (which is based on Turbine) and the Turbine 3 pipeline. Regards, -- Rodney -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
