Projects like Springframework use docbook. It's really nice, You put all documentation in xml files which are in the scm and when you release it, you have documentation per release.
On Wed, Jan 23, 2013 at 12:26 PM, Martin Grigorov <mgrigo...@apache.org>wrote: > Hi, > > > On Wed, Jan 23, 2013 at 12:36 PM, Philippe Demaison > <ph.demai...@gmail.com>wrote: > > > If I had your knowledge and more time (project manager), I wish I could > > help. > > > > Many people have said this... > > But I know exactly what you mean about the missing reference. > I have an idea to start writing a reference guide that will explain the > topics I'm most acquaint with. > I'll use http://sphinx-doc.org/ because it supports an easy way to embed > code snippets from other Maven modules - wicket-examples. So the code > examples will evolve with the framework. > Stay tuned! > > > > > > Best regards > > Philippe > > > > > > 2013/1/22 Thies Edeling <th...@rrm.net> > > > > > Wicket is open source, if you feel that the documentation is lacking - > > feel > > > free to contribute. > > > On Jan 22, 2013 5:54 PM, "Philippe Demaison" <ph.demai...@gmail.com> > > > wrote: > > > > > > > Hi Ondra and Kees, > > > > > > > > Are you kidding ? > > > > > > > > Are you saying that I need to > > > > > > > > - read a book released in 2009 covering wicket 1.3 ? > > > > - read http://www.wicket-library.com/wicket-examples/index.html (for > > > which > > > > wicket version ? ) > > > > - read the Wicket Cookbook > > > > - read the migration from 1.x to 1.5 > > > > https://cwiki.apache.org/WICKET/migration-to-wicket-15.html > > > > - read the migration from 1.5 to 1.6 > > > > https://cwiki.apache.org/WICKET/migration-to-wicket-60.html > > > > > > > > to understand what are the Wicket's benefits and write a POC ? > > > > > > > > > > > > Are you saying that I need to google to read the best practices ? > > > > > > > > You know that framework adoption is linked to good documentation. > > > > Not only of course (quality are community are equally important) but > > > > documentation is essential. > > > > > > > > For example, I find these documentations much more appealing > > > > > > > > http://www.playframework.org/documentation/2.0.4/Home > > > > http://tapestry.apache.org/documentation.html > > > > https://developers.google.com/web-toolkit/doc/latest/DevGuide > > > > http://www.springsource.org/spring-framework#documentation > > > > > > > > Don't you ? > > > > > > > > Philippe > > > > > > > > 2013/1/22 Ondrej Zizka <ozi...@redhat.com> > > > > > > > > > Hi Phillipe, > > > > > > > > > > you're right, the documentation deserves improvements. > > > > > > > > > > I would recommend you to start with the Wicket in Action book. That > > > will > > > > > give you the basic concepts of Wicket. > > > > > Then continue with the examples from > > http://www.wicket-library.com/** > > > > > wicket-examples/index.html< > > > > http://www.wicket-library.com/wicket-examples/index.html>. That will > > > > enforce what you learned in the book, and show more tricks. > > > > > Then go through the Wicket Cookbook. That is a collection of > > solutions > > > > and > > > > > best practices for common tasks. > > > > > Then skim through https://cwiki.apache.org/** > > > > > WICKET/migration-to-wicket-15.**html< > > > > https://cwiki.apache.org/WICKET/migration-to-wicket-15.html> > > > > > and > https://cwiki.apache.org/**WICKET/migration-to-wicket-60.**html< > > > > https://cwiki.apache.org/WICKET/migration-to-wicket-60.html>. > > > > > > > > > > It is quite easy to create non-ajax websites. I only have > dificulties > > > > once > > > > > it gets to Ajax. > > > > > In such cases, this mailing list is very useful, and also > > stackoverflow > > > > > and the multitude of blogs. > > > > > > > > > > Not sure what are your other options, but e.g. I prefer Wicket over > > > JSF. > > > > > Even big JSF fans claim that "JSF is marginally better". > > > > > > > > > > And last thing, I would recommend to try Wicket in combination with > > > JBoss > > > > > AS 7, which made my development quick and easy - redeployment in 3 > > > > seconds, > > > > > restart in 5 seconds, CDI, JPA and JAAS at hand, the Infinispan > > cache, > > > > easy > > > > > management, ... > > > > > > > > > > my2c, > > > > > Ondra > > > > > > > > > > > > > > > > > > > > > > > > > On 01/22/2013 11:24 AM, Philippe Demaison wrote: > > > > > > > > > >> Hi All, > > > > >> > > > > >> As Gabor Friedrich from the FAO, we are in my company, L'Oreal, > > > > comparing > > > > >> different web frameworks. > > > > >> Apache Wicket may be the best framework, may be usefull for my > > > company, > > > > I > > > > >> don't know. > > > > >> I don't know because there is no clear documentation for a good > > > > >> evaluation. > > > > >> > > > > >> In fact the documentation is not good. > > > > >> > > > > >> The documentation is not up to date, not to say obsolete, not well > > > > >> organized and definitely not sexy. > > > > >> Sorry to being rude, I know this is difficult to do, but this is a > > > major > > > > >> drawback when company and people evaluate Wicket. > > > > >> > > > > >> Some articles are for 1.4 or 1.5, not many for 6 > > > > >> Some articles are redundant. > > > > >> > > > > >> I am sure the folowing structure could be improved : > > > > >> https://cwiki.apache.org/**WICKET/framework-**documentation.html< > > > > https://cwiki.apache.org/WICKET/framework-documentation.html>is > > > > >> https://cwiki.apache.org/**WICKET/index.html< > > > > https://cwiki.apache.org/WICKET/index.html> > > > > >> https://cwiki.apache.org/**WICKET/documentation-index.**html< > > > > https://cwiki.apache.org/WICKET/documentation-index.html> > > > > >> > > > > >> The http://wicket.apache.org/ layout is good. > > > > >> Why not reorganize the documentation with this layout ? > > > > >> > > > > >> Managers want to see benefits, developpers want to learn fast(and > > have > > > > >> fun). > > > > >> > > > > >> > > > > >> I tested the mentionned blogs on http://wicket.apache.org/meet/** > > > > >> blogs.html <http://wicket.apache.org/meet/blogs.html> > > > > >> > > > > >> Here is what I found : > > > > >> > > > > >> Chillenious! - Eelco Hillenius - http://chillenious.wordpress. > > **com/< > > > > http://chillenious.wordpress.com/> > > > > >> last update : 2008 > > > > >> > > > > >> Here be beasties - Al Maw - http://herebebeasties.com/ > > > > >> last update : 2009 > > > > >> > > > > >> Codierspiel - Nathan Hamblen (runs on Wicket) - > > > > >> http://code.technically.us/ > > > > >> no a single wicket post > > > > >> > > > > >> Antwerkz - Justin Lee - http://antwerkz.com/wp/ > > > > >> empty > > > > >> > > > > >> Geertjan - Geertjan Wielenga - http://blogs.sun.com/geertjan > > > > >> http 404 ! > > > > >> > > > > >> Mystic Coders - Andrew Lombardi and > > > > >> Wicket by Example - Community driven are pointing to the same > > address > > > : > > > > >> http://www.mysticcoders.com/**blog/ < > > > http://www.mysticcoders.com/blog/> > > > > >> > > > > >> > > > > >> For a wider adoption of Wicket, > > > > >> Best regards to all of you > > > > >> > > > > >> Philippe Demaison > > > > >> > > > > >> > > > > > > > > > > > > > > > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com <http://jweekend.com/> >
