> > > Have you at least tried to use the mixin without any other changes to your > component and see what happens?
By that I assume you mean just to define the mixin? Yea I have tried that nothing happened :( I guess then I will have to go with some custom logic that will identify what is the element that needs to receive this and then to add it using ComponentResources.**renderInformalParameters(): On Wed, Jun 26, 2013 at 12:00 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Tue, 25 Jun 2013 18:50:25 -0300, Boris Horvat <horvat.z.bo...@gmail.com> > wrote: > > I need to make sure that I "manually" render an element and then to close >> it. >> > > This is up to your code. The easiest way is to return a Block or component > instance in beginRender(). > > > This will allow I guess to the mixin to do its magic. There is no >> mention of the afterRender() so I am not sure how to use it. >> > > You don't need afterRender() for RenderInformals to work. > > Actually, what you need is the JavaDoc for ComponentResources.** > renderInformalParameters(): > > "Indentifies all parameters that are not formal parameters and writes each > as a attribute/value pair into the > current element of the markup writer." > > Have you at least tried to use the mixin without any other changes to your > component and see what happens? > > > The only thing I can come up is to create this writer call for each one >> of my fields? >> > > I have no idea what you're talking about here. > > > -- > 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 > > -- Sincerely *Boris Horvat*
