Hi, Now that half of the team is getting ready to work on Wicket 1.4, which is all about supporting the Java 5 features, I think it is time for the other half of the team to start talking about Wicket 3.0 (we skip 2.0 as we've used that for prototyping before), which is scheduled for 2009.
We've had some offline talk about this with various team members, and it seems that we have basic agreement on at least a couple of things: * Wicket 3.0 source will be all Scala (http://www.scala-lang.org/), which means quite a transition for our team, but we will still maintain compatibility with regular Java. * Relax our policy towards scripting in pages. We're just getting tired of people having a hard time to do simple things with Wicket, so in the future we want to support loops, conditionals and property expressions directly in the markup on top of the facilities we have now. * Introduce layout managers. While it is great to be able to directly code markup with Wicket, we'd like to hide that a bit more and introduce layout managers as the preferential mechanism for composing pages and components. * Swing compatibility. We want our future components to be able to run directly in Swing, and Swing components to be run in Wicket apps. Just like some of our competitors. WDYT? Comments/ suggestions? Cheers, Eelco
