At 12:18 PM 4/17/00 -0500, you wrote:
>Taking a look at the quick start I worked up, I have a couple suggestions
>for changes that would make the Hello, World case easier.
>
>1. On win32, consider using JDE_Run_Java_VM for JDEbug since
>JDE_Run_Java_VM_W doesn't seem to be working.
>
Aha, I get it. You must be using NT/XEmacs. Yes, you must be use java.exe
with NT/XEmacs because the NT/XEmacs process launch code is broken. You
must use java.exe to launch command-line apps like the JDEbug backend and
javaw to launch GUI apps. You cannot successfully interact via XEmacs with
an app that has both a GUI and standard I/O. This is one of the reasons why
I constantly urge people interested in doing serious Java development on
Windows to avoid NT/XEmacs like the plague. (Other reasons are that it is
very unstable, leaks memory like a sieve, and may not even come up on your
system depending on what drivers you have installed.) See the JDE mailing
list archive for a more extensive discussion of why I recommend avoiding
NT/XEmacs.
BTW, my quarrel is not with XEmacs per se. Only with the current NT
version, which is still, in my view, of alpha quality at best. I'm sure
that the hard-working NT/XEmacs team will eventually iron out the bugs. In
the meantime, I think Windows users who are primarily interested in getting
work done are better off sticking with GNU Emacs.
>2. If JDE_Global_Classpath or JDE_DB_Source_Directories are
>empty, consider defaulting them to the directory of the class we're
>running so that it's in the classpath and its source is available.
>
I believe that the vm classpath includes the current directory by default.
The suggestion for jde-db-source-directories is a good one and I'll
implement it.
>3. The user has to quit and restart in order to get the JDEbug menu to
>display. Is it possible to sense that the user changed their properties
>file to request JDEBug and show the menu without a restart?
>
Note that you don't need to restart Emacs. Simply close the source file and
reload it. However, it should be possible to do what you suggest and I will
try to impliment it ASAP.
>4. With JDEbug you set the path to the JDK. If unset, could
>JDE_Run_Java_Vm_W and JDE_Run_Java_Vm use that path + /bin to find
java/javaw?
>
Yes, but I think a better solution would be to have general variables for
specifying the JDK that you want to use that would be used everywhere by
default. Something like
jde-jdk
whose value would be a cons of the version number and its home directory,
e.g.,
("1.3" . "c:/jdk1.3")
The JDE would then use this information to find the compiler and vm, the
JDPA libraries, etc. You could still override the values, using
jde-run-java-vm-w. For example, you could jde-compiler to specify use of
jikes instead of javac.
This would make it easier to write a command that would allow you to switch
JDKs. Again, I'll try to implement this soon.
- Paul
------------------------------------------------------------
TECH SUPPORT POLICY
I respond only to requests that contain a complete problem report. The
easiest way to ensure that your report is complete is to include the output
of the JDE->Help->Submit Problem Report command in your request.
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JDE website: http://sunsite.auc.dk/jde/
JDE mailing list archive:
http://www.mail-archive.com/[email protected]/maillist.html
