cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <joerg.heini...@gmx.de>
Subject Re: [cforms] new validation: every widget can have a validator
Date Wed, 04 Feb 2004 22:45:17 GMT
On 04.02.2004 23:12, Sylvain Wallez wrote:

>> Which properties are available here? Obviously widget, but maybe also 
>> form?
> 
> The form is available on each and every widget through 
> "widget.getForm()" or "widget.form" in JS.

Ah, good to know. Just like document.getElementById() and 
element.getOwnerDocument() in DOM.

> I also added get/setAttribute on Form that allows passing arbitrary data 
> between the enclosing context (flowscript or action) and the various 
> components operating on the form (validators, event handlers, etc).

Nice.

>> Must we specify 
>> Packages.org.apache.cocoon.woody.datatype.ValidationError() ?? It 
>> seems to be to much typing. What about just setValidationError(String 
>> [, more parameters])? Do we loose flexibility? At the moment there is 
>> only o.a.c.w.validation.ValidationError and the deprecated extending 
>> o.a.c.w.datatype.ValidationError.
> 
> My plan is to make some of the most useful Woody classes directly 
> visible in the JS snippets. This includes ValidationError, among others.

Does this mean like import in Java, so that it is possible to access the 
class without package?

>> BTW, shouldn't the sample create a non-deprecated ValidationError?
> 
> Yeah sure. This is the first commit of this new feature, which needs 
> some polishing. The deprecated ValidationError remains from the various 
> code iterations.

Ok, will polish it :)

Joerg

Mime
View raw message