You're making the assumption that the users of JDE like the industry
standard for IDEs. This is not always true. Personally I like to be able
to just open up a java file and the classpath etc. is set correctly for that
buffer. This is very helpful when I work on multiple projects at once with
different classpaths. I don't have to close a project and open it, I can
just switch buffers.
> -----Original Message-----
> From: Hayhurst, Lyle [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 01, 2000 9:47 AM
> To: [EMAIL PROTECTED]
> Subject: JDE Project Management
>
>
> Hello all, I was thinking about project management in JDE,
> and wanted to
> share my thoughts around.
>
> The current project management paradigm in JDE seems to be
> _implicit_ : ie,
> simply visiting a file in a project causes the project to be
> loaded. This
> can be annoying; sometimes you are just visiting a file to
> browse around,
> and -- whoops! -- JDE loaded up the associated project file.
>
> This paradigm seems unorthodox when compared with the normal
> IDE project
> management paradigm, which normally goes something like this:
>
> File Menu -->
> Open -->
> Project -->
> [ Directory Tree GUI ] -->
> Select project
> <<Project loads>>
>
> Here project loading is _explicit_. Similarly, when you want
> to close a
> project down ( with the idea of loading another ), you do a
>
> File Menu -->
> Close -->
> Project
>
> And all of the files associated with the project will
> disappear from the
> IDE. In JDE, you _can_ do a JDE --> Project --> Load Project
> File, but the
> buffers associated with the previous project are still lying around.
> Annoying!
>
> I guess what I'm trying to get at is it would be nice if the
> JDE project
> manangement environment was more industry-standard IDE-like.
>
> Cheers!
>
> Lyle
>
>
>
