At 06:42 PM 8/31/99 +0000, [EMAIL PROTECTED] wrote:
>
>I would like to add my voice to the others who have objected to linking
>frames with projects. I tend to arrange my windows (emacs frames) to fit my
>screen and I don't want ones popping up just anywhere on the screen.
>
Wow, I never imagined that anyone would object to having projects in
frames.
Eric, the frames feature is going to be completely OPTIONAL.
>I also find the JDE project file a little awkward to work with because, as
>I mentioned in an earlier email, JDE puts all the settings in the project
>file instead of just the ones that you've set for the particular project.
>
Again, it's a BUG, not a feature. I just haven't gotten around to fixing it.
I thought I had save-changes-only working in the very first release of the
prj.el capability but somehow it doesn't work. As soon as I can figure out
why, I'll fix this.
> I would vote for having these changes to project files:
>
>1. Store a JDE version number in the project file so that JDE can inform
>you that you've got an old project file.
Excellent suggestion.
>2. Only store changed settings in the project file.
Yes, yes, yes.
>3. Provide away for environment variables or functions to locate things
>like the compiler.
>
Well, you provide me with some more details. What exactly are you suggesting?
Right now, if you include the JDK bin directory in your system command path,
the JDE will find java, javac, and jdb right out of the box. I don't see what
is to be gained by adding extra environment variables for this purpose.
- Paul