I've been studying Woody a little, and have some proposals (maybe some of them are nonsense):
1. Ability to generate client-side JavaScript for validation, in
addition to server-side one, like ASP.NET. E.g. the required
condition is easy to do
This would be a welcome addition. It would not be difficult to implement in XSL-T.
2. Possibility of embedding the widget definitions directly into the
template file, so you don't have to maintain 2 files that must be
in sync
I'm not sure I like this. Could save a little typing in simple cases, but would rule out the possibility, for example, of using different templates for different devices.
3. The binding framework could be simpler, if given a bean we bind
matching widgets names with bean properties, by using Java
reflection. In this way the binding xml file could be omitted. Normally the set of bean properties and widget names are the same.
Again, this could be useful in simple cases.
Ugo
-- Ugo Cei - Consorzio di Bioingegneria e Informatica Medica P.le Volontari del Sangue, 2 - 27100 Pavia - Italy Phone: +39.0382.525100 - E-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
