Otan schrieb: > Hola, > > Please make the Javadoc more informative. The Wicket Example is fine and I > always learn from it, but, I think the example is limited; so, the Javadoc > is the one I look into most of the time. > > I think it's Ok if the Javadoc of some classes and methods are completely > blank; the class and method names are descriptive anyway. But what's not ok > is not stating the USAGE of a class or method. I think if Wicket includes > the USAGE aside from the description of a class or method, I would not be > needing a book anymore. How and when a class or method is used and what are > the consequences of using it are one of the things I want to see at the > Javadoc. Of course, it's not always necessary but it's really a great help > sometimes. I'm not asking a tutorial or a manual in the Javadoc, of > course.
Maybe the wiki can help you out: There is a comprehensive guide for getting started: http://www.wicket-wiki.org.uk/wiki/index.php/Newuserguide And the reference library with a lot of how-tos: http://www.wicket-wiki.org.uk/wiki/index.php/Reference_library#View_Layer Timo _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
