Hi Chris,

I understand you concern. When I introduced the changes that you 
mentioned, I thought that the HierarchyBrowser was just another browser 
like the PackagePaneBrowser and that the registry should be the one 
deciding which browser to use.

But now I see that there is no HierarchyBrowser but that this is a 
regular Browser but only invoked different.

So I see two different courses of actions.

1. revert my change and TURN OFF the #alternativeBrowseIt preference.

This preference is wrong to have it enabled by default because without 
prior notice it changes the browser to be used with <cmd>-b.

2. Make a preference which will control the use of the HierarchyBrowser.

Note that the purpose of #alternativeBrowseIt has nothing to do with 
which browser is used. So the fact that the preference changes the 
browser seemed a bug to me. And one very annoying If I might add. 
Suppose that you had installed the RefactoringBrowser, then every time 
you did <cmd>-b on a ParagraphEditor instead of a RB what you got was 
the regular Browser.

For this last one I can submit a .cs later today or tomorrow.

Regards,
Hernán

Chris Muller wrote:

 > I just noticed that alternativeBrowseIt no longer works for opening a 
Hierarchy
 > browser instead of a package browser.  So we just have the two 
browsers that
 > are 99% the same (e.g., 1) showing the package-category in a separate 
pane or
 > 2) simply following a dash "-" in the first pane), and 
alternativeBrowseIt
 > appears to provide no alternative.
 >
 > I traced the cause to be the change made to 
ParagraphEditor>>browseClassFromIt
 > by hpt on 10/2/2004.
 >
 > I understand the intent is to make the system use the new SystemBrowser
 > registry, which I think is great, but can we figure a solution that 
respects
 > those who prefer the Hierarchy browser?  All the various browser 
frameworks;
 > standard, Refactoring and Omni all have Hierarchy browsers now don't 
they?  I
 > don't know whether we need "SystemBrowser hierarchy new" or 
"HierarchyBrowser
 > default new" or something else.  I'm not expert in these browser domains,
 > thanks..
 >
 >