Regarding this subject, I have been running some tests as time
permits.
May I suggest the following (which I might have mentioned before):
1) The form needs to be more CSS friendly (following the MVC pattern).
This means no tables.
In my tests I have been able to trim the fields to: <label...>
+<input...>+comment+<br/>
and with very simple CSS make the form look like the current one.
More complex CSS could be used to position each element individually
if desired.
2) For each field passed to the form its label and its value must be
accessible in the view via a statement similar to the one mentioned
above: {{=form.latest.field}}, mine look like {{=form.label.field}}
and {{=form.value.field}}. Labels are required for translation
purposes. Some field values, like those of select type fields, require
special consideration; specially when the fields can be converted to
display only (e.g. using DIV instead of INPUT).
3) Custom forms also need custom form error handling. My solution so
far is to use a small JS to change the background color of the fields
in error and change the title attribute to hold the error, so hovering
a field in error displays the error message. But this is probably a
matter of personal preference. Same as replacing the comment with an
image of a question mark that opens the text when requested without
cluttering the form.
4) In the future I would like to integrate the automatic creation of
cascaded fields and autocompletes if possible.
I could be leaving something out but things tend to come out on the
ensuing discussion.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
