I’ve put together some interesting material on making really shiny forms with Wicket. I’ll be presenting it tomorrow at the fourth London Wicket Users Group event, which is being hosted by Skills Matter in Clerkenwell. See the jWeekend registration page for more details.
The recent talk I did at the last London Wicket event and Wednesday’s Java Web User Group is now available on-line (12Mb, Quicktime H264, plays fine under Linux using VLC or MPlayer).
There’s also a ready to run Maven 2 + Eclipse quickstart available to accompany it (built against Wicket 1.3.0-beta2).
Although it’s billed as an introduction, I’m going to cover some slightly more advanced stuff so that people can see just how powerful Wicket is, including a properly useful and reusable generic POJO editor in only a few tens of lines of code.
Hope to see you there!
jWeekend is running an Introduction to Apache Wicket 1.3 course on July 21-22. Their approach of running courses on a weekend means busy people don’t need to take time out of their day jobs to find the time for training.
This course is the perfect opportunity to really get up to speed with the latest version of Wicket, due to be released very shortly (we’ve now frozen the API ahead of the 1.3 release, so this course is as relevant as it gets). I’m going to be overseeing the second day; presenting the material and running the workshops. As one of the core coders on Wicket, I’m well placed to give you excellent insight into the framework and answer any questions you may come up with during the course.
Hope to see you there!
londonwicket.org has now been launched. Initially, we’re just using this for event management and booking, but it might well grow into other things if the community wants it to. It is, of course, written in Wicket.
Visit us and register for the first London Wicket Users Group meeting, on July 3rd at 6:30pm, near Aldgate.
Having refactored our proxy support in Wicket’s Spring module into a new wicket-ioc module last night, I decided to see how hard it would be to add decent integration for Google’s Guice IoC framework.
Turns out, it’s not very hard at all, as I’ve just done it over my lunch-break.
Trying to find information about Wicket? I’ve set up a new custom Wicket search engine courtesy of Google. Feel free to give it a twirl, and please ask me if you’d like any sites adding to it.
- How many tools (i.e. IDE plugins) are available for your web framework?
- How many jobs are available for your framework on Dice.com? What about Indeed.com?
- How many messages where [sic] posted to your user mailing list (or forum) in March 2007?
- How many books are available for your framework?
What on earth does he intend to do with them, I wonder? All of these numbers superficially look like they should be “more is better”. On second glance, they’re anything but:
- If you have lots of IDE tooling available, it probably means the configuration for the framework is overly complex and unmanageable without it.
- The framework with the largest number of jobs available is probably Struts 1. Enough said.
- People only post to user lists when they are stuck. If the framework is hard to use, there will be lots of e-mails. If it has a steep learning curve, and/or the documentation is poor, this will be particularly so. On the other hand, an active list might point to a large active user base. Who knows which is which from a raw figure? It might be better to find the number of posters, not the number of messages.
- If your framework is fairly stable, and someone has written a fabulous tome on it that is universally acknowledged as “the bible”, few people would bother writing another book for it. Niche books usually only get written if there is no book currently in that space or if the existing books are rubbish and the author(s) think they can do better. How many books are written is therefore a function of the number written on the subject before a good one arrives, and how stable your framework is. The first is a small random number, probably. The second number is “more is worse”, assuming you don’t like frameworks that change under you all the time.
So, I guess I’m curious what extrapolations Matt intends to make from these figures.
Most programmers like writing things from scratch, but throwing it all away and starting again often isn’t feasible, especially with web applications. I’ve recently been migrating a JSP/servlet based app to Wicket and I suspect there are many people who are going down this path.
Continue reading JSP and Wicket, sitting in a tree…