The answer is quite easy if you are up for a bit hacking. Just define a block around the part you want to write raw. Then provide a special render method for the block you want to write differently. And when tapestry wants to render the block, just open the template file yourself and read everything inside the block tags by hand. Once you optained it just use a raw write instead writing the given block. This way you can mark something transparently and include it in raw output. Check out the user guide for that.
The fun part is that tapestry cuts out the part inside the block for you so you really only have to take care about the block writing. Cheers, Martin (Kersten), Germany 2013/9/27 Barry Books <trs...@gmail.com> > OutputRaw does not do the same thing because it does not support parameter > expansion, but you are correct there are potential issues with this > approach. > > I can't use the outputRaw component here because the data is the template. > > It does let you do things like this > > <t:dynamic template="prop:template.resource"> > > <p:classes> > > <t:form> > > <t:select t:id="item" model="itemSelectModel" validate="required" /> > > <t:submit value="Add To Cart" /> > > </t:form> > > </p:classes> > > </t:dynamic> > > > Which allows the page to contain any content and place the order form > anywhere on the page. > > > > > > > On Fri, Sep 27, 2013 at 10:36 AM, Thiago H de Paula Figueiredo < > thiag...@gmail.com> wrote: > > > On Fri, 27 Sep 2013 12:31:01 -0300, Barry Books <trs...@gmail.com> > wrote: > > > > The long story is I have a CKEditor component that allows site admins to > >> select content on a page and edit it. I do this with the Dynamic > >> component. > >> > > > > I'm not sure Dynamic, which is basically Tapestry templates loaded from > > any place, is a good choice for including stuff written by non-developers > > in a WYSIWYG editor. I'd use OutputRaw instead of dynamic templates, not > > inside them. By the way, you said OutputRaw doesn't work inside dynamic > > templates, but didn't really explain what you meant by that. > > > > Of course, I don't know well your scenario, so my suggestion here may not > > the best for it. > > > > -- > > Thiago H. de Paula Figueiredo > > > > ------------------------------**------------------------------**--------- > > To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org< > users-unsubscr...@tapestry.apache.org> > > > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > >
