heh, if its just a css reference then why have your component include a default one at all? let the user style it however they like by including their own css files.
-igor On Jan 23, 2008 1:33 AM, Martijn Lindhout <[EMAIL PROTECTED]> wrote: > that makes sense. > > 2008/1/23, Eelco Hillenius <[EMAIL PROTECTED]>: > > > > > On Jan 23, 2008 1:12 AM, Dmitry Kandalov <[EMAIL PROTECTED]> wrote: > > > On Wednesday 23 January 2008 12:55:17 Martijn Lindhout wrote: > > > > I like that one with the ResourceReference. What about providing a > > setter > > > > on the component, so that no subclassing is needed? > > > > > > IMO setter or constructor parameter should be ok, though Wicket classes > > use > > > getters (probably to reduce session size?). > > > > Yep, we often work with overridable methods instead of properties > > because it saves memory. Probably not something you have to worry too > > much about when you create your custom components, but especially for > > the Wicket basic components, this can make quite the difference. > > > > Eelco > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Martijn Lindhout > JointEffort IT Services > http://www.jointeffort.nl > [EMAIL PROTECTED] > +31 (0)6 18 47 25 29 > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
