I think the semantic parser package would enable this at some level.
It's just a matter of designing an implementing how it would work, and
being patient while it ran on large projects. ;)
Speedbar also supports arbitrary display programming also, so using
speedbar as a display mechanism would work. Reto Zimmermann (author
of vhdl-mode) did this for VHDL.
Eric
>>> "Nascif Abousalh-Neto" <[EMAIL PROTECTED]> seems to think that:
>What about some way of quickly moving around in the hierarchy tree? I'm really
>missing a class hierarchy browser functionality, like the one provided by
>oo-browser. I would expect that getting all the descendants of a class would
>imply a huge search on other files in the project (maybe not, I hope there is
>an easier way) but I think that a quick way to go to the ancestor (and the
>implemented interfaces ) definition would be useful.
>
>Paul Kinnucan wrote:
>
>> At 12:52 PM 5/2/00 -0500, you wrote:
>> >In the speedbar, there are buttons for expanding and un-expanding
>> >classes, interfaces, variables, etc. However, there isn't a
>> >corresponding button for methods. Why not? This would be more useful to
>> >me than the button for classes, for examples. Thanks
>> >
>>
>> Funny, you should ask. I've been thinking about this issue recently and am
>> interested in your input. First, some background.
>>
>> The next JDE release, which is imminent, will provide support for the
>> latest, parser-based version of Eric Ludlam's speedbar. (You will be
>> required to download this version plus Eric's new parser generator package
>> for Emacs, semantic, from Eric's web page.) With this version, the first
>> expansion level for each source file will have three buttons: Package,
>> Types, and Misc. These names were chosen by Eric to be language
>> independent. In the case of Java, expanding the Package option will show
>> the java package to which the file belongs; expanding the Types entry will
>> show all the top-level classes in the source file; expanding the Misc
>> button will show all the import statements in the file. (This entry may be
>> changed to Dependencies.)
>>
>> You will be able to expand the entry for each class to show the methods,
>> fields, and inner classes defined in that class plus the class's parent.
>> You will be able to expand each method entry to show its arguments.
>>
>> The following is an example of how the speedbar will look:
>>
>> + A.java
>> - B.java
>> - Package
>> com.mycompany.pkg1
>> - Types
>> - class B
>> - method1 ()
>> - (arg1
>> @ String
>> + |arg2
>> + )arg3
>> @ void
>> + method2 ()
>> + field1 =
>> - field2 =
>> @ BeanInfo
>> + field3 =
>> - class InnerClassA
>> + InnerClass AA
>> + method1 ()
>> + field1 =
>> + class InnerClassB
>> > Frame
>> - Misc
>> import java.lang.String
>> import java.awt.Frame
>> + C.java
>>
>> The new version of speedbar does not support expansion of methods. However,
>> Eric and I have discussed the desirability of this capability. The benefit
>> I can see would be the ability to navigate to variables and classes defined
>> within methods. The tradeoff would be greater time to parse the buffer.
>>
>> I'd be interested in yours (and others) input on this issue and on the new
>> speedbar design.
>>
>> - 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
>
