> > On a resource constrained box your best bet is probably JDEE
> > the Emacs based IDE.> Isn't that ironic, Emacs used to be regarded as a resource hog before Java IDEs came along...
Nothing is a resource hog when compared to a java IDE.
> > Its a bit basic as IDEs go
> Hmm, not really. Code completion, code wizards, code
> checking, Ant support, a built-in Java interpreter (really sweet for
> on-the-fly testing)... Only thing really missing is refactoring support
> but there are some attempts to add even that. And, of
> course, GUI design tools :-)I use emacs and jdee on linux day in and day out for my coding needs, so I have some experience with the features of emacs and jdee. Jdee just doesn't compare (from a features and ease of use standpoint) to most of the mainstream IDEs currently available. The code completion is inconsistant at best, the code checking isn't bad and the ant support is acceptable, but nothing to write home about (jedit has much better ant support, as do the IDEs). The built in interpreter is *very* nice, but also available elsewhere. They are getting close on refactoring from what I understand, but its not complete yet. So there is quite a few places where emacs and jdee fails from a bells and whistles standpoint.The main thing emacs has going for it is that you dont have to touch the mouse, and you can extend it easy with a bit of elisp. That and every kind of source imaginable is supported in emacs, so if you have a multi-langauge project emacs is by far the best bet.
> You can also complement it with the many Emacs extension packages out there.
> I for one use JDEE plus ECB, the Emacs Code Browser (http://ecb.sourceforge.net/)
> which gives the package a definitive IDE "flavor".Ecb is very nice, I wouldn't use emacs without it.
> JDEE has its own debugger but if you want something more
> graphical for the interface I highly recommend JSwat
> (http://www.bluemarsh.com/java/jswat/). Both tools integrate nicely with Emacs and JDEE.I wouldn't really call what they do integration. They can all be used easily together, but its not like jswat will read your ant files to find the source and classpaths, nor will emacs pass it. Emacs can launch jswat and vise-versa but thats not really integration. I only raise this to illustrate the differences between and integrated debugger and the seperate editor/debugger senario you describe.
That being said the emacs, jdee, ecb, and jswat pretty much describes my java development environment.
> > and emacs has a steep learning curve,
> Another urban legend, given that it has
> 1) a great help system. You can even ask what a keyboard shortcut will do!
> 2) a built-in tutorial, hands-on tutorial.My rosy red ... well you get the idea ;) For someone who is used to a graphical environment it is a difficult learning curve. It was only a few years ago that I went through this so I remember it vividly, its only after a few weeks or months that the key groups become automatic and its days or weeks before you have to stop looking up each key combination.
> On top of that you can configure pretty much everything, making it behave more like the tools
> you are familiar with. For example, check the CUA mode (http://www.cua.dk/emacs.html)
True but from a newbie prospective this configurability makes it harder, not easier to learn. Of course, once learned I can't imagine giving it up.
CONFIDENTIALITY NOTICE: This e-mail and its attachments may contain confidential, proprietary, and/or privileged information which is legally protected from disclosure. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is strictly prohibited. If you received this e-mail in error, please notify the sender immediately and appropriately delete the material from your computer. Thank you.
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
