Welcome, Bill! Though I feel strange welcoming you, since this is my first day as a registered member here. I'd like to solely credit you with my registration, but I was especially tech-motivated in general today due to hearing about Eclipse 3.0 finally being released.
(note: I'm terribly sorry for the length of this post -- feel free to pick-and-choose what you read and respond to; I won't be offended =) )
I've actually been using 2.1.3 exclusively -- I tried switching to a 3.0 stream release (M4, I believe) awhile back, but none of my Ant tasks would work because there was a bug in that Eclipse couldn't read in my property files if there was a space in their filepath, and circumstances at my work prevented me from working around that.
My questions to you, then, have to do with new Eclipse 3.0 features, since I have been a bit out of the loop. Specifically, my questions stem from http://www.idevnews.com/TipsTricks.asp?ID=115
. Until I read that article, I was ignorant of plans for "rich client application development" or "opening up Java tools."
For example, my first passes through the "rich client application" stuff got me horribly excited, as I thought this meant built-in GUI support, preferably SWT -- which I love. This appeals to me since I haven't found a decent SWT GUI plug-in that wasn't rather expensive. Hehe, I'm pretty sure now that I completely misunderstood, but the article linked above, nevertheless, stresses "general application development" with regard to this new feature, and I'm having trouble wrapping my brain around the concept. Maybe I'm getting lost in the buzzwords; I'm wondering if you're familiar with this and could possibly try to summarize it
Similarly, the part on "generalized Java tools" says: "Finally, Eclipse 3.0 will provide support for debugging Java like files e.g. JSPs." Does this mean (which is the other reason I was way over-excited about the upcoming release of 3.0) that Eclipse 3.0 will have Lomboz-like functionality built-in, at least with regard to JSPs, and/or that refactoring will now extend to JSPs? Or did they mean that debugging JSPs, etc., is a possible extension of the new functionality? i.e. it's a possibility when someone writes the code for it?
It's just that I hadn't heard these plans yet and I haven't had time to scour the Eclipse site for which plans were implemented, etc. I'm assuming you've used a very recent release and could spare me a lot of research
The other reason I worry is that, at a glance, the list of chapters in your book seemed like they could also very well have been the list of chapters for an Eclipse 2.1.* book. Is that because your book covers the requisite Eclipse basics, and is simply updated to the Eclipse 3.0 look-and-feel?
Bonus question: How does one approach the business of tech-book writing? Do authors approach the publishers with their ideas as with traditional books? It'd almost make more sense to me that the publishers would publish a list of books they need written. e.g. I can envision Manning recognizing that Hibernate and JavaServerFaces are growing in popularity and potential usefulness, and soliciting authors. But I have no idea -- I'm certainly interested, though.
You have my guilty gratitude if you've read even half of this
At any rate, thanks for being here!