By "tutorial style", I mean the book should be read chapter-by-chapter basis in order to understand the later topics and skipping the chapters might affect the understanding in the more advance topics in the book.
By "reference style", I mean the chapters in the book are independent of each others and one can pick up the book, go to the TOC and he can get what he want from a certain chapter about Eclipse.
I feel like most of the books from O'Reilly are more likely to be tutorial style and books from Wrox, McGraw-Hill(The Complete Reference Series) are more likely to be reference style...
The style of the book is, I believe by your definition, more 'reference style'. However the chapters are tutorial in nature. For example if you want information about a particular refactoring you can look that up in the TOC then scroll there. Once there you can then read 'reference' style info on the refactoring and why you might use it as well as see a 'tutorial' style example of it being applied to some piece of code.
You can also get a sample chapter at the Source Beat site (the link to Eclipse 3 Live in my sig).
Well then I guess the book is in reference style as per my definition...
Anyway, I've just downloaded the sample chapter... I'll have a look at that and I'll be able to say whether it is exactly in the "reference style" as per my definition or not... And I'll share more opinions on the sample chapter as well.... [ June 22, 2004: Message edited by: Ko Ko Naing ]
Joined: Oct 12, 2000
I knew there was a promotion coming here but not for which book nor did I know it had yet started (usually they're announced on the day ).
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