no, no, you're on the right track with composition. more simpler classes is the ideal because it breaks the problem down. if you start to feel like you have too many classes, you probably need to grow (or maybe refactor) your package hierarchy.
Loren Cole wrote: > > No that is pretty much what I meant. The composition solution would > involve > and abstract superclass and then for each kind of widget a fairly trivial > implementation of the superclass, a static panel, and a dynamic panel. > It's > just that all that class proliferation gives me a nasty feeling and I'd > like > avoid it if possible. > > Any other ideas? > > Thanks, > Loren > > -- View this message in context: http://www.nabble.com/building-extensible-components-tp21488696p21490219.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
