Hi Jan, This was answered recently on the mailing list: http://www.nabble.com/Re-%3A-Re-%3A-T5%3A-Layout-question-td16448904.html#a16448904
Peter Beshai On Mon, Apr 14, 2008 at 2:25 PM, Jan Vissers <[EMAIL PROTECTED]> wrote: > Thanks Howard, > > However this doesn't work for the Component templates. It does work for > the Layout component, though. My question is what to add to other > Components, in order to maintain previewability, but without extraneous > <html> element at runtime. > > -J. > > On Mon, 2008-04-14 at 11:09 -0700, Howard Lewis Ship wrote: > > <html t:type="layout" > > xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";> > > > > On Mon, Apr 14, 2008 at 11:02 AM, Jan Vissers <[EMAIL PROTECTED]> > wrote: > > > Hi, > > > > > > Using > > > http://tapestry.apache.org/tapestry5/tapestry-core/guide/layout.htmlI > > > have a setup where the layout component uses a couple of other > > > components. All of which have: > > > > > > <html xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";> > > > > > > at the top - to keep a certain degree of previewability. However this > > > results in multiple <html> elements being rendered in the actual > runtime > > > content. Is there someway around this? > > > > > > Thx, > > > -J. > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
