Technical Beef -

Not that I'm much into Windows development, but I've personnally always preferred using the Microsoft CHM format rather than plain HTML. It's compact, it's fast to open, and pretty fast to search for a specific class or method.

I took some time this morning to generate the Wicket javadocs WITHOUT the examples packages (I can't see why they are included in the default javadocs, it's just annoying to have them mixed with the Wicket API), and the corresponding CHM file using the jd2chm javadocs-to-chm converter. This program works amazingly well.

For those interested, I generated two flavours of the wicket-javadocs:

• Wicket 1.4rc4 CHM (standard version, 7.76Mb)
• Wicket 1.4rc4 CHM with the linksource option (12.5Mb)

• Wicket 1.4rc2 CHM (standard version, 7.76Mb)
• Wicket 1.4rc2 CHM with the linksource option (12.5Mb)

The linksource option provides a link between a method and its java source code, which makes it a breeze to check what the code does under the water (and that's utterly useful when the documentation of some method is not available).

Other adjustments I've made to the javadocs:

• The Java API classes link to the online JDK1.6 javadocs
• I've separated the core wicket packages and other extension packages that are bundled in a different jar, so that they appear in different groups