Magnus, I think you've just answered my previous threads http://tapestry.1045711.n5.nabble.com/How-does-MultiZoneUpdateEventResultProcessor-get-a-html-string-from-a-RenderCommand-td5518968.html
http://tapestry.1045711.n5.nabble.com/tml-parameter-rendered-into-a-JavaScript-string-td5512889.html#a5518439 Thanks very much!! On Wednesday, 7 March 2012, Magnus Kvalheim <mag...@kvalheim.dk> wrote: > Hi Tapestry friends, > > We've just upgraded to 5.3.2 and checked out some of the new components. > The Alerts seems pretty useful, but looks like it's only possible to pass > on strings. > > I'm thinking a pretty common use-case would be to render some > components/markup in it - like links. > > I experimented a little by manually rendering a block and pass that on to > alertManager. Got some inspiration from this thread about rendering blocks > - > http://tapestry.1045711.n5.nabble.com/Howto-render-a-block-and-put-it-into-a-JSON-reply-td5486823.html > > -------- > *RenderCommand renderCommand = (RenderCommand)alertBlock;* > *MarkupWriter markupWriter = new MarkupWriterImpl();* > *RenderQueueImpl renderQueue = new RenderQueueImpl(log);* > *renderQueue.push(renderCommand);* > *renderQueue.run(markupWriter);* > * > * > *alertManager.info(markupWriter.toString());* > -------- > That seems to work, but it's a bit clumsy and don't know if it's > the recommended approach for rendering blocks. Does a convenience method > exist for rendering blocks/components? > > > Not sure if it's possible, but how about if one could pass blocks to alerts > directly. That could be pretty flexible as well... > > > Thoughts? > > Cheers > Magnus >
