Hi Martijn. Since you requested for a user's comment, here's mine.
I've completed two projects using 2.0: an ajax webapp and the other one is a
templating engine that renders html. The reason I liked 2.0 is because they
say it has a more cleaner and simpler API and of course, the Java 5
features.
yes. also, i think it's much less shift than you are thinking, stefan.
we've only really
been talking about discontinuing the constructor change. most if not all of
the other
useful features in 2.0 would be moved into the 1.x branch, not discarded.
and i think
generics would probably be li
This is what we are discussing, and we ask our user community how much
investment they have in 2.0, what they like about it, or don't, and
how hard it would be to go back to the 1.x branch.
Before we have that picture clear we don't make a decision. Wicket is
a community and we can't work without
We are a little bit confused about the future directions of the wicket project.
We startet switching from wicket 1.x to 2.0 in june 2006 and are working with
wicket 2 now for more then 10 months. One year ago it seemed that wicket 2.0
(with generics and new constructor) will be the future and wa
