Re: [ jEdit-users ] Broken search macros in 3.1final

[Bryan T. <bry...@ya...>]

--- Jeremy Wadsack <jwa...@wa...> wrote:
 
> > It would be nice to have a plug-in that would tell you the dependencies
> > within your project, so that you could easily know all the other project 
> > members that
> > call a certain part of the code. I'm imagining JBrowse, parsing the entire
> > project, with the ability to show "references" and "referenced by" classes,
> > methods, fields, macros, etc...
> 
> How about javadoc? It's not a plugin, but it will tell you all the 
> 'uses' and 'used by' for each method in every class it documents (in a 
> session).

I think you are exagerating javadoc's capabilities, but even if it did this,
having to run javadoc every time you wanted to check dependencies would be a
serious limitation. Compare this with JBrowse which does "live" parsing and
presents it's results in a dockable window that jumps to the appropriate buffer
location when you select a nodes.

Essentially, project dependencies are a directed graph: program units (classes,
macros, etc...) are nodes and the 'uses' relationship is an edge. Calculating
that graph and presenting it to the user somehow (perhaps using a tree control)
to allow rapid navigation in the editor would add very valuable functionality.


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/