[#STS-47] Tag renderers (not just error renderers) - Stripes

Details

Type: New Feature
Status: Resolved
Priority: Major
Resolution: Won't Fix
Affects Version/s: None
Fix Version/s: Release 1.6
Component/s: Tag Library
Labels:
None

Description

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.

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Sebastian Hennebrueder added a comment - 20/Aug/07 3:29 PM

What about a tag provided as hook into custom code. It provides access to Stripes infrastructure and delegates rendering to custom code.

We could even think about a shell script being used so that rendering can be influenced dynamically.

Regards

Sebastian

Show

Sebastian Hennebrueder added a comment - 20/Aug/07 3:29 PM What about a tag provided as hook into custom code. It provides access to Stripes infrastructure and delegates rendering to custom code. We could even think about a shell script being used so that rendering can be influenced dynamically. Regards Sebastian

Hide

Permalink

Tim Fennell added a comment - 12/Jan/08 7:38 AM

This is the last really big thing that was left on the 1.5 list, and I think at this point it's more important to get 1.5 out than to get this done. Sorry.

Show

Tim Fennell added a comment - 12/Jan/08 7:38 AM This is the last really big thing that was left on the 1.5 list, and I think at this point it's more important to get 1.5 out than to get this done. Sorry.

Hide

Permalink

Remi VANKEISBELCK added a comment - 17/Feb/13 3:10 PM

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.

Show

Remi VANKEISBELCK added a comment - 17/Feb/13 3:10 PM 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.

Hide

Permalink

Remi VANKEISBELCK added a comment - 17/Feb/13 3:11 PM

needs "Won't fix" sorry for the noise

Show

Remi VANKEISBELCK added a comment - 17/Feb/13 3:11 PM needs "Won't fix" sorry for the noise

Hide

Permalink

Remi VANKEISBELCK added a comment - 17/Feb/13 3:11 PM

Here, won't fix.

Show

Remi VANKEISBELCK added a comment - 17/Feb/13 3:11 PM Here, won't fix.

People

Assignee:

Remi VANKEISBELCK

Reporter:

Greg Hinkle

Vote (3)

Watch (5)

Dates

Created:

08/Aug/05 12:48 PM

Updated:

17/Feb/13 3:11 PM

Resolved:

17/Feb/13 3:11 PM