that is why we try to layer functionality in class hierarchy via abstract classes, so you can find a good point to rewrite something high level for your particular usecase.
-igor On Thu, Mar 27, 2008 at 2:06 AM, Timo Rantalaiho <[EMAIL PROTECTED]> wrote: > On Wed, 26 Mar 2008, Charlie Dobbie wrote: > > I'm guessing at this point that I should just copy the DateTimeField > > component entirely and modify to fit! :-) > > Yes, Wicket does not entirely solve the issue of GUI > component reuse, though helps a lot in it. I have also > sometimes found that the most complex ready-made components > serve better as examples than generic solutions; sometimes > trying to make the same component usable in cases that > differ by too much would make it too complex. > > Best wishes, > Timo > > -- > Timo Rantalaiho > Reaktor Innovations Oy <URL: http://www.ri.fi/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
