Also one very benefiial point of view is just to code something and when you find a bug (either in your own code or Wicket), debug through wicket source and find the cause. If it's a wicket bug -> contribute quickstart to jira that repeats the bug. I have learned myself quite a bit by doing this. However, I am still a bit puzzled with wicket's request cycle, there seems to still to be some magic going on ... ;)
** Martin 2009/7/24 Pierre Goupil <goupilpie...@gmail.com>: > Good evening, > > In order to learn Wicket as well as good Java coding ^ ^, I'd like to read > Wicket source code. It's been a couple of months since I use it, so I have a > general user-view on it. > > Do you have advice ? Where should I start it all ? Is there any typical > workflow through the code-base for such a matter ? > > Hope to hear from you soon, guys ! > > Regards, > > Pierre > > > > -- > Sans amis était le grand maître des mondes, > Eprouvait manque, ce pour quoi il créa les esprits, > Miroirs bienveillants de sa béatitude. > Mais au vrai, il ne trouva aucun égal, > Du calice du royaume total des âmes > Ecume jusqu'à lui l'infinité. > > (Schiller, "l'amitié") > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
