[JIRA] Resolved: (STS-47) Tag renderers (not just error renderers)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Resolved: (STS-47) Tag renderers (not just error renderers)

JIRA jira@stripesframework.org

     [ http://www.stripesframework.org/jira/browse/STS-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remi VANKEISBELCK resolved STS-47.
----------------------------------

    Resolution: Fixed

This is a very broad subject and goes beyond the scope of Stripes IMHO.

"core" Stripes already allows to craft your own mechanism like the one you describe. There is nothing preventing to do this already, even on 1.5.x.

Woko (http://www.pojosontheweb.com) already includes an implementation of what this ticket describes : a dynamic, metadata driven system for generating FORMs on the fly. It uses Stripes heavily for repop and binding, but the logic of FORM rendering is specific to Woko : one could easily build another FORM generator...

Feel free to reopen if I'm wrong of course.

> Tag renderers (not just error renderers)
> ----------------------------------------
>
>                 Key: STS-47
>                 URL: http://www.stripesframework.org/jira/browse/STS-47
>             Project: Stripes
>          Issue Type: New Feature
>          Components: Tag Library
>            Reporter: Greg Hinkle
>            Assignee: Remi VANKEISBELCK
>             Fix For: Release 1.6
>
>
> I thought about this idea back for a certain pfw as a mechanism to allow flexibility in the display of the form tags. For example, allowing one to have a renderer that would output a calendar interface instead of a date entry if configured to do so. The renderers could be just for the input tags really, and would be the equivalent of the UI classes in swing.
> What struck the idea up again was this other wf: http://examples.millstone.org/features/ (check out the DateField component, and set to calendar rendering)
> I also really like the idea of being able to intercept the rendering to show, for example, required field icons/stars, perhaps by groking the destination validation info. Or just a JS info button that explains the field, based on a property lookup.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Stripes-development mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/stripes-development