You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Michael Wyraz (JIRA)" <ji...@apache.org> on 2013/11/07 21:43:18 UTC
[jira] [Commented] (TAP5-1864) Block renderer helper / service
[ https://issues.apache.org/jira/browse/TAP5-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13816396#comment-13816396 ]
Michael Wyraz commented on TAP5-1864:
-------------------------------------
This feature is much discussed and often requested. There seems to be several ways to do so, it's unclear which is the best.
I use the one above beacuse it is the cleanest, most easy to understand - but I have no idea if there are any drawbacks. Too much internal knowledge is required to decide this.
To please pick this issue and add the service to T5.4!
Thank you!
> Block renderer helper / service
> -------------------------------
>
> Key: TAP5-1864
> URL: https://issues.apache.org/jira/browse/TAP5-1864
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.3.2
> Reporter: Magnus Kvalheim
>
> I've seen several posts on the mailing lists asking for how to render blocks manually in pages/components.
> Had a use case in this issue: https://issues.apache.org/jira/browse/TAP5-1863
> Basically I tried with:
> --------
> RenderCommand renderCommand = (RenderCommand)alertBlock;
> MarkupWriter markupWriter = new MarkupWriterImpl();
> RenderQueueImpl renderQueue = new RenderQueueImpl(log);
> renderQueue.push(renderCommand);
> renderQueue.run(markupWriter);
> alertManager.info(markupWriter.toString());
> --------
> Don't know if it's the 'correct' way of doing things so requesting a service or a helper class available in core that does the job.
--
This message was sent by Atlassian JIRA
(v6.1#6144)