Is it the case that a "project" only deals with a single directory? That
is, if I have two packages (two directories) which are in the same project,
then I would have to have a separate project file for each package? If so,
that doesn't seem right. A "project" is higher-level than a "package". I
should be able to set up a "project" so that it spans multiple
directories/packages.
----------
From: Paul Kinnucan [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, July 20, 1999 11:12 AM
To: Karr, David; 'jde'
Subject: RE: Looking at using JDE as JUST a standalone debugger
At 09:52 AM 7/20/99 -0700, Karr, David wrote:
>Saving a "project" file along with a source file creates problems
for me. I
>have a common source tree which will support several different
>"applications" which I will need to debug at some point in time.
My notion
>of a "project" consists of exactly what I listed in my previous
note. I
>can't assume that any particular source file belongs exclusively to
one
>project.
>
I don't understand why this is a problem. I'm currently developing a
set of
applications that use a common 2D graphics library, called
jgraphics. I
have a project file for jgraphics and a project file for each of the
applications that use jgraphics. This all works very nicely. I can
be
working on AppA and realize that I need to add a method to a
jgraphics
class. I open the source for the jgraphics class and all the
settings for
the jgraphics project are restored. I edit and compile the class and
then
switch back to the AppA source file. All the settings are restored
for
AppA. So all I need to do is to type
C-c C-v C-c to recompile the AppA class. I find it very nice to be
able to
develop the common library and the app in tandem in the same .emacs
session.
- Paul
- Paul
