Hi -
Sorry, I wasn't clear enough. What about other informal parameters besides "class"?
Dorothy
-----Original Message-----
From: Richard Lewis-Shell [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 08, 2003 2:32 PM
To: Dorothy Gantenbein; [EMAIL PROTECTED]
Subject: Re: [Tapestry-developer] Extending Textfield Question
You don't - you create an explicit parameter in FooSubmit.jwc and then write
a method that interrogates it (eg. public String getClass()) and passes on
the default value if there is no binding. Then bind this method to the
class (informal) parameter of the Submit. I can send sample code if you
want...
R
----- Original Message -----
From: "Dorothy Gantenbein" <[EMAIL PROTECTED]>
To: "'Richard Lewis-Shell'" <[EMAIL PROTECTED]>; "Dorothy Gantenbein"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, January 09, 2003 11:12 AM
Subject: RE: [Tapestry-developer] Extending Textfield Question
> Initially, I thought of the same approach. However, how do you pass the
> informal parameters into your contained Submit button?
>
> Thanks...
> Dorothy
>
> -----Original Message-----
> From: Richard Lewis-Shell [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 08, 2003 2:13 PM
> To: Dorothy Gantenbein; [EMAIL PROTECTED]
> Subject: Re: [Tapestry-developer] Extending Textfield Question
>
>
> OK - I see now. We have the same problem - mainly with submit buttons.
We
> just created a FooSubmit component that uses (rather than inherits) a
submit
> component. We can then control the default class from the FooSubmit, and
> let it be overriden on a case-by-case basis. It's then just a matter of
> making sure everyone uses FooSubmit, rather than Submit...
>
> R
>
> PS. Some names were changed in the above to protect the innocent ;-)
>
> ----- Original Message -----
> From: "Dorothy Gantenbein" <[EMAIL PROTECTED]>
> To: "'Richard Lewis-Shell'" <[EMAIL PROTECTED]>; "Dorothy Gantenbein"
> <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
> "Neil Clayton" <[EMAIL PROTECTED]>
> Sent: Thursday, January 09, 2003 10:55 AM
> Subject: RE: [Tapestry-developer] Extending Textfield Question
>
>
> > Hi -
> >
> > We want to the HTML class to defaulted to our standard style. We do not
> > want to pass "class" everywhere a text field is used within a page or
> > component. For odd cases, the UI designer can pass "class" and override
> our
> > standard style.
> >
> > Does that help?
> >
> > Dorothy
> >
> > -----Original Message-----
> > From: Richard Lewis-Shell [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, January 08, 2003 2:02 PM
> > To: Dorothy Gantenbein; [EMAIL PROTECTED]; Neil
> > Clayton
> > Subject: Re: [Tapestry-developer] Extending Textfield Question
> >
> >
> > I think I have missed the point of this discussion - can you explain why
> > informal parameters cannot do this (as per Malcolm's suggestion)? We
use
> > informal parameters on loads of Tapestry's form components to control
> their
> > class, and it works fine...
> >
> > Richard
> >
> > ----- Original Message -----
> > From: "Dorothy Gantenbein" <[EMAIL PROTECTED]>
> > To: "'Howard M. Lewis Ship'" <[EMAIL PROTECTED]>; "Dorothy Gantenbein"
> > <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
> > Sent: Thursday, January 09, 2003 10:35 AM
> > Subject: RE: [Tapestry-developer] Extending Textfield Question
> >
> >
> > > Hi Howard -
> > >
> > > Yours suggestions of using inheritance for my own text field worked
> great.
> > > However, I also wanted to the same behavior in Radio,
PropertySelection,
> > > Select, TextArea and Checkbox. These components do not have a
> > > beforeCloseTag method. Therefore, I must copy their entire
> > renderComponent
> > > method into my subclass. Unless there is another approach, I would
like
> > to
> > > file and enhancement request for these components to have a
> beforeCloseTag
> > > method added.
> > >
> > > Dorothy
> > >
> > > -----Original Message-----
> > > From: Howard M. Lewis Ship [mailto:[EMAIL PROTECTED]]
> > > Sent: Wednesday, January 08, 2003 4:01 AM
> > > To: Dorothy Gantenbein; [EMAIL PROTECTED]
> > > Subject: Re: [Tapestry-developer] Extending Textfield Question
> > >
> > >
> > > TextField is designed for this, fortunately (mostly to support
> > ValidField).
> > >
> > > You should be able to copy the TextField .jwc into your application
and
> > > modify it to point to your own class. Add the class parameter as
> > direction
> > > "in" to a property named "styleClass".
> > >
> > > Subclass TextField and override beforeCloseTag() to insert your
> styleClass
> > > property.
> > >
> > > By putting TextField into the application specification it will
> > > automatically take effect for all the pages of your application.
> > >
> > > ----- Original Message -----
> > > From: Dorothy Gantenbein <mailto:[EMAIL PROTECTED]>
> > > To: [EMAIL PROTECTED]
> > > <mailto:[EMAIL PROTECTED]>
> > > Sent: Tuesday, January 07, 2003 8:37 PM
> > > Subject: [Tapestry-developer] Extending Textfield Question
> > >
> > > Hi -
> > >
> > > We would like to have our own textfield with an HTML 'class'
parameter.
> > > This class parameter would have a default to our pre-defined style.
> > Should
> > > I inherit from Tapestry's TextField or use delegation? If I use
> > delegation,
> > > how do I pass the informal parameters to the contained Tapestry
> TextField?
> > >
> > > Thanks...
> > > Dorothy
> > >
> > > <http://informative.com/advise/index.jsp>
> > > <http://informative.com/images/spacer_clear.gif>
> > >
> > >
> > >
> > > Dorothy Gantenbein
> > > Software Architect
> > > 650.534.1077 | t
> > > 650.534.1020 | f
> > > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> > >
> > >
> > >
> > >
> >
> >
>
>
