Thanks for your opinion on this... I think this is a similar approach to what I had in mind with the panel. What I do not like about those Panel solutions is that the link has to be wrapped and thus in itself is not a subclass of Link anymore. I think a really elegant solution should inherit from Link or one of its subclasses...
I agree with you in what you said about implementing components fitting to our needs ourselves. However, there are less common components in core as well as in extensions... Anyway - it is okay to it it by oneself. I was just hoping that there was a more elegant way to extend wicket components with additional markup than wrapping it into a Panel or fiddling about too much with the component tag body... -- View this message in context: http://www.nabble.com/Implement-LabeledLink-and-ImageLink-components---what-is-the-most-elegant-way--tp19147651p19161875.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
