Depending on what you are doing, you may want to try implementing the "foo" feature code as a behavior. Behaviors are like plugins for components, and can be used on any component. So, if it is possible to implement your functionality as a behavior, then you could add it to the button or ajax button, or a link, etc.
-- Jeremy Thomerson http://www.wickettraining.com On Tue, Oct 7, 2008 at 10:12 AM, Martin Dietze <[EMAIL PROTECTED]> wrote: > Hi, > > I am currently running into the following: I extend the button > class by a snappy "foo"-feature. I build stuff which uses it. > Now I need a "foo"-ified AjaxButton within this infrastructure. > > The obvious way to do this is to write an interface FooButton > which gives me this "foo"-feature. However FooButton is by > itself not a Button, nor can I make it one since the Button > class is an abstract class, not an interface. > > Just wondering, whould it be a good idea to add such interfaces > to the Wicket-API? Or am I missing something? > > Cheers, > > Martin > > -- > ----------- / http://herbert.the-little-red-haired-girl.org / > ------------- > =+= > Was ist der Unterschied zwischen einer Bratsche und einer Waschmaschine? > Die Waschmaschine vibriert, kommt erst am Ende ins Schleudern, und was > rauskommt, ist sauber. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
