At 03:33 PM 12/1/99 -0700, Ploski, Karen L wrote:
>Paul:
>

[snip]

>
>Hmmmm...if I use the customize interface that you prefer to see people use,
>then
>instead of directing Emacs to save the values for the current session, I
>could direct
>it to save them across sessions.  Then, when I need to debug the NEXT
>application I
>create, I could just enter the appropriate values for the NEXT application
>at that
>time through the customize interface.
>
>Is this what you would recommend?  If so, then that is what I'll do, and
>that is what
>I'll tell my co-workers to do...I realize it's important to start people off
>on the
>right foot.
>

Here's how I handle this situation. I put every application it its own
directory. All of my applications have the following structure:

AppA
  class                      -> class files go here
  lib                        -> jar files go here
  help                       -> JavaHelp files go here
  src
    prj.el                   -> Contains JDE settings for this application.
    .emacs.desktop           -> Records my Emacs window config (and more)
from previous session
    pkg1                     -> directory for pkg1
    pkg2
  doc                        -> javadoc goes here

The src directory for each application contains a prj.el file and a
desktop.el file. The prj.el file contains the JDE settings for the
applications. See the JDE User's Guide for instructions on how to create
and use prj.el files (it's very easy). The emacs.desktop file records my
Emacs "desktop" from the previous session. See desktop.el for a description
of this wonderful facility. When I want to work on an application, I start
an Emacs session in the app's src directory. Thanks to the emacs.desktop
file, Emacs comes up exactly as it was when I last worked on this
application. All the files that were open then are open now. Even the
command history is restored. Thanks to the prj.el file, all the JDE
settings for this application are in effect. I can start work without
further ado, exactly at the point that I left off in my previous session.

Note that you can work on multiple applications simultaneously. The JDE
notes when you change from a source buffer belonging to one app to a buffer
belonging to another and automatically resets the JDE environment to the
new app's settings.  

>BTW: I have also just installed beta 12: I saw the release notes, and
>started to drool
>as I read them.  At the moment I'm trying to locate the JPDA "package": I
>believe this
>package is Sun Microsystem's pre-release...is that correct?  If so, what do

JPDA is included in JDK 1.3 and is available separately for use with JDK
1.2 at JavaSoft's Developers Connection site. (It does not work with JDK 1.1).

>I need to
>do to "tie" JPDA into the JDE...just specify the path in the JDE Bug JPDA
>Directory
>customize widget?  (I was about to try just that when I saw your message).
>

Yes. Complete instructions for setting up JDEbug are in the
ReleaseNotes.txt file provided with the beta 12 release. The file contains
the release notes for all the JDK  2.1.6 beta releases. The JDEbug
instructions are in the release notes for one of the early releases.

- Paul

Reply via email to