Hey Les,
For me code is like pictures, they speek for themselves.
Sorry, I probably was not clear enough about this: I totally agree with
that.
Actually, for me, looking at the code most of the time helps more than
any technichal explanation.
However, if I read a book on Wicket (or any other
Of Gavin
Sent: Thursday, September 14, 2006 1:32 AM
To: wicket-user@lists.sourceforge.net
Subject: [Wicket-user] Pro Wicket: Great first book on wicket
Hello,
I have been looking at wicket for some time. I found it after
looking at
many other frameworks (Struts, Spring, WebWork, etc
By the way:
There is a very nice introduction to Wicket 2.0 in the last chapters of
the book - I cannot wait to play around with that baby... :)
//Che
__
DISCLAIMER: This e-mail message is intended for the addressee(s) or authorized
recipient only. If you are not the
: [Wicket-user] Pro Wicket: Great first book on wicket
Hello,
I have been looking at wicket for some time. I found it after
looking at
many other frameworks (Struts, Spring, WebWork, etc). Wicket
seemed to be
the best suited to my needs (more java focused with great components).
Although
Wicket: Great first book on wicket
Hello,
I have been looking at wicket for some time. I found it after
looking at
many other frameworks (Struts, Spring, WebWork, etc). Wicket
seemed to be
the best suited to my needs (more java focused with great components).
Although, technically, it had
Hello,
I have been looking at wicket for some time. I found it after looking at
many other frameworks (Struts, Spring, WebWork, etc). Wicket seemed to be
the best suited to my needs (more java focused with great components).
Although, technically, it had one the web framework race for me, its
