Maybe OT, but does anybody know what feature the normal jde-xref has
that isn't done faster and without all the db stuff by the jde-usages
plugin? While I really think jde-xref is cool, maybe we should think
about integrating jde-usages itself...
jtl
signature.asc
Description: This is
I think jde-usages is a perfectly acceptable replacement, and there is
really no difference in functionality as far as I know.
On Aug 18, 2004, at 4:08 AM, Jens Lautenbacher wrote:
Maybe OT, but does anybody know what feature the normal jde-xref has
that isn't done faster and without all the db
There are no missing pieces in jde-usages as far as I know too, but it
does some things
differently, based on my personal preference:
1) Instead of creating a new buffer each time you call one of the
usage functions, jde-usages just reuses one buffer called *usages*
2) I did not implement the
When using the jde-xref feature, I have experienced a problem.
Syndrome: After jde-xref-make-xref-db, I moved the cursor to a method
in one of my classes ClassA and did a C-c C-v a, I got this in the
mini-buffer:
Wrong type argument: listp, com.x.x.ClassB
The ClassB is the super class of
I submitted a patch to fix this... I believe it is in the latest beta of JDE
(2.3.4beta5).
Raul
On Tue, 17 Aug 2004, Ping Liang wrote:
When using the jde-xref feature, I have experienced a problem.
Syndrome: After jde-xref-make-xref-db, I moved the cursor to a method
in one of my classes
