You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org> on 2008/09/10 19:43:48 UTC

[jira] Updated: (TAPESTRY-849) Tutorial showing use of Block/RenderBlock to render dynamic forms based on object types

     [ https://issues.apache.org/jira/browse/TAPESTRY-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Schulte updated TAPESTRY-849:
------------------------------------

    Fix Version/s:     (was: 4.1.6)
                   4.1.7

> Tutorial showing use of Block/RenderBlock to render dynamic forms based on object types
> ---------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-849
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-849
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 4.1
>         Environment: public facing documentation
>            Reporter: Jesse Kuhnert
>            Assignee: Jesse Kuhnert
>            Priority: Minor
>             Fix For: 4.1.7
>
>
> Using Block/RenderBlock to dynamically render form inputs based on runtime data not available at template design time seems to be a very common pattern that people don't immediately know is easy to do with Block/RenderBlock. 
> A tutorial showing something simple, like a list of object types with varying input fields based on their classtype (or some property of a superclass) would go a long way towards clearing this up. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org