David, 1) you can easily adjust the woody-default.xsl that generates the html tags and then also the javascript code. I've already developed a basic clientside javascript framework but didn't had any time to finish it completely (then I might throw it to the community)
2) this would be against the SoC (Separation of Concerns) of Cocoon but in a form template you are talking about a widget instance while in the form definition it's a widget definition. An object wi (woody instance) is made based on the form definition and then the wi is send to the WoodyTemplateTransformer to inject the html representation of each widget inside the form template 3) not a bad idea but the binding framework is also used to xml binding and then each widget should always be a separate child of the root element (no nested structures could be possible); but also keep in mind that the binding does more than only setting and getting a property; it can also add/delete rows/nodes in a repeater etc. I think when using reflection it would make the bean or xml restricted and that is something we better avoid. Regards, Gunter D'Hondt -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carmona Perez, David Sent: donderdag 6 november 2003 13:03 To: Cocoon (E-mail) Subject: Woody proposals Hi all, I've been studying Woody a little, and have some proposals (maybe some of them are nonsense): 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 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 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. -------- David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
