Package tags for extensions
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. Cheers. Uko
Hi Yuri, 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. Esteban On 07 Apr 2014, at 05:54, Yuriy Tymchuk <yuriy.tymchuk@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.
Cheers. Uko
Hi Esteban, thanks for explanation. Uko On 07 Apr 2014, at 13:21, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi Yuri,
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.
Esteban
On 07 Apr 2014, at 05:54, Yuriy Tymchuk <yuriy.tymchuk@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.
Cheers. Uko
Hi Esteban, Yuri, It's really nice to hide extensions as objects and not anymore as protocols. I have been working with that for more than a year now, and it's very nice not to have to write anymore *Name-Of-Package to create extensions. Thierry ________________________________________ De : Pharo-dev [pharo-dev-bounces@lists.pharo.org] de la part de Esteban Lorenzano [estebanlm@gmail.com] Envoyé : lundi 7 avril 2014 13:21 à : Pharo Development List Objet : Re: [Pharo-dev] Package tags for 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. Esteban On 07 Apr 2014, at 05:54, Yuriy Tymchuk <yuriy.tymchuk@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.
Cheers. Uko
participants (3)
-
Esteban Lorenzano -
GOUBIER Thierry -
Yuriy Tymchuk