- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PharoLauncher feedback

by Stephane Ducasse

Tx I loved the launcher! On Fri, Sep 29, 2017 at 3:50 PM, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > Hi StÃ©phane, > >> Le 22 sept. 2017 Ã 20:34, Stephane Ducasse <stepharo.self(a)gmail.com> a Ã©crit : >> >> Hi christophe >> >> I took the bleeding edge and here are my report. >> >> - We need a signed VM because the security on mac is getting in our way. > > Right. It is not directly related to the launcher. Pharo binaries need to be signed. > OS packaging scripts are shared (launcher, std pharo distribution). > >> - I got PrimitiveFailed: CreatedDirectory in MacStore failed. >> So I do not know what to do :( >> >> I do not get why I cannot write on my download folder ;( but this >> error should be caught. >> >> - Pharo.app should be renamed PharoLauncher >> - the Quit menu is showing SqueakOSXApp and the about too. > > This two points are not easy because they are related to how the VM is built. > I tried to use Alien and OS X integration to change menus at runtime but it takes time as I do not know a lot on OS X api. > We should put that on the TODO list. > >> - There is a template 7.0 (beta) but it does not exist below Pharo60 >> We should not have Pharo 60 but Pharo 6.1 > > fixed > >> else it seems to work. >> >> well no :) >> I downloaded Pharo70 alpha and I got a problem with FT2Error primitive failed. >> May be this is normal. I do not know. > > Not sure you tested the latest version. > I did a lot of improvements (especially for Linux) on the launcher to ensure the environment you get when forking from the launcher process is clean (setting the working dir and clean env variable set by the VM used by the launcher). > It should be fine now. > >

Sept. 29, 2017

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

by Stephane Ducasse

tx! On Fri, Sep 29, 2017 at 9:58 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2017-09-28 21:12 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >> I would not use meta because you would not write annotationAnnotations :) >> and annotations is meta by its name. >> >> classAnnotation is much better than metaAnnotation >> > > Done. > > >> >> Stef >> >> >> On Thu, Sep 28, 2017 at 5:40 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> >>> So I renamed it to ClassAnnotation with all related names. >>> >>> But I keep meta prefix in #metaAnnotations Class extension to avoid >>> general name: >>> >>> MyClass metaAnnotations >>> >>> You can check updated readme for details https://github.com/dio >>> nisiydk/ClassAnnotation >>> >>> 2017-09-26 17:31 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>> >>>> ;) >>>> >>>> On Tue, Sep 26, 2017 at 1:28 PM, Ben Coman <btc(a)openinworld.com> wrote: >>>> >>>>> 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. 29, 2017

New Pharo booklet: Scraping HTML with XPath

by Stephane Ducasse

Hi we wanted to let you that a new booklet is available on http://books.pharo.org Stef and Peter

Sept. 29, 2017

Re: [Pharo-dev] Two GitHub organizations

by Peter UhnÃ¡k

http://forum.world.st/IMPORTANT-iceberg-home-changed-tp4944480p4944684.html On Fri, Sep 29, 2017 at 3:54 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > What is the difference between pharo-project and pharo-vcs? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Sept. 29, 2017

Re: [Pharo-dev] CI does not finish (PR 309)

by Martin Dias

On Fri, Sep 29, 2017 at 5:52 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > I think the reason is that the last image opens an epicea window > to recover codeâ¦ which it should not. > The setting to do that is disabled by default (at least I did that before 6.0 release). BTW, ~Sunday night I fixed test errors of epicea in p7. The reason was that Class, Trait and metas do not use the TClass trait. It's in #development but still not in #stable. I still have to read the mailing list how to integrate a new epicea version in P7 (I guess a PR). > > > On 29 Sep 2017, at 10:38, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > For whatever reason the CI jobs for PR's to Pharo 7 runs endless and > never finishes. > > It run well a few days ago ... > > > > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% > 20pull%20request%20and%20branch%20Pipeline/job/PR-309/ > > > > Any ideas? > > > > > > >

Sept. 29, 2017

Re: [Pharo-dev] Iceberg Contribution Barrier

by Esteban Lorenzano

Iâm sorry, I didnât understand. You want to contribute to iceberg? Then yes, in Pharo 6.1 you need to follow the update instructions. Now, Pharo 7 is a bit more complicated because of things :) This is the âupdatedâ iceberg update processâ¦ it just removes adapters from monticello: MCRepositoryGroup default repositories select: [ :each | each isKindOf: IceMetacelloRepositoryAdapter ]) do: [ :each | MCRepositoryGroup default removeRepository: each ]. #('Iceberg-UI' 'Iceberg-Plugin-GitHub' 'Iceberg-Plugin' 'Iceberg-Metacello-Integration' 'Iceberg-Libgit' 'Iceberg' 'BaselineOfIceberg' 'LibGit-Core' 'BaselineOfLibGit') do: [ :each | each asPackage removeFromSystem ]. Metacello new baseline: 'Iceberg'; repository: 'github://pharo-vcs/iceberg'; load. (Iâm working to remove this problem, Iâm sorryâ¦ iceberg 0.6 will fix a lot of this problems) and Iâm very sorry for the confusion :) Esteban > On 29 Sep 2017, at 15:25, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > EstebanLM wrote >> you do not need to update Iceberg >> ... >> please, take the instructions from Guilleâs place as your guide: > > Just so I'm clear, do you mean to adapt Guille's instructions to the Iceberg > repo? IIUC Steph's recent post, patches to outside projects like Bloc and > Iceberg must be pushed to their respective canonical repos, no? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Sept. 29, 2017

Re: [Pharo-dev] Should we always put application file paths into FileLocator?

by Sean P. DeNigris

Denis Kudriashov wrote > What do you think? It makes sense to me to have a single uniform access point for system files. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 29, 2017

Re: [Pharo-dev] Non-deterministic ombu errors

by Martin Dias

Now I do not know the best way for you to get the new fixed version. It's too late to include it in P6.1, I guess, so... either add epicea into metacello configuration or wait until P7. On Fri, Sep 29, 2017 at 5:34 AM, Jan BlizniÄenko <bliznjan(a)fit.cvut.cz> wrote: > I'm glad it has known reason then, thank you for looking into it, all I was > able to find out was that it relates to non-ascii characters and that build > on our production server fails because of that :) > > Jan > > > tinchodias wrote > > On Sun, Sep 24, 2017 at 5:49 AM, Sven Van Caekenberghe < > > > sven@ > > > > wrote: > > > >> > >> > On 23 Sep 2017, at 22:42, Jan BlizniÄenko < > > > bliznjan@.cvut > > > > wrote: > >> > > >> > Hello > >> > > >> > I am having very similar errors from time to time when manually > loading > >> code > >> > into Pharo from filetree (gitfiletree), but only in one of my projects > >> which > >> > contains non-ASCII characters like ÄÅ¡ÄÅÅ¾Ã½Ã¡ÃÃ©Å¯ÃºÅ¥Ä. For the very same > >> reason > >> > (not able to find why sometimes the error is there and sometimes is > >> not), I > >> > did not report it yet, but it is quite annoying. Retrying loading the > >> > package helps every time. > >> > >> I think was reported before. I believe Ombu somewhere takes an arbitrary > >> chunk of bytes out of an UTF-8 encoded file (like the last 100 of > >> something > >> like that) and then starts reading that. With UTF-8, a variable length > >> encoding, that can be dangerous because you could end up in the middle > of > >> a > >> character, not between encoded character boundaries. This would also > >> explain the randomness, as it is highly dependent on the contents. > >> > >> ZnUTF8Encoder>>#backOnStream: can be used to make sure you are really at > >> the start of an encoded character. > >> > > > > > > Hello > > > > This issue was reported as: > > > > https://pharo.fogbugz.com/f/cases/20112/Epicea-can-fail- > while-reading-non-ascii-blocks > > > > My apologies for the bug... I introduced that code as an i/o optimization > > but wasn't properly tested. > > > > Thnks Sven, but I finally used stream's #basicNext (as Henrik suggested > in > > fogbugz) which skips forward. > > > > > > Martin > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Sept. 29, 2017

Two GitHub organizations

by Sean P. DeNigris

What is the difference between pharo-project and pharo-vcs? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 29, 2017

Re: [Pharo-dev] PharoLauncher feedback

by Christophe Demarey

Hi StÃ©phane, > Le 22 sept. 2017 Ã 20:34, Stephane Ducasse <stepharo.self(a)gmail.com> a Ã©crit : > > Hi christophe > > I took the bleeding edge and here are my report. > > - We need a signed VM because the security on mac is getting in our way. Right. It is not directly related to the launcher. Pharo binaries need to be signed. OS packaging scripts are shared (launcher, std pharo distribution). > - I got PrimitiveFailed: CreatedDirectory in MacStore failed. > So I do not know what to do :( > > I do not get why I cannot write on my download folder ;( but this > error should be caught. > > - Pharo.app should be renamed PharoLauncher > - the Quit menu is showing SqueakOSXApp and the about too. This two points are not easy because they are related to how the VM is built. I tried to use Alien and OS X integration to change menus at runtime but it takes time as I do not know a lot on OS X api. We should put that on the TODO list. > - There is a template 7.0 (beta) but it does not exist below Pharo60 > We should not have Pharo 60 but Pharo 6.1 fixed > else it seems to work. > > well no :) > I downloaded Pharo70 alpha and I got a problem with FT2Error primitive failed. > May be this is normal. I do not know. Not sure you tested the latest version. I did a lot of improvements (especially for Linux) on the launcher to ensure the environment you get when forking from the launcher process is clean (setting the working dir and clean env variable set by the VM used by the launcher). It should be fine now.

Sept. 29, 2017