thod call that
>>> in
>>> textfield and override in addpage , this approach will make me change
>>> the
>>> base class for everytime for any new features the sub class needs .I am
>>> looking for some way through whcih I can retrieve the component in the
>>
in
>> textfield and override in addpage , this approach will make me change
>> the
>> base class for everytime for any new features the sub class needs .I am
>> looking for some way through whcih I can retrieve the component in the
>> sub
etrieve the component in the
> sub
> class and add decoratos without changing the base class ?
>
>
--
View this message in context:
http://www.nabble.com/controlling-components-from-sub-classes-tp23853627p23856345.html
Sent from the Wicket - User mailing list archive at Nabble.com.
How about returning the TextField itself from the subclass ? And the
baseclass just returns a default TextField ?
On Wed, Jun 3, 2009 at 10:22 AM, tubin gen wrote:
> I looking for some best practices or better way to control my page
> components , like set enable add attribute modifiers etc.
I looking for some best practices or better way to control my page
components , like set enable add attribute modifiers etc.
for example
I have add and edit page , where one textField should be enabled in add
and disabled in edit so for this I did
add(new
TextField("findingNumber").setEna