I agree with you; the idea of a book should really be to clarify concepts. Because technology keeps moving on and that's where the code and user forums come is. But a foundation ;..specially on architecture and life cycles is best explained bya book. That's what I"m searching for . But each one to their own!
:) Sent from BlackBerry® on Airtel -----Original Message----- From: "Frank Silbermann" <[email protected]> Date: Fri, 12 Nov 2010 09:40:42 To: <[email protected]> Reply-To: [email protected] Subject: RE: Need Wicket Book When I coded my application originally based on Wicket 1.2, I after looking at the DataTable example, I had to peruse the DataTable (and, for 1.2, DefaultDataTable) code to figure out what I needed to do for my task. Even if I had had_Wicket_in_Action_ at my disposal back then, I think I still would have had to look at the DataTable implementation. Perhaps with open source it is expected that users will have to look at the implementation code now and then, but I think for many people it is a psychological hurdle. /Frank -----Original Message----- From: Martijn Dashorst [mailto:[email protected]] Sent: Friday, November 12, 2010 8:57 AM To: [email protected] Subject: Re: Need Wicket Book On Fri, Nov 12, 2010 at 3:24 PM, Frank Silbermann <[email protected]> wrote: > Does any Wicket book describe the use of Wicket Extensions, such as > DataTable? I didn't see anything on that subject in _Wicket_in_Action_. In order to keep the book manageable (in thickness) and to be able to publish it on some derailed schedule, datatable and extensions friends were not included. It would probably have costed another 20 pages or so to properly discuss datatable, and another 20 to quickly summarize each component in extensions. We believe that the explanations offered in Wicket in Action should provide anyone to fully grasp Wicket concepts and that should suffice to have a really quick understanding of anything wicket extensions throws at you (unless you look at modal window, or the tree components ;-) Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
