[news.eclipse.tools] Re: Call for screenshots

["Bob Foster" <bob@xxxxxxxxxx>]

"Harald Niesche" <harald@xxxxxxxx> wrote in message
news:akb9cb$4a9$1@xxxxxxxxxxxxxxxx
> "Bob Foster" <bob@xxxxxxxxxx> wrote in message
> news:ak900f$9o8$1@xxxxxxxxxxxxxxxx
> > "I admit it's been a few months since I looked at it, but last time I
> looked
> > it didn't even have a "File, Open" option on its menus. EVERYTHING has
to
> be
> > in some kind of project, and you couldn't even pick or choose files in a
> > directory, it would import EVERY file in a directory."
> >
> > Lots of people can't get past Eclipse's inflexible use of the file
system.
>
> Those people have probably not worked with any of the other IDE's for more
> than ten minutes (you don't need longer to collect the material for a
> review).

Those people are professional programmers who have been around a heck of a
lot longer than Eclipse.

Bob

> I really like the fact that everything in the filesystem becomes part of
the
> project. I make heavy use of CVS and if a file is no longer needed I
delete
> it in CVS. No need to explicitly ignore things in the filesystem.
>
> IDE's that force you to add everything manually (like, eg. Visual Studio)
> are such a pain in the lower back -- and they force the whole team to use
> the same IDE, otherwise some people won't see some of the files.
>
> I think it's great, that there is such a thing as a 'standard project
> layout' (and with source folders one can really do a lot of things).
>
> Another counter-example: the Apple ProjectBuilder lets you define Java
> classes' package independent of the folders the .java file is in (they
copy
> the files before compiling). That is really quite flexible, but I can
never
> seem to find the classes I'm looking for (which is in part due to the
> horrible classbrowser, which was state-of-the-art ten years ago ...).
>
> Anyway -- I had not noticed that there is no File|Open ... menu in Eclipse
> until I read the post quoted above.
>
> Just my EUR .02 :-)
>
> Harald
>
>