Hello Eric and Kent, I have a few questions about your book: 1] What level of readers or Eclipse users does it best cater to... I mean Basic/Intermediate/Advanced? 2] Looking at the TOC, I get a feeling that for starters, this book would be more useful after a book like "Eclipse - Step by Step by Joe Pluto" since it covers the basic IDE. and your book covers Patterns and Plugins. 3] Do you have seperate examples here in the book or one example being expanded/used throughout the book. What is the testProject mentioned in the Appendix. I need to know this because I am going to start learning Eclipse after having used a few other tools like VAJ and Visual Cafe. Just wanted to know how this book can aid readers like me. Cheers, Karen
Originally posted by Karen Gomes: I need to know this because I am going to start learning Eclipse after having used a few other tools like VAJ and Visual Cafe. Just wanted to know how this book can aid readers like me.
Without knowing anything else than what can be interpreted from the table of contents, I'd say you won't need this book unless you're about to develop your own plugins. The other books, such as Joe Pluta's and a couple of others, cover the basic usage including installing 3rd party plugins. However, if you're about to develop plugins yourself, I'd definitely check this one out!
The relevant question is, do you want to develop plug-ins? You can do this as a beginning user or an expert. Your level of Eclipse expertise will not limit the usefulness of this book. The TestProject mentioned in the appendix is code we developed to help you write automated tests for plug-ins. Kent
Author of <a href="http://www.amazon.com/exec/obidos/ASIN/0596007434/ref=jranch-20" target="_blank" rel="nofollow">JUnit Pocket Guide</a>
The relevant question is, do you want to develop plug-ins? I think question should rather be, when to plug-in. Kent I know I'm being vicious here, but I do find it hard to know when I should make a plug-in as apposed to a stand alone java application. Are there basic "rules" that can one help decide when to plug in or not ??
Joined: Nov 07, 2003
Knowing what I know now having written the book, I can't imagine writing more standalone Java apps. Having to rewrite all the support provided by Eclipse would be a waste of my time. What I didn't suspect was how powerful the opportunities for integration would prove over time. It took us a couple of years to figure out a really integrated way to support JUnit. If we'd just kept using the standalone test runner, we wouldn't have discovered full-time testing (the example from the book). Kent
Johannes de Jong
Joined: Jan 27, 2001
Thanks Kent. I'm putting you book on my christmas list