I'd say you'd be best served by using a quickstart application and clicking into code to see what it does. Set breakpoints to see what's happening in a real, live application. Just randomly reading code files won't give you nearly as much benefit.
-- Jeremy Thomerson http://www.wickettraining.com On Fri, Jul 24, 2009 at 3:07 PM, Pierre Goupil<goupilpie...@gmail.com> wrote: > 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
