Leon Rosenberg wrote:
Another superb features of an ide (at least eclipse has it):
All good points Leon. Since I like UltraEdit so much, I thought it
might be worth it to tell you how I do these things, and which ones I
can't readily duplicate...
- Search: who's calling this method / constructor.
This is just a search with a regex. I understand that doesn't do
*quite* the same thing, there obviously is something to be said for a
tool having some insight into the code, but I find it does what I need
99% of the time.
- Organize imports, so you always see what this class is _really_ using
(since i got eclipse i never import bla.bla.* anymore)
I can sort imports at least, but true enough, I can't say "show me the
classes that are used by this class". I personally stopped importing
with asterisk a while back so it's a simple matter of discipline to
always import explicit classes.
Things like unused imports are caught by CheckStyle, and UltraEdit has a
nice output window that is clickable... just click on the Checkstyle
error, or the compile error, and I'm brought to that line.
- Quickjump to method definition and jumping through a possible call tree.
UltraEdit includes a function list, so I can always jump to a method
definition. No call tree though.
- Finding hidden bugs like unnecessary else statement, obsolete casts or
unused variables, things your compiler will not tell you
about, but what probably could point to a bug. Right now I have to perform
code review for 7 developers, and it saves me 50% of the time.
I have some hotkeys defined in UltraEdit to run various external tools
either on the current source file or an entire project. CheckStyle is
one of them (along with PMD, JLint and some others). Everything you
mentioned is caught by at least one of these tools.
- Builtin CVS support.
A side note: IDEA has the absolute best built-in CVS support I've ever seen.
For UltraEdit, again it's hotkeys mapped to macros to control a
commandline CVS client. True, I can't do browses, which would be nice,
but again it's a 99% solution for me.
Since eclipse (Jbuilder 3,4 and 5 were ok, but not that good) teams I'm
working with can actually produce better code on lower cost.
Excellent! That's all that counts, whatever tool you choose :)
P.S. I don't like tomcat integration into an ide, or lomboz, but some people
can find it useful too.
I do all my development in Tomcat before sending it up to Websphere for
STest and ATest, and I have semi-integration... I can compile, deploy,
start up Tomcat and open a browser window with a single click (or hotkey
usually). I don't have debugging capabilities, and that would be nice I
admit, but I do just fine without it, again, 99% of the time.
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
