September 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Ann] Class meta annotations

by Denis Kudriashov

2017-09-25 17:38 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > I agree with guille. We should just called them class annotations. > > Denis what is a declared instance (is it an object returned by the method > having the annotation) > but can we find a better name. > My idea that the method with pragma #classMetaAnnotation is the declaration of annotation. Internally this declaration creates instance of specified annotation which cached by system. And users access all these declared instances for reflection purposes. Also annotation has inst var declarationSelector. > may be effectiveInstances? > I don't like this name. I not understand "effective" in that context. > > > On Mon, Sep 25, 2017 at 5:09 PM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Why calling them meta-annotation and not just annotation? Annotations are >> in general already meta :) >> >> On Mon, Sep 25, 2017 at 5:01 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> >>> Hi. >>> >>> I glad to present one class package which introduces reusable mechanism >>> for first class annotations. >>> >>> The project can be found on github https://github.com/dion >>> isiydk/ClassMetaAnnotation. >>> And I tried to describe why it is needed in my blog >>> http://dionisiydk.blogspot.fr/2017/09/class-meta-annotations.html. >>> >>> And here is overview: >>> >>> Every annotation should be subclass of ClassMetaAnnotation. To attach it >>> to class you create new class side method which will return an instance of >>> the annotation. Method should be marked with pragma #classMetaAnnotation: >>> >>> >>> MyClass class>>specialAnnotation >>> >>> <classMetaAnnotation> >>> >>> ^MySpecialAnnotation new >>> >>> >>> To query annotations from system there are two methods: >>> >>> 1) You can ask concrete annotation class for all declared instances: >>> >>> MySpecialAnnotation declaredInstances >>> >>> 2) You can ask given class for all attached annotations: >>> >>> MyClass metaAnnotations >>> >>> Every annotation includes information about annotated class and the >>> selector of declaring method. >>> All annotations are cached. So it is cheap to query them. There are >>> extra messages to enumerate annotations using block. >>> >>> Now let's discuss it. I think it can be good addition for the Pharo 7. >>> Especially that it is very small code. >>> >>> Also I would like to thank Marcus who helps me realize this concept in >>> Commander and Calypso which I start simplify with this library. >>> >>> Best regards, >>> Denis >>> >> >> >> >> -- >> >> >> >> Guille Polito >> >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> >> CRIStAL - UMR 9189 >> >> French National Center for Scientific Research - *http://www.cnrs.fr >> <http://www.cnrs.fr>* >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >> > >

Sept. 25, 2017

Re: [Pharo-dev] [Ann] Class meta annotations

by Stephane Ducasse

I agree with guille. We should just called them class annotations. Denis what is a declared instance (is it an object returned by the method having the annotation) but can we find a better name. may be effectiveInstances? On Mon, Sep 25, 2017 at 5:09 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Why calling them meta-annotation and not just annotation? Annotations are > in general already meta :) > > On Mon, Sep 25, 2017 at 5:01 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> Hi. >> >> I glad to present one class package which introduces reusable mechanism >> for first class annotations. >> >> The project can be found on github https://github.com/dion >> isiydk/ClassMetaAnnotation. >> And I tried to describe why it is needed in my blog >> http://dionisiydk.blogspot.fr/2017/09/class-meta-annotations.html. >> >> And here is overview: >> >> Every annotation should be subclass of ClassMetaAnnotation. To attach it >> to class you create new class side method which will return an instance of >> the annotation. Method should be marked with pragma #classMetaAnnotation: >> >> >> MyClass class>>specialAnnotation >> >> <classMetaAnnotation> >> >> ^MySpecialAnnotation new >> >> >> To query annotations from system there are two methods: >> >> 1) You can ask concrete annotation class for all declared instances: >> >> MySpecialAnnotation declaredInstances >> >> 2) You can ask given class for all attached annotations: >> >> MyClass metaAnnotations >> >> Every annotation includes information about annotated class and the >> selector of declaring method. >> All annotations are cached. So it is cheap to query them. There are extra >> messages to enumerate annotations using block. >> >> Now let's discuss it. I think it can be good addition for the Pharo 7. >> Especially that it is very small code. >> >> Also I would like to thank Marcus who helps me realize this concept in >> Commander and Calypso which I start simplify with this library. >> >> Best regards, >> Denis >> > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

Sept. 25, 2017

Re: [Pharo-dev] [Ann] Class meta annotations

by Denis Kudriashov

2017-09-25 17:09 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Why calling them meta-annotation and not just annotation? Annotations are > in general already meta :) > First of all we can rename it. We discussed name with Marcus. And our feeling was that simple "class annotation" name is a bit collide with "class properties" which we also have. So we added extra word to the name but maybe it not makes any sense. Also we thought about ClassPragma name. But it is possible that with new class definition we will be able to annotate classes just in place like methods. Also using the name different from pragma is good (or feels good) to get some sign that it uses different mechanizm. > > On Mon, Sep 25, 2017 at 5:01 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> Hi. >> >> I glad to present one class package which introduces reusable mechanism >> for first class annotations. >> >> The project can be found on github https://github.com/dion >> isiydk/ClassMetaAnnotation. >> And I tried to describe why it is needed in my blog >> http://dionisiydk.blogspot.fr/2017/09/class-meta-annotations.html. >> >> And here is overview: >> >> Every annotation should be subclass of ClassMetaAnnotation. To attach it >> to class you create new class side method which will return an instance of >> the annotation. Method should be marked with pragma #classMetaAnnotation: >> >> >> MyClass class>>specialAnnotation >> >> <classMetaAnnotation> >> >> ^MySpecialAnnotation new >> >> >> To query annotations from system there are two methods: >> >> 1) You can ask concrete annotation class for all declared instances: >> >> MySpecialAnnotation declaredInstances >> >> 2) You can ask given class for all attached annotations: >> >> MyClass metaAnnotations >> >> Every annotation includes information about annotated class and the >> selector of declaring method. >> All annotations are cached. So it is cheap to query them. There are extra >> messages to enumerate annotations using block. >> >> Now let's discuss it. I think it can be good addition for the Pharo 7. >> Especially that it is very small code. >> >> Also I would like to thank Marcus who helps me realize this concept in >> Commander and Calypso which I start simplify with this library. >> >> Best regards, >> Denis >> > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

Sept. 25, 2017

[Pharo 7.0-dev] Build #154: 20470 run headless without writable changes file

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #154 was: SUCCESS. The Pull Request #315 was integrated: "20470 run headless without writable changes file" Pull request url: https://github.com/pharo-project/pharo/pull/315 Issue Url: https://pharo.fogbugz.com/f/cases/20470 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 25, 2017

Re: [Pharo-dev] [Ann] Class meta annotations

by Guillermo Polito

Why calling them meta-annotation and not just annotation? Annotations are in general already meta :) On Mon, Sep 25, 2017 at 5:01 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > I glad to present one class package which introduces reusable mechanism > for first class annotations. > > The project can be found on github https://github.com/ > dionisiydk/ClassMetaAnnotation. > And I tried to describe why it is needed in my blog > http://dionisiydk.blogspot.fr/2017/09/class-meta-annotations.html. > > And here is overview: > > Every annotation should be subclass of ClassMetaAnnotation. To attach it > to class you create new class side method which will return an instance of > the annotation. Method should be marked with pragma #classMetaAnnotation: > > > MyClass class>>specialAnnotation > > <classMetaAnnotation> > > ^MySpecialAnnotation new > > > To query annotations from system there are two methods: > > 1) You can ask concrete annotation class for all declared instances: > > MySpecialAnnotation declaredInstances > > 2) You can ask given class for all attached annotations: > > MyClass metaAnnotations > > Every annotation includes information about annotated class and the > selector of declaring method. > All annotations are cached. So it is cheap to query them. There are extra > messages to enumerate annotations using block. > > Now let's discuss it. I think it can be good addition for the Pharo 7. > Especially that it is very small code. > > Also I would like to thank Marcus who helps me realize this concept in > Commander and Calypso which I start simplify with this library. > > Best regards, > Denis > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Sept. 25, 2017

[Ann] Class meta annotations

by Denis Kudriashov

Hi. I glad to present one class package which introduces reusable mechanism for first class annotations. The project can be found on github https://github.com/dionisiydk/ClassMetaAnnotation. And I tried to describe why it is needed in my blog http://dionisiydk.blogspot.fr/2017/09/class-meta-annotations.html. And here is overview: Every annotation should be subclass of ClassMetaAnnotation. To attach it to class you create new class side method which will return an instance of the annotation. Method should be marked with pragma #classMetaAnnotation: MyClass class>>specialAnnotation <classMetaAnnotation> ^MySpecialAnnotation new To query annotations from system there are two methods: 1) You can ask concrete annotation class for all declared instances: MySpecialAnnotation declaredInstances 2) You can ask given class for all attached annotations: MyClass metaAnnotations Every annotation includes information about annotated class and the selector of declaring method. All annotations are cached. So it is cheap to query them. There are extra messages to enumerate annotations using block. Now let's discuss it. I think it can be good addition for the Pharo 7. Especially that it is very small code. Also I would like to thank Marcus who helps me realize this concept in Commander and Calypso which I start simplify with this library. Best regards, Denis

Sept. 25, 2017

[Pharo 7.0-dev] Build #153: 204607-Rename-package-Collections-DoubleLinkedListTests-into-Collections-DoubleLinkedList-Tests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #153 was: SUCCESS. The Pull Request #313 was integrated: "204607-Rename-package-Collections-DoubleLinkedListTests-into-Collections-DoubleLinkedList-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/313 Issue Url: https://pharo.fogbugz.com/f/cases/204607 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 25, 2017

Re: [Pharo-dev] Calypso question

by Ben Coman

On Mon, Sep 25, 2017 at 3:58 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2017-09-24 9:15 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >> anyOf: means >> senders of any of the following message = or >> >> because of: with a list could mean that you expect to find the senders >> of all the message in the list. >> >> Am I clear? >> > > Yes. > But is it good english to say "Senders anyOf: #(do: x)"? Should not it be > "Senders ofAny: #(do x)"? > The second sounds more natural. cheers -ben > > >> >> Stef >> >> >> On Sat, Sep 23, 2017 at 10:37 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> > 2017-09-23 7:54 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> >> >> Ok what is localClassScope? >> > >> > >> > From LocalClassScope you will see only things which are defined in class >> > itself. >> > >> > There are also ClassHierarchyScope subclasses. They show you all things >> > which are visible from related classes depending on what type of >> hierarchy >> > they represent (there are ClySubclassScope, ClyInheritedTraitScope, >> etc). >> > >> > I will add this notes to class comments. >> > >> > Before I introduced ClassHierarchyScope there was only ClassScope (with >> > instance side and class side subclasses). Then I extract >> LocalClassScope. >> > >> >> >> >> >> >> so may be we should rename it anyOf: >> > >> > >> > I not understand it. >> > >> >> >> >> >> >> On Fri, Sep 22, 2017 at 9:54 PM, Denis Kudriashov < >> dionisiydk(a)gmail.com> >> >> wrote: >> >> > Hi >> >> > >> >> > 2017-09-22 20:41 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com >> >: >> >> >> >> >> >> Hi denis >> >> >> >> >> >> I'm doing a pass on the architecture of calypso chapter :) as a way >> to >> >> >> force me to understand it better. >> >> >> >> >> >> Now I do not understand why the following does not work. >> >> >> >> >> >> | env classScope | >> >> >> env := ClySystemNavigationEnvironment currentImage. >> >> >> classScope := env selectScope: ClyClassScope of: {Point. >> Collection}. >> >> >> classScope allClasses >> >> >> >> >> > >> >> > Probably it is not implemented. Each scope should implement what can >> be >> >> > retrieved from it. >> >> > If something was not needed for browser implementation then it will >> not >> >> > work. (I not implemented it). >> >> > >> >> > But try also with ClyLocalClassScope. I did little refactoring and it >> >> > can be >> >> > not reflected in any doc/comment. >> >> > >> >> >> >> >> >> >> >> >> another question >> >> >> >> >> >> packageScope query: (ClyMessageSenders of: #(do: x)) >> >> >> >> >> >> It is returning all the senders of do: and the senders of x >> >> >> or >> >> >> returning all the sender of do: and x >> >> > >> >> > >> >> > It returns methods which sent #do: or #x >> >> > >> >> >> >> >> >> >> >> >> >> >> >> Stef >> >> >> >> >> > >> >> >> > >> >> >

Sept. 25, 2017

[Pharo 7.0-dev] Build #152: 20449-System-SupportTests-package-should-be-renamed-to-System-Support-Tests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #152 was: SUCCESS. The Pull Request #312 was integrated: "20449-System-SupportTests-package-should-be-renamed-to-System-Support-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/312 Issue Url: https://pharo.fogbugz.com/f/cases/20449 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 25, 2017

Re: [Pharo-dev] XPath chapter...

by Nicolas Anquetil

To make all this documentation (booklets) more easily availbale, we could create a link to them in pharo itself for example as a special method, instance variable, or pragma (although I hate pragmas) in the Manifest? nicolas On 24/09/2017 16:27, StÃ©phane Ducasse wrote: > Hi > I'm fully convinced that we can have the best language if we do not > let people find their way super easily to do what they want to do we > will fail. > Documentation is KEY and I feel a bit alone. > Since I always wanted to learn XPath I started to write a chapter on > XPath. I hope that I did not write too many mistakes. > Pull requests are welcome here > https://github.com/SquareBracketAssociates/Booklet-Scraping > I would love to have one booklet on SAX and DOM handling. > Stef -- Nicolas Anquetil -- MCF (HDR) Project-Team RMod

Sept. 25, 2017