>From my own experience most of the times the images in those links are taken from properties of some entity (say product or user) that is ultimately comming from a model, not just static resources. So you can't avoid the code counterpart anyway.
Reagrds, Carlos On 9/11/07, mchack <[EMAIL PROTECTED]> wrote: > > I think it's a common case in most if not all web apps (hyperlinked images). > It is so common that having to add code would cumbersome. I appreciate the > component oriented aspect of the framework but really want to use it for > more leveraged UI elements. > > I guess what I am looking to build is something analogous to the > <wicket:link> tag that will work when encapsulating an <a....><img../> > sequence. I assume this is possible and will review the code behind the > wicket:link component. This will make it possible to achieve the > appropriate behavior directly in the markup. > > Thanks > > > Carlos Pita-4 wrote: > > > > If it's such a common case in your application write a (trivial) > > component for it, and add it to your hierarchy with a oneliner where > > it's needed. That's what componentization is mostly about, after all. > > > > Regards, > > Carlos > > > > > > -- > View this message in context: > http://www.nabble.com/Any-way-to-apply-wicket%3Alink-to-%3Ca%3E-with-contained-%3Cimg%3E--tf4425113.html#a12625672 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
