Slashdot Mirror
Eclipse in Action
Overview With a book like this it's difficult to know where to pitch the level. Do you aim for the lowest common denominator or do you assume some experience on the part of your reader? This book seems to have pitched itself well, not pandering to the absolute Java newbie, not afraid to get down into the code and yet gentle enough that newer Java developers can follow easily. The heavyweight chapter on writing plug-ins is at the back where it shouldn't frighten those of a sensitive nature.
The book is divided into two sections. The first and largest section concerns actual use of Eclipse during Java application development. The second section is for those who wish to write plug-ins for Eclipse.
The book takes a very 'Test Driven Development' approach to Java development and this shows in the manner that Eclipse is presented and taught. Emphasis is given to the tools that come with Eclipse, especially Ant, Junit and the CVS client. For those already skilled in these tools, this might seem like filler, but remember that there are still pitifully few Java developers using even these simple and free tools. My hat is off to the authors for their TDD evangelism, skillfully disguised as Eclipse usage instruction.
What's To Like I liked the progression followed in the book, first teaching the basic operation of Eclipse and then moving on to the tools that come with the base install. What's To Consider Some may consider that the material on Ant, Junit and CVS is filler. The 'Test Driven Development' theme may be a little too much evangelism for some.I use Eclipse on a Mac OS X box and I felt that there was very little discussion concerning the cross-platform attributes of the tool. All of the screenshots were from a Microsoft Windows build of the software; a Linux or OS X screenshot would have been helpful.
One more niggle and then I'm done. There is no information on using Eclipse with other programming languages (a couple of paragraphs in the introduction chapter doesn't really count). I've recently started tinkering with Ruby and have used a Ruby plug-in to allow me to work within Eclipse as I learn the language. This is a wonderful testament to the power and extensibility of Eclipse.
Summary This is a good book. You know it's a good book when you already use the tool (both pure Eclipse and IBM's WSAD) regularly and you find yourself learning things that you had not previously been aware of. If you are working with Java and want a good free IDE that's going to grow with you, then Eclipse is a tool you should try -- and consider this book the User's Guide that would have been in the box if Eclipse came shrink-wrapped.Table Of Contents
- Using Eclipse
- Overview
- Getting started with the Eclipse Workbench
- The Java development cycle: test, code, repeat
- Working with source code in eclipse
- Building with Ant
- Source control with CVS
- Web development tools
- Extending Eclipse
- Introduction to Eclipse plug-ins
- Working with plug-ins in Eclipse
You can purchase Eclipse in Action from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
Eclipse is easily the best IDE i have ever used - especially for java compared to other bloatwares for development like
:)
JBuilder/Netbeans/ Visual Age for Java. IMO, it is also the most easiest one to get familiar with. I have used IBM tools like Visual Age For java & Visual Age for CPP and boy, where they a pain to get started on.
This page has all the shortcuts in the IDE- valuable time savers
Siggy Say, Siggy Do
From the Eclipse page :
Welcome to eclipse.org
Eclipse is a kind of universal tool platform - an open extensible IDE for anything and nothing in particular.
It's an EMACS clone then ?
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
Even during an Eclipse, it's still unsafe to look at Sun.
i've got this book as well as the slightly outdated netbeans book from oreilly. the netbeans book is miles better than the eclipse book. the eclipse book definately reads like an ibm type book. there are not enough pictures and walk throughs as there are explaining every single widget/button/option in extreme wordy detail.
the netbeans was an overall easy read and got the user quickly familiar with the parts of the ide they needed to use.
i'm a heavy eclipse user during my day job mainly b/c i think it's slightly nicer on win32, and i like the debugger more than netbeans. eclipse also seems to require slightly memory footprint and since i haven't yet convinced my manager that having more than 384MB of memory for a java development ide and running a local wl server is absolutely necessarry for maintaining some level of sanity, i'm using what works best for me. at home on a linux platform, i prefer netbeans just because it looks and feels nicer. the gtk+ on linux isn't as nice as the native java look and feel. just my personal preferance.
This should be obviuos, but here we go.
JBuilder is not free software (or even OSS). Borland can restrict the use of the Personal edition in whatever ways they want. Borland can simply discontinue the free edition at any time and leave the users without any option short of buying the paid edition or switching development platform (and this is a major problem for any serious development effort).
You also can't assume Borland will update the product in a timely manner. They can for instance delay the support for a new JDK version for whatever reason and you can do nothing.
In the end, having control over its development platform is strategic for most companies in this business. Im my shop we are moving fast towards completely open enviroment. In most cases only Windows itself is the last piece that must go but the market still requires us to have it around.
Here are the new features from the Eclipse 3.0 Milestones 1 and 2.
2 00306051737/eclipse-news-M1.html 0 M2-200307181617/eclipse-news-M2.html
Got these links off blogdex this morning.
Milestone 1: http://download.eclipse.org/downloads/drops/S-M1-
Milestone 2: http://download2.eclipse.org/downloads/drops/S-3.
I use WSAD and Eclipse 2.0 regularly. WSAD's (Based on Eclipse 1.0) java editor is weak, but the editor in Eclipse 2.0 is among the best I have ever used.
Sure, Eclipse is good, but does it give your mouth a good clean feeling, no matter what?
How are you going to keep them down on the farm once they've seen Karl Hungus?
Then let the team know.
They're currently working on the 3.0 release for Eclipse - one of the topics discussed on the development mailing lists a while back was properly supporting sub-projects. The primary Eclipse team was asking users to submit information on how they would like to see Eclipse support nested projects. If you look through their bug database, you should be able to find the relevant bugzilla entries along with the attached discussions.
"Great men are not always wise: neither do the aged understand judgement." Job 32:9
It could be that for a general experienced java programmer, GUI editors just don't work as well for Java. What with layouts, different ways to do things, etc., designing powerful UI code for Java is different than say for Win32 (and yes, I've done both). Personally, I'm faster just writing straight code from a logical standpoint instead of dragging in code from a physical one. It's a fairly common sentiment on comp.lang.java.* also.
Borland should be afraid. I develop java with Eclipse pretty much exclusively now, and if you're doing server-side java you don't really need anything else. Only thing I haven't figured out how to do is deploy EJB's like Jetace (I use Websphere). Anyone know? Can I export the EJB completely from within Eclipse?
Back on track, check out this plugin: PMD. It scans your classes for unused variables and a few other things. Some code our company paid for had literally hundred of unused strings in a class!
Yes. C/C++ IDE
Cobol
Thos are just a couple of the official ones off hand. There are others floating around out there, including some commercial solutions.( XML/JSP/HTML support, XMLBuddy ... )
Heavyweight chapter on plug-in development? The Java Developer's Guild to Eclipse (Sherry Shavor, Jim D'Anjou, Dan Kehn, Scott Fairbrother, John Kellerman, Pat McCarthy) has a far better section (over half the book) on plug-in development. From what I can tell, the tutorial section of the book is well-done, though I haven't spent much time with it.
If you've ever used Eclipse, I'd recommend the other book. If you're completely new to Eclipse, check out the included tutorials. They're surprisingly well-done.
Even if you aren't a Java programmer, it may be worth having a look at Eclipse as a CVS client. Most graphical CVS clients rub me the wrong way. WinCVS is difficult to use and not intuitive. Try Eclipse - it actually lets you look at the projects on the repository and lets you view the resource history to compare any two files. The branching and mergeing features are very nice as well.
Random is the New Order.