Re: Java IDEs *Le sigh*
"Nate the Capricious" <NatLWalker@gmail.com> wrote in message
news:1146095632.329638.154010@y43g2000cwc.googlegroups.com...
Intuitive as in easy to pick up.
Intuitive IDEs have features like Dynamic Help, collapsible
toolbars/panes, etc.
I'm not sure why "collapsible toolbar/panes" would be intuitive, but
Eclipse has those (click on the button that looks the "minimize" icon from
Windows). Eclipse has dynamic help too, but I've never had to really use it
(that's how intuitive Eclipse is! ... for me, anyway).
in the likes of VS, Sun's IDE, Netbeans,
and JDeveloper.
I've only used Eclipse and VS. I don't like how, when I tell VS in debug
more to "run to this line", it runs right past it and keeps going. That
wasn't very intuitive (as in easy to pick up) behaviour to me. I don't like
how when I click on a method call and say "Show me where this method is
declared", it tells me that the method isn't declared anywhere (when I know
it is).
Maybe my install of VS was buggy or something, but my experience of VS
was that it was not very intuitive. I mention this not to say "You're wrong,
VS is bad, Eclipse is good", but to point out that people's experiences with
IDEs may not be universal. So when you say "Look at VS as an example of
intuitive", people might get the wrong idea.
I can see how the Perspective system (or
view system as some call it) would be intuitive for some; but
I'm not *that* much of a noob that I need everything to be
sorted out in such a way. There is always a 2 second pause
while the JVM garbage collects and/or Eclipse switches
perspectives, it seems. And that's annoying.
On my machine (Pentium 4 1.8Ghz, 1 GB RAM), there's a noticeable delay
when switching perspectives, but it's less than 1 second. I'm guessing you
might get better performance out of Eclipse if you had more RAM.
[...]
Also, for the person who was talking about J2EE features and what-
not. My instructors demand that we properly document our projects;
design documentation, implementation, code comments, and end-
user documentation. That is why I like the UML features. It comes
in handy for putting some aspects of an application in a more visual
term; and I routinely round-trip code/etc. and use those in my docs.
Not sure if that person was me, but I mentioned "forget about J2EE for
now" because every tutorial I've seen on J2EE assumes you've already
"mastered" J2SE. Note that "writing documentation", "implementation", "code
comments" and "end-user documentations" are concepts that exist in J2SE as
well. I've never actually touched J2EE, but I write documentation, I
implement stuff, I comment my code, and I provide documentation to the end
user. I use UML too. That's not what J2EE is about. J2EE, as far as I can
tell, is about multi-tiered web services.
- Oliver