Our friends at the former JavaLobby have written up an interview detailing Wicket’s Ajax implementation. Igor, Jonathan and Eelco provide answers, insight and a glimpse of the future of Wicket Ajax.
When you are away from your open source endeavours for a week or two, you’ll get a big inbox full of messages you need to catch up. There are two ways to tackle the 200+ threads that are waiting for your attention:
Using #1 will lead you to miss out on some really great stuff. I was fortunate to use #2 for the Wicket user list: Andrew Broderick wrote on April 15th some really nice praise to the user list:
[T]he inherent ease of splitting things up into components, and the inherent encapsulation that comes with this, has shrunk our development time markedly. It also gives us a high level of confidence in what we’ve built, because once you get something working in isolation, it keeps working wherever you eventually put it. This is, I think, the single biggest benefit it gives us.
And he concludes:
We’ve thrown our site together quickly and under great time pressure, and Wicket has delivered. The inherent type safety you get from building the site from Java classes helps hugely. It means very few run-time bugs. The separation of markup means our web designer can work in the same codebase as our Java guys too, so no duplication of effort. In fact, what we have done wouldn’t be possible in such a short time frame with any other framework.
I’d hate to have missed this message. Thanks Andrew!
We just released Wicket 1.3.3 and moved the 1.3 codebase into its own branch to make room for new development.
Johan committed the first go at a generified, Java 5 based Wicket framework during the Wicket Amsterdam Meetup held last tuesday. The meetup was great, and I have video of all the talks. Now I just need to ensure the video is good quality and have to transcode it into a web format. I’ll keep you posted on the progress.
So if you depend on Wicket 1.3 and want to build your own Wicket, you should switch your repository to:
If you are interested in an adventure and dare to move to Java 5 based Wicket you can check out trunk:
Please note that trunk will be in flux during the next couple of weeks while we iron out the wrinkles of moving to Java 5
Eclipse and OS X (10.4 Tiger) makes me unhappy. Today I witnessed something really stupid. I have allocated 768MB for Eclipse (eclipse.ini) and to my amazement, Eclipse was beach balling (being unresponsive for you non-OS X-ers). This beach balling was due to the simple fact that the Java garbage collector was reading in pages from the swap file in order to throw everything away. Woohoo! This took of course over 2 minutes.
I doubt that Java will ever become a consumer technology with this kind of shit.