I suppose this would be interesting to some of you, so if you want to, I'll put them on the wiki. Just need to port them to the new velocity-implementation (I'm having some trouble with error display, but I'll probably get it fixed sometime tomorrow). A template gallery would perhaps also be nice - if the velocity context are remains as it is now for a while? Patrick, are they? :)
Cheers,
Dag
Patrick Lightbody wrote:
You can also _just_ create the controlheader.vm and controlfooter.vm files without making a whole new template. Just add the following dir structure to your web-app:
/templates/xhtml - controlheader.vm - controlfooter.vm
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Francisco Hernandez Sent: Tuesday, October 21, 2003 8:28 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] UITags inflexible
check out this thread:
http://www.mail-archive.com/[EMAIL PROTECTED]/m sg05276.html
I dont know if this ever got checked in to cvs or not but this seems like it can help you out (if it is checked in..) you could do similar things just using other templates but its alot easier to just create new
foo-header.vm instead of a whole new template dir and files for that template dir
John Patterson wrote:
Hi,code
It appears that the UI tags all include standard header and footer
that places them within a table within the containing form. Thisallows
validation errors to be nicely formatted above the relevant input. However, the simple structure of this table makes it hard to create forms that are not laid out in its extremely simple manner. For this reason I could not use the UITags in my last application.'layout'
I think that if the UITags were simplified to not include this
functionality they would become much more useful to most real life web
applications. I need the ability to define exactly where the error messages will appear on the page. More importantly I need the ability
to layout form fields in a pattern other than the simple 'one row per field' that is assumed by the UITags.output
A new tag would be useful that would check for error messages and
them where the designer wants them. Something like this:name="age"><ww:iterator><ww:property/></ww:iterator></ww:error>
<ww:text name="age"/>
<ww:error
This would simply check the fieldErrors for messages and push themonto
the stack allowing you to display your messages whereever on the page you want.
John.
------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
