Martijn Dashorst wrote:
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!
Thanks for the response. I've just attached my patch to the bug issue.
This is my first patch ever for Wicket (or even any Apache project, I
think), so if I've done anything not-quite-right, please let me know.
I hope to send in more patches in the future. (Who knows, I might take
a look at that PagingNavigator.)
mcv.
