StéphaneDucasse
StéphaneDucasse
There is also ``` ClyTextEditor >> sendersOf: selectedSelector self browser browseReferencesTo: selectedSelector inNameResolver: self browserTool selectedClassOrMetaClass ```
When we press the little arrow showing methods of the superclass we get also a problem. ``` ClyShowLocalImplementorCommand >> execute | selectors query | selectors := methods collect: [ :each...
I hacked a first version as. It is bad since it does not take into account multiple methods and in addition it does not work for the down arrows. But...
To be able to work while StMessageBrowser does not support (or maybe this is hidden) class References. I did the following. ``` ClyShowClassRefCommand >> execute "browser spawnQueryBrowserOn: (ClyClassReferencesQuery toAny: classes)"...
I changed my mind. see below
Now I defined also (obviously I'm breaking the scoping) but this is just to be able to continue to work. ``` browseUppercasedReferencesTo: aSymbol inNameRespolver: anEnvironment "browser spawnQueryBrowserOn: (ClyClassReferencesQuery toAny: classes)"...
The tool registry is good because it let us do the experience I'm doing. Now the tools should have the same API within the same tool and this is normal....
Good catch :)
@estebanlm can you help us on this?
Ok I will try to reproduce it.