jmut wrote:ole wrote:OK I've finished the UML for my forms library. ...
Where is it?
Its only rough, I doubt it would mean anything to anyone but myself.
# Organised fields and labels
How would you like to see this done?
# Custom CSS
You write your own, none is generated, basic templates will probably be bundled. How would you like to see this done?
# Form <--> SQL
You can use or, if necessary, write your own postprocessor which can do anything you like to field input. Most of the time it'll just be SQL escaping. How would you like to see this done?
Pluggable/extendable validation on both client and server
Server only at this stage. You write your own assertions or use conventional logic to add errors in onSubmit events. The events are obviously totally within your control so you can attach them to individual fields, whole forms, interchange them, extend them. A test class is provided to make testing for common things easy. How would you like to see this done?
# Pretty errors
Errors appear in a separate div above the entity in question (you can change this if you wish) you can apply whatever CSS you like. The errors messages are written by yourself to ensure user friendlyness. How would you like to see this done?
# Required fields (ties in with validator)
I was thinking of leaving this to be done manually with the onSubmit events but I might actually make required a fixed property of fields.
# Bot prevention
No support as yet. I'll definately think about this. How would you like to see this done?
# Ability to set client-side events (DHTML) for individual fields
Supported. How would you like to see this done?
# (Possibly) some kind of markup/template support
How do you mean?