Guys, Now we're into 1.0.3, I'd like to enable the inline validation for 'onchange' of an input component. I'd like to start some discussion on how we'd achieve this and provide the most flexbility. The feature is currently implemented in a private method and can be tested using onchange="_validateInput(this);". I'd like to use onchange rather than onblur so that users can still navigate around the form and validation would only kick-in when they started editing (ie. changing) an inputs value.
My questions for 1.0.3 are: Should we use 'onchange' and for event based validation? ... and what's the preferred way to do the event registration? Would this be the default (or perhaps only) mode for client-side validation? ... and would we provide a per-field way to disable event based validation? Should c/s validation routines be namespaced (e.g. TrValidator)? ... and should we move away from outputting the validator/convertor arrays per form and perhaps have input components self register their validators/convertors? Your thoughts, Danny -- Chordiant Software Inc. www.chordiant.com
