<pre>Author/s : R. Winder, Graham Roberts Publisher : Jon Wiley & Sons Category :Beginning Java Review by : Johannes de Jong Rating : 9 horseshoes</pre> The problem for many of us when learning Java is that we have to make a considerable mind shift from the procedural paradigm to OO, I finally found a book that really helps one make that shift. I, especially, appreciate the small examples they have in the beginning of the book where they purposely code "wrong" solutions and then after reviewing the result recode it the OO "way". This is something they do throughout the book, constantly revisiting some examples when you've acquired new knowledge/insight. They then show you alternatives and/or improvements. A great teaching tool. The section "Building Libraries" shows you how to build a class library containing , sort algorithms, heaps, etc. What can I say but, thanks for finally helping me understand the design considerations behind class libraries. The case examples are fun and really very detailed, its more than a simple coding exercise. They teach you how to define the problem, design the solution, implement it, improve it, recode it, in short "dah lot". The Java Language reference at the end of the book is also a gem. Everything you need is there. (don’t expect the class libraries discussed in detail though). I have a few small negatives that cost the book it's perfect 10, see the Book Review Forum for more info. However , I honestly believe this book teaches you sound Java and OO fundamentals, as such I highly recommend this book.
If decided not to give this book a perfect 10 because of the way the authors have decided to structure their accompanying software, (it can be downloaded from their site). In all the books I've read so far the accompanying software was placed in directories that corresponded with the chapters they were printed in. I makes finding the source easier. The authors of this book however have decided to place the code in directories named at times the Chapter name and at other times the sub-sections in the chapter. Now I know this is nitpicking, but after having use FIND for the 3rd time to find a specific listing, they had lost that final point. It would also be nice if they used line numbers for their code listings in their book. It makes finding the code they discuss so much easier too. [ March 12, 2002: Message edited by: Johannes de Jong ]
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Developing Java Software by R. Winder, Graham Roberts