[Pharo-dev] Package tags for extensions
estebanlm at gmail.com
Mon Apr 7 07:21:29 EDT 2014
is no-issue and no-work in progress: is like that by design. extensions are package related and not tag related.
so… you can name an extension MyPackage-B, but it will still be going to rpackage extensions.
one of the things we need to continue improving is protocols… now they are objects (before they were just strings), but extensions are still name matching conventions, and they should be also objects (like ExtensionProtocol) or something like that.
but well… future stuff.
On 07 Apr 2014, at 05:54, Yuriy Tymchuk <yuriy.tymchuk at me.com> wrote:
> Hi guys,
> Now we have tags for packages in Pharo 3, and it’s very cool. So if I select a tag ‘A’ in ‘MyPackage’ I will see all classes from category ‘MyPackage-A’. On the other hand if I’m extending another class with a protocol ‘*MyPackage-B’ I can’t see that class under the ‘B’ tag. Is this some kind of issue or it’s still a work in progress.
More information about the Pharo-dev