What would constitute good Wicket improvement projects for Google’s Summer of Code 2007? Here’s a list I just came up with:
- add support for new markup languages: WML, XUL, …?
- create visual editor for Eclipse, Netbeans or IntelliJ?
- create comprehensive scalability/performance tests between Wicket, JSF and Tapestry
- expand/improve on Wicket Kronos, a Wicket based CMS
- write a reference manual or a doclet for generating one from our JavaDoc
- write a conference planner for ApacheCon in Wicket
- …
I think this is just a short list, and I guess there are much better ideas than what I came up with. Share your ideas!
Very nice list. Can’t wait to see the full list populated.
I hope I can take one of the final assignment this summer! Just can’t wait to do it !
Which assignment would you like to do? Or do you have other ideas?
More widgets! Can. Always. Use. More. Widgets!
Yes, that is *even* more widgets.
Nicer error pages for mismatched component hierarchies. If it’s in the markup only, send the plain template over (to be rendered, not escaped) with the stranded element having a red border. If it’s in the page hierarchy only, send out a tree with the relevant hierarchy in it and the stranded component outlined in red. Neither page should require horizontal scrolling or very much paging-down to find the problem.
(Obvs, I’ve thought about doing this myself! But who knows if I’ll get around to it.)