)
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
View this message in context:
http://www.nabble.com/Reading-Wicket-source-code-tp24651141p24665454.html
Sent from
Coding style is not the best in all parts, fro reading point of view,
definitely ...
**
Martin
2009/7/26 Vladimir K koval...@gmail.com:
For me the magic is how wicket is managing pages and their versions. For
instance I realized that it increments version when preparing the page for
render.
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.
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
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
