A new version of jde-usages is available : http://prdownloads.sourceforge.net/jde-usages/jde-usages-0.9.1.zip?download
I've updated the docs on the website (http://jde-usages.sourceforge.net/) and have added some screenshots (http://jde-usages.sourceforge.net/screenshots.html) This version tries to find the exact location of a method call on a line, which is the first step towards a rename method refactoring. It uses a combination of regexps and jde-parse.el functions and can avoid comments and strings, so throw your real-life code at and let me know if anything breaks. >From the release notes : ------------------------------------------------------------------ Version 0.9.1 * Type Hierarchy buffer: (M-x jde-usages-display-type-hierarchy or Jde-Usages->Inheritance Tree->Type Hierarchy) This command displays a view which combines some of the information in the subclasses and superclass views. It shows all the subtypes - all derived classes/interfaces and classes that implement the interfaces, and the direct super classes. The interfaces implemented by this class are not shown in this view, only the superclasses view shows them. * Key bindings for class tree buffers The *subclasses*, *superclasses* and *type-hierarchy* buffers have the following single letter keybinding to view a different type of class tree buffer for the class name under point. `t':type hierarchy `a':superclasses (ancestors) `d':subclasses (descendants)`q':delete window Typing '?' in one of these buffers will show a message listing these keybinding. * *usages* changes - When navigating to method calls from the *usages* buffer, point goes to the exact location of the call in the source. Earlier it would just be placed at beginning of the line with the call. It makes use of jde-parse-* functions and works even when there are multiple calls to the same method on a line. It does not get confused by things that look like a call to the same method that are in comments or inside strings or by method calls to the same method name in an unrelated class. - Clicking on the first line of the usages buffer takes you to the method definition * jde-open-class-source-with-completion used ido style completion. If (the amazing and wonderful) ido-mode is active, ido-mode style completion will be used for class names. Ido is included in CVS Gnu Emacs. It replaces iswitchb and offers the same type of fast switching for opening files as well as switching buffers. * motion-sensitive buffers Jde Usages->Options->"Motion Senstive" Buffers or customize jde-usages-buffers-are-motion-sensitive If this option is enabled moving the cursor in any of the jde-usages buffers will automatically make the corresponding line of source visible in the other window. * tag/caller highlighting Jde Usages->Options->"Use Highlighting" or customize jde-usages-highlight Momentarily highlights a tag or method call before moving to it. When `jde-usages-buffers-are-motion-sensitive' is on the highlighting happens in the source buffer while moving around in the usages buffer, which remains the current buffer. * Ecb integration: Make jde-usages easier to use with ECB. (This is not turned on by default you have to say M-x jde-usages-load-ecb-integration or Jde-Usages->Options->Load ECB Integration) For now this does the following things: 1) Adds a jde-usages submenu for the ECB methods buffer. 2) Add s the jde-usage buffer names to ecb-compilation-buffer-names so they appear in same location as a compilation buffer. 3) Sets jde-usages-window-height to nil so that the height of the jde-usages windows is only controlled by ecb-compile-window-height. * Unit test framework + unit tests ------------------------------------------------------------------ Suraj
