On 12/03/10 06:51, Viktor Klang wrote:
On Thu, Mar 11, 2010 at 9:43 PM, Peter Becker <peter.becker.de
<http://peter.becker.de>@gmail.com <http://gmail.com>> wrote:
The current generation of IDEs already supports this navigation
approach, just not the visualization. I hardly ever go through the
file hierachy to find a file to open, I use the shortcuts to open
types or resources, I use the shortcut to go into a method that's
called, I find all callers via another shortcut or hit a key to
see the hierarchy for an object. And then there is the object
browsing, hot code replacement and all the other cool stuff in the
debugger.
If you are still using vi/emacs/whatever you should probably go
back and check out the keyboard reference chart of a proper IDE. I
only recently converted a hard-core vi user to Eclipse (or at
least an Eclipse/vi combo) -- it is pretty easy to see an IDE just
as a glorified text editor, in which case sticking with vi makes
sense if you already know it. But an IDE is much more than that,
but it is not all that obvious. The code bubbles just make it
obvious, but that by itself is a major achievement.
100% of the time I'm not interested in what file the code is in - I
just want to jump to the declaration or definition of a type or
method. IMHO files are not a good fit for organizing code.
Frankly: I find tree-shaped hierachies the even worse part of organizing
code (or anything else). A lattice, my virtual kingdom for a lattice!
Peter
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
