I guess this should go into Wicket NG (2.0/1.5) as a replacement for the current image map. I don't think it is a problem that we break backwards compatibility for a couple components in the release after the generics release.
I'd chalk this one up to the Wicket 1.0 components. They exist since the beginning of Wicket, and haven't had any real major updates. Another component is the PagingNavigator which could use some love. I'll add this one to the wish list and assign the correct Wicket version for this patch. We'll get back to this one when we start 1.5/2.0. Thanks! Martijn On 3/30/08, Martijn Vos <[EMAIL PROTECTED]> wrote: > I've posted about this issue on the users mailinglist a couple of days > ago, and I've > got a fixed version of the ImageMap ready now. Unlike the existing > ImageMap, my > new one works together with an Image, so you can easily have a dynamic > image > corresponding to your dynamic ImageMap. > > One problem: it breaks compatibility with the old ImageMap, because it's > attached > to the <map> tag instead of the <img> tag and requires a <map> tag in > the markup. > I think this is a better approach than the old way, but for people > already using the > old ImageMap, such a break in compatibility may be a problem. So what to do? > > Options: > 1: Add the new ImageMap under a different class name (but which?) > 2: Replace the old ImageMap with the new one anyway > 3: Replace the old ImageMap with the new one starting with Wicket 2.0 > > Personally I don't quite see the use of the old ImageMap (it looks like > it can't work > together with a dynamic Image, but I could be wrong), but I'm pretty new > to Wicket, > so I could easily be overlooking some other way of dealing with Images. > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
