One thing I've found myself interested in is the reverse of the
Dependency browser -- the dependency browser is good for knowing what
particular packages are required and why by the left-most selected
package.

Sometimes I want to know, for a selected package, what other packages
_require_ it, but I don't know whether there's an easy way to do
that..

On Mon, May 14, 2012 at 12:56 PM, Yoshiki Ohshima
<Yoshiki.Ohshima at acm.org> wrote:
>> El 5/12/12 11:43 AM, "Chris Muller" <asqueaker at gmail.com> escribió:
>>
>> Good one, thanks..
>
> At Sat, 12 May 2012 11:55:49 -0300,
> Edgar De Cleene wrote:
>>
>> DependencyBrowser seems an unfinished concept, glad you take it Yoshiki
>
> DependencyBrowser is useful for some specific tasks.  It'd e handy to
> have a menu item to refresh things (an automatic update would not be
> good as it'd delete the entry as soon as you edit and accept a
> method).  One could imagine to analyze the usage of methods, when the
> method(s) with the selector is in one particular package, but that
> would not be perfect and could give false sense of packages.
>
> -- Yoshiki
>
>