Gaetan; I also like starting from a book. Then read the (scattered) docs and wiki when am looking for a solution to specific issues. Some projects have an official user guide that is downloadable as pdf or read online as html. I know documentation is one of the the most boring tasks for developers but its is necessary. May be we should hire someone to do the user guide. The users can donate to pay him.
My 2c. Josh. On Fri, Nov 18, 2011 at 2:45 PM, Gaetan Zoritchak < g.zoritc...@moncoachfinance.com> wrote: > I started with the book wicket in action so it was ok. Before choosing a > technology I look at the number of existing books and I buy the best one. > But I'm not sure that every body does like me. > > My main problem is the wiki. The pages are often very old explaining things > that do not apply with the last version of wicket.... and the wiki si so > slow that I can't imagine working on it to update the pages :( > > 2011/11/18 robert.mcguinness <robert.mcguinness....@gmail.com> > > > i'm baffled when people say the documentation is poor, the javadocs are > > excellent and like igor said there are some great books (blogs too!). > > books > > and blogs get outdated fast since technlogy is rapidly advancing, so *use > > the source luke!*. Not only will you learn Wicket, but I guarantee your > > Java skills will improve. > > > > > > awesome examples: > > > > > > > > https://github.com/apache/wicket https://github.com/apache/wicket (scan > > over the unit test, best way to learn any framework not just wicket) > > > > https://github.com/55minutes/fiftyfive-wicket > > https://github.com/55minutes/fiftyfive-wicket (fantastic) > > > > https://github.com/42Lines https://github.com/42Lines > > > > https://github.com/wicketstuff/core https://github.com/wicketstuff/core(a > > gem, tons of examples on how to pretty much do anything) > > > > http://code.google.com/p/wiquery/source/checkout > > http://code.google.com/p/wiquery/source/checkout > > > > https://github.com/jolira/wicket-stateless > > https://github.com/jolira/wicket-stateless (wicket stateless is > > excellent, > > even easier with wicket 1.5) > > > > https://github.com/reaktor/oegyscroll > > https://github.com/reaktor/oegyscroll > > (endless pagination) > > > > http://code.google.com/p/wiquery/source/browse/core > > http://code.google.com/p/wiquery/source/browse/core (jquery) > > > > http://code.google.com/p/jqwicket/source/browse/ > > http://code.google.com/p/jqwicket/source/browse/ (jquery, learn from > the > > code and roll your own if it doesn't fit your needs, super easy > > > > https://github.com/rjnichols/visural-wicket > > https://github.com/rjnichols/visural-wicket (great ui tools) > > > > https://xaloon.googlecode.com/svn/ https://xaloon.googlecode.com/svn/ > > (excellent!) > > > > > > > > rob > > > > -- > > View this message in context: > > > http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-is-a-Flawed-Framework-tp4080411p4082034.html > > Sent from the Users forum mailing list archive at Nabble.com. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > >
