On Thu, 16 Jan 2003 03:55, you wrote: > I had added a hack^H^H^H^Hfeature to my customized Layout to enable > layouts to be embedded within other layouts. This way you can have a > standard layout containing just the basic HTML HEAD and BODY tag > stuff, and then reuse that layout in other layouts. <snip> > Note that the embedding does not involve looking up the Layout class > for the template that is being embedded in. This is only for reusing > content. > Does this idea appeal to anyone for general use in Turbine?
I think I'm missing something, but can't you just embed a Navigation template with the "basic" stuff mentioned above into the header and footer parts of your Layout templates? Could you explain why you need to embed a Layout into another Layout? 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. ------------------ > On a related note, I think it would make sense for "navigations" to > be available within the screens. This would make it much easier to > create widget-like templates with smart functionality that can be > reused throughout the site. It would be akin to portlets in a sense. Sounds like a good idea... we've been using the #parse Velocity directive for this, preceded by a bunch of #set directives to set up the context for the template to be parsed. -- Rodney -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
