Here's a couple ideas for JDE enhancements (or maybe just glaring
misunderstandings on my part).
1. When you step into a class constructor, skip over the
ClassLoader.LoadClass() call in the Java libraries if it gets made.
2. Show a pseudo "startup command line" used to launch the runtime in
JDEbug in the debugger output buffer, a la the command line that shows when
you run an app, so that you can see the parameters that are getting passed
in in one place.
3. Once the debug target process terminates, keep the menu items under
JDEbug->Show Buffer live while the buffers are around. Right now I have to
hunt around to find their buffers.
4. Can the debugger reuse the CLI, Local Variables, Threads, and debug
Process buffers? They tend to build up over time.
5. Could the debugger process go away automagically after the debuggee
terminates? Right now, I have to do "Exit Debugger" after my debugee
terminates.
6. I get a java window when running JDEbug, and I think it's from the
debugger, not the debuggee as it is still present after the debuggee
terminates. Could this use javaw or, alternately, minimize the window?
Steve
--
Steve Peterson +1 952 948 9729
Principal Consultant FAX +1 612 677 3050
Virtation Technologies, Inc. http://virtation.com
