I'm all for improving the javadocs... oh yes... but in my experience with javadocs, the context is too limited.. to the class or interface in question.. there is rarely the more important 'bigger picture' information that you need as a developer diving into something new... Wicket is a fantastic framework .. it encapsulates so much ... but in doing that, it hides so much... I have been using tit for a couple of years now... The initial learning path is easy .. (by design) But we eventually need to step outside of the box... and that's where the encapsulation bites most of us... Ajax... jQuery... Response cycles, page caching..... We need to know how it all works and yes we have the source code... but... Back to my initial request...
Wicket Internals... !!!! :) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/I-think-it-s-time-for-a-new-book-Igor-and-Co-tp4650687p4650787.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
