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

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

by Stephane Ducasse

I would prefer to remove the meta. because class instance variables are not class meta instance variables :) On Mon, Sep 25, 2017 at 5:59 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> On 25 Sep 2017, at 17:38, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> I agree with guille. We should just called them class annotations. >> > > The problem that I see is that people will confuse them with per class > properties (and pragmas, should we add them). > > If I hear âclass annotationâ I think that this is something visible in the class > definition pane. > > But I have no strong opinion, that is, if everyone else thinks the name is good > I am ok with it. > > Marcus > >

Sept. 26, 2017

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

by Stephane Ducasse

Effective means instances. Because I do not understand what declared are. On Mon, Sep 25, 2017 at 5:57 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 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. 26, 2017

[Pharo 7.0-dev] Build #157: 20416-Add-the-notion-of-a-Cursor-owner

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

There is a new Pharo build available! The status of the build #157 was: SUCCESS. The Pull Request #299 was integrated: "20416-Add-the-notion-of-a-Cursor-owner" Pull request url: https://github.com/pharo-project/pharo/pull/299 Issue Url: https://pharo.fogbugz.com/f/cases/20416 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 26, 2017

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

by Ben Coman

Shhh... The first rule of meta-club is we don't talk about meta-club. cheers -ben On Mon, Sep 25, 2017 at 11: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. 26, 2017

Re: [Pharo-dev] STON question :)

by Sven Van Caekenberghe

Stef, > On 24 Sep 2017, at 12:26, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi Sven > > For Moose we are wondering if we can use STON to save/load models > instead of MSE. > - I'm sure we can :) > > Now my little friends would like to kill two or three birds with the > same stone :) > > Would it be possible to use STON to handle cycles but to generate JSON > compatible > in the following sense: > > Class { > "id": 123, > "name" : "A" > } > > => > > { > "id": 123, > "type" : "Class", > "name" : "A" > } > > It means that we could be able to output an extra field and when we > read that the materialiser > would create an entity based on the type field for example. > > Am I thinking something totally wrong? I am not sure how to answer. It should be possible to use STON as it is, no ? JSON is different, as you know. NeoJSON was not designed to work with such dynamic types, its optional mapping mechanism works with a static type map. STON is a format with an implementation, it is not designed as a general purpose object visitor. Sven > Stef

Sept. 26, 2017

[Pharo 7.0-dev] Build #156: 20448-WriteBarrierTests-package-should-be-renamed-to-WriteBarrier-Tests-package

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

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

Sept. 26, 2017

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

by Marcus Denker

> On 26 Sep 2017, at 10:45, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > +1 just call them class annotations. "annotation" itself already means "meta-information" > > What are class properties ? You can say: Object propertyAt: #hello put: true. e.g instead of checking if the name starts with a certain substring, we now implement #isObsolete like this: isObsolete "Return true if the receiver is obsolete." ^ self propertyAt: #obsolete ifAbsent: false

Sept. 26, 2017

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

by Denis Kudriashov

2017-09-26 10:45 GMT+02:00 Damien Pollet <damien.pollet(a)gmail.com>: > +1 just call them class annotations. "annotation" itself already means > "meta-information" > > What are class properties ? > Any class has dictionary of arbitrary properties: MyClass propertyAt: #testKey put: #testValue > How do annotations relate to Magritte? I'm guessing Magritte descriptions > are a specific kind of annotation already, right? > For the class side descriptions yes. But for instance side not because they looks like object specific annotations. > > About #declaredInstances: you could do MySpecialAnnotation new in a > playgroundâ¦ but that instance would not be attached to any class. I think > the point of that query is to return the annotation instances that do come > from an actual class with an actual method with the <classAnnotation> > pragma. > yes. > > BTW, what if the method with <classAnnotation> returns a different result > each time? > All annotations in system are collected and cached when you first time query for any of them. So you will work with same annotation instances until the cache will be reset. But annotation redefines equality in the way that two annotations from same method will be equal after cache rebuilt. > > On 26 September 2017 at 03:11, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > >> Denis Kudriashov wrote >> > Also I would like to thank Marcus who helps me realize this concept in >> > Commander and Calypso which I start simplify with this library. >> >> Embarrassingly, I'm not quite clear on what this all means so I'll be >> eager >> to hear the results of the case study with Commander and Calypso! >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> >> > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet >

Sept. 26, 2017

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

by Damien Pollet

+1 just call them class annotations. "annotation" itself already means "meta-information" What are class properties ? How do annotations relate to Magritte? I'm guessing Magritte descriptions are a specific kind of annotation already, right? About #declaredInstances: you could do MySpecialAnnotation new in a playgroundâ¦ but that instance would not be attached to any class. I think the point of that query is to return the annotation instances that do come from an actual class with an actual method with the <classAnnotation> pragma. BTW, what if the method with <classAnnotation> returns a different result each time? On 26 September 2017 at 03:11, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Denis Kudriashov wrote > > Also I would like to thank Marcus who helps me realize this concept in > > Commander and Calypso which I start simplify with this library. > > Embarrassingly, I'm not quite clear on what this all means so I'll be eager > to hear the results of the case study with Commander and Calypso! > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Sept. 26, 2017

[Pharo 7.0-dev] Build #155: 20454-JobsTests-package-should-be-renamed-to-Jobs-Tests

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

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

Sept. 26, 2017