>>>>> "David" == Karr, David <[EMAIL PROTECTED]> writes:
David> I'd like to see if I can use JDE as JUST a standalone
David> debugger. I already have good colorization and syntax
David> editing for Java, I just need a good debugger. From what I
David> can see, JDE tries to be much more than I need.
The JDE is as the name suggests a development environment
and does most things. Of course if you only want to use it as a source
level debugger this is your option.
David> From a debugging point of view, it seems like I need to
David> select a "project", which has various attributes, like:
David> 1. run directory 2. classpath 3. main class 4. other "java"
David> command-line arguments 5. run class command-line arguments
David> From what I can see, JDE makes me reconfigure all of these
David> things if I need to work on a different "project".
No.
The projects are there for you to use if you want. The idea
is that you can set up these (and lots of others) things as
defaults. Additionally you can (if you wish) define project
directories which are something like a snapshot of your current
settings. These snapshots then get loaded depending on what file you
are currently editing. It means for instance if you have two projects
one a 1.1, and one a 1.2 project you can have JDE automatically switch
compilers and classpaths as you edit different files. If you have
always keep your source in the same places, always want to use the
same jdb then there is no problem. Just dont use the projects.
Phil
