I'd like to get opinions if it's worth trying to add some example html/code to at least some of the simpler Wicket Examples?
To see what I mean, take a look at the (static) pages here: - http://www.javaguy.co.uk/tmp/comp_ref_panel.html and - http://www.javaguy.co.uk/tmp/comp_ref_multiline.html The downside is that it's not automated, and there needs to be something like this in each example, which, even if off in a discrete method may confuse anyone looking at the real source... // Explaining how String html = "<span wicket:id=\"panel\">panel contents come here</span>"; String code = " public PanelPage()\n" + " {\n" + " add(new MyPanel(\"panel\"));\n" + " }"; add(new ExplainPanel(html, code)); On the other hand, the Component Reference doesn't need to change that often, it can be commented in the real code/html and it might help with people just browsing... /Gwyn [By the way, what /is/ up with the Wicket-Examples site?] ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
