You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Glen Stampoultzis <gs...@iinet.net.au> on 2003/12/05 12:59:14 UTC
ValidatingTextField, NumericField, DateField ...
I noticed that because the subclasses of ValidField in contrib provide
their own validator that you can't get access to methods like
setClientScriptingEnabled(). Is there any good reason that this
functionality hasn't been exposed?
Regards,
Glen Stampoultzis
gstamp@iinet.net.au
http://members.iinet.net.au/~gstamp/glen/
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: ValidatingTextField, NumericField, DateField ...
Posted by Glen Stampoultzis <gs...@iinet.net.au>.
Some interesting points raised. We have two points of view:
1. ValidField does everything these other components do so why do we need them.
2. The other components are easier to use because you don't need to define
separate beans.
I think it would be nice if ValidField could be made a little easier to
use. Perhaps something like:
<component id="bidAmountField"
type="<http://jakarta.apache.org/tapestry/doc/ComponentReference/ValidField.html>ValidField">
<binding name="value" expression="lotBid.bidAmount"/>
<static-binding name="validator" value="number{required: true;
minimum: 10; maximum: 200}"/>
<static-binding name="displayName" value="Bid Amount"/>
</component>
So validator could be a class or a string expression describing one of the
default registered validators and it's parameters.
Once that's the case the need for these extra components goes away.
Regards,
Glen
At 06:32 AM 6/12/2003, you wrote:
>I added a bug enhancement about that some time ago.
>You can read comments about it at
>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22838
>
>Regards
> Julio.
>
>At 22:59 05/12/2003 +1100, you wrote:
>
>>I noticed that because the subclasses of ValidField in contrib provide
>>their own validator that you can't get access to methods like
>>setClientScriptingEnabled(). Is there any good reason that this
>>functionality hasn't been exposed?
>>
>>Regards,
>>
>>
>>Glen Stampoultzis
>>gstamp@iinet.net.au
>>http://members.iinet.net.au/~gstamp/glen/
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
Glen Stampoultzis
gstamp@iinet.net.au
http://members.iinet.net.au/~gstamp/glen/
Re: ValidatingTextField, NumericField, DateField ...
Posted by "Julio C. Rivera" <ju...@ya.com>.
I added a bug enhancement about that some time ago.
You can read comments about it at
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22838
Regards
Julio.
At 22:59 05/12/2003 +1100, you wrote:
>I noticed that because the subclasses of ValidField in contrib provide
>their own validator that you can't get access to methods like
>setClientScriptingEnabled(). Is there any good reason that this
>functionality hasn't been exposed?
>
>Regards,
>
>
>Glen Stampoultzis
>gstamp@iinet.net.au
>http://members.iinet.net.au/~gstamp/glen/
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org