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 > >
