[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tapestry-user
Subject:    RE: setting size and maxlength of ValidField in a reusable  component
From:       "Howard M. Lewis Ship" <hlship () attbi ! com>
Date:       2003-03-24 23:50:23
[Download RAW message or body]

You can still use inherited binding, informal parameters can still make use
of inherited bindings.  Declare two formal parameters on your component, and
have the ValidField link informal parameters "size" and "maxlength" to the
formal parameters of the containing component.

Those two parameters harken way, way back to before your were allowed to
specify informal parameters in the template.  I also thought I could rename
HTML attributes (size -> displayWidth, maxlength -> maximumLength) like that
wouldn't confuse anybody.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry



> -----Original Message-----
> From: Blake Nicholson [mailto:tapestry@package.com] 
> Sent: Monday, March 24, 2003 6:41 PM
> To: tapestry-user@jakarta.apache.org
> Subject: setting size and maxlength of ValidField in a 
> reusable component
> 
> 
> I have a reusable component that contains a ValidField, among other 
> components.  With Tapestry 2.4 alpha 5, the displayWidth and 
> maximumLength 
> parameters were removed from ValidField.  How do I need to set up my 
> reusable component so that the displayWidth and maximumLength 
> can be set on 
> it and passed through to the ValidField that it contains?
> 
> Prior to the change, I could easily use inherited-binding in my 
> component-specification, but I'm not clear how to approach this now.
> 
> 
> Thanks,
> Blake
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> 


[prev in list] [next in list] [prev in thread] [next in thread]