Re: [Pharo-dev] [Ann] Commander. Command pattern library

2017-04-12 15:27 GMT+02:00 Alexandre Bergel <alexandre.bergel@me.com>:

I see. But why not to let the class subscribe to what it needs? Maybe something like:

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Command subclass: #ClyShowClassRefCommand

I guess you mean:

ClyShowClassRefCommand class>>registerFor: aCommandActivator aCommandActivator add: self for: *ClyClassSystemBrowserContext*. aCommandActivator add: self for: *ClyMethodBrowserContext*.

How different applications will extend such registration? Probably they will need multiple version of #registerFor:. And system will need to find them somehow. For example by pragma. No?