>>>>> "Paul" == Paul Kinnucan <[EMAIL PROTECTED]> writes:
>>
Ivana> Is something like this already available?
>> As someone already mentioned JDE has some support for this,
Paul> ^^^^^^^^^^^^
Paul> Some support??!! The JDE's support is complete unlike the
Paul> very limited ffap solution that you propose.
Hey - sorry if I offended you! That was not the intention at all. And
please remember that this "package" was created in about 30 minutes of
tampering on the keyboard help the Ivan guy which was tired of
requiring etags for doing this.
And as he states - not much is needed to do this for normal
java-operation. It is all a matter of searching directories for the
names - that means it will work even without JDE and it also works
beautifull together with JDE.
Paul> The
Paul> jde-show-class-source command finds the source for any class
Paul> that exists on the class path defined by the
Paul> jde-global-classpath variable or CLASSPATH environment
Paul> variable and whose source is in one of the paths specified
Paul> by jde-db-source-directories, unlike your solution, which
Paul> does not work for JDK API classes or jar libraries or
Paul> projects where source files and class files are stored in
Paul> separate directories.
Did you see the TODO item about adding support for searching other
directories thant the one mentioned in CLASSPATH ?
And does JDE examine the JAR files for .java files and extract them to
be shown ?
>> but for me it is dreadfull as it seems to require the startup
>> of the
Paul> beanshell
>> which is not always working correctly - so I have just put this
>> solution together for you all to enjoy :)
>>
Paul> I have no problems with the Beanshell on any of the Windows
Paul> platforms and occasionally have to issue the first command
Paul> that requires the Beanshell twice on Solaris but this is
Paul> minor.
Paul> If you are having problems with the beanshell, please report
Paul> them. A lot of JDE functionality, e.g., the wizards, depends
Paul> on the Beanshell. Thus, if it is not working for you, you
Paul> are missing out on key features of the JDE.
Im using the features in BeanShell and I think it is great.
But I have tried to set jde-db-source-directories
But for finding source files my ffap-solution has the following
advantages:
+ Does not require JDE-mode (but who is not using this :)
+ Is faster than BeanShell as it does not try to resolve the class name
+ Does not require the java file to be compiled
+ Beanshell does not (yet?) support automatically loading class'es
which did not exist when it was invoked
+ Less memoryintensive as is does not need to communicate
with the beanshell (which can bring my Pentium 166Mhz, 64 meg. to
its knees
The negative sides is:
- Does not resolve the class name (well - this is not needed in
practice to find the source files)
- Does not support multiple instances of the same class name (can be
added if one wishes)
- Does not search other paths than classpath (can easily be added if
one wishes)
So the bottom line is that this package makes ffap usable when
developing java and it has advantages over JDE and vice versa.
Primarily it is pure elisp and faster than using the beanshell and is
usable for java files which is not compiled (or not compiled when
beanshell was invoked.)
So can't we just live happily side by side ? :)
Thanx for a great java enviroment..
--
Max R. Andersen ([EMAIL PROTECTED])
