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
Hey,
I have to agree with Gavin: the book is indeed a bit rough.
For example, the auther takes loads of time to elaborate certain
'features' while others are being handled as if he expects the audience
to know what he is talking about.
The examples are imo completely useless in real life since
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
This book was (and still is) a very valuable help to me. I did not read
it cover to cover, although I should have. (I wish I had enough time for
this !). It's a very good introductory book, the kind that gives the
best value for the time you spend reading it. In a perfect world, it
would have
There is always this thing called expectations.
This is the first book written for those who want to get up to speed with
Wicket and I find it extremely to the point.
Funny, but I have dramatically oppossite comments after reading this book.
I like it very much and I find it extremely important
