- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

by philippe.back＠highoctane.be

Great. Le 14 nov. 2016 11:23, "Esteban Lorenzano" <estebanlm(a)gmail.com> a Ã©crit : > > On 14 Nov 2016, at 10:00, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Revert the new API. It was mistake to integrate it in the code freeze > phase. > > > yep, thatâs accurate :) > > Esteban > > > -- Pavel > > 2016-11-14 9:53 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> >> >> 2016-11-14 9:42 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >> >>> Well, we will revert the change >>> >>> >> revert the autodeprecation or the new api ? >> I made a fix for case 19336 Finder and FileList can now work with the new >> api. >> >> >>> -- Pavel >>> >>> 2016-11-13 17:33 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>> >>>> >>>> >>>> 2016-11-13 10:06 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>>> >>>>> >>>>> >>>>> 2016-11-11 10:55 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >>>>> >>>>>> Hi, >>>>>> >>>>>> the API of Pragma was changed in quite dangerous way. >>>>>> In past we had: >>>>>> - #selector to access to method selector >>>>>> - #keyword to access to pragma selector >>>>>> >>>>>> now we have: >>>>>> - #methodSelector to access to method selector >>>>>> - #selector to access to pragma selector >>>>>> >>>>>> That means that the meaning of the message #selector was changed and >>>>>> it can cause some problems (like some currently failing tests [1]). The >>>>>> #selector message was deprecated in the middle of the transition process so >>>>>> most of usages should be already rewritten to #methodSelector but we >>>>>> need to be aware of it. >>>>>> >>>>>> [1] https://pharo.fogbugz.com/f/cases/19333/17-more-tests-fa >>>>>> iling-due-to-MockSettings-class-Object-doesNotUnderstand-moc >>>>>> ksystemsettings-SettingTreeBuilder-mocksystemse >>>>>> >>>>> >>>>> And it broke finder. >>>>> 19336 >>>>> <https://pharo.fogbugz.com/f/cases/19336/Finder-broken-Can-not-search-for-pr…> >>>>> Finder broken: Can not search for pragmas >>>>> >>>> >>>> And FileList can not show .cs files anymore. >>>> I think both has something to do with a lock (?) during the transform >>>> of the autodeprecation. >>>> >>>> >>>>> >>>>> >>>>>> >>>>>> Cheers >>>>>> -- Pavel >>>>>> >>>>> >>>>> >>>> >>> >> > >

Nov. 14, 2016

Re: [Pharo-dev] macOS Sierra support

by Dimitris Chloupis

This is weird but I have never experienced this "sandbox" thing I have Sierra, updated to the latest and when I download this zip to my downloads folder, I uncompress it and double click the application without moving to the application folder it works without doing anything additionally or complaining about it. I am almost always do this with applications I download because I like to test them before copying them to the application folder. Never had any issues. So apparently my Sierra loves me :D On Mon, Nov 14, 2016 at 12:31 PM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > On 14 Nov 2016, at 11:01, MartinW <wm(a)fastmail.fm> wrote: > > > > Can someone put a note to the website (http://pharo.org/download)? It is > > frustrating for users to follow the link to > > http://files.pharo.org/platform/Pharo5.0-mac.zip from there and get a > > defunct Pharo installation. > > no, in fact that link should work. > â¦ and in fact, it worksâ¦ is just that due the changes in sierra, the > bundle needs to be put in /Applications to not be copied into a sandbox, > readonly place. > > Iâm working on have this working in a different way: is time to make > PharoLauncher the default download. That way it will be in /Applications > naturally and your images will be in a correct place naturally (I also > would like a âadd command line toolsâ option to install a pharo and > pharo-ui in /usr/local/bin). > > Esteban > > > > > > > Sean P. DeNigris wrote > >> > >> EstebanLM wrote > >>> the regular download by zeroconf should give you an usable VM. > >> That worked - thanks! > > > > Yes, this VM works well :) > > > > > > > > -- > > View this message in context: > http://forum.world.st/macOS-Sierra-support-tp4917181p4922891.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > >

Nov. 14, 2016

Re: [Pharo-dev] macOS Sierra support

by Esteban Lorenzano

for the moment, I added this nice (?) alert when you press mac download button: > On 14 Nov 2016, at 11:30, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 14 Nov 2016, at 11:01, MartinW <wm(a)fastmail.fm> wrote: >> >> Can someone put a note to the website (http://pharo.org/download)? It is >> frustrating for users to follow the link to >> http://files.pharo.org/platform/Pharo5.0-mac.zip from there and get a >> defunct Pharo installation. > > no, in fact that link should work. > â¦ and in fact, it worksâ¦ is just that due the changes in sierra, the bundle needs to be put in /Applications to not be copied into a sandbox, readonly place. > > Iâm working on have this working in a different way: is time to make PharoLauncher the default download. That way it will be in /Applications naturally and your images will be in a correct place naturally (I also would like a âadd command line toolsâ option to install a pharo and pharo-ui in /usr/local/bin). > > Esteban > >> >> >> Sean P. DeNigris wrote >>> >>> EstebanLM wrote >>>> the regular download by zeroconf should give you an usable VM. >>> That worked - thanks! >> >> Yes, this VM works well :) >> >> >> >> -- >> View this message in context: http://forum.world.st/macOS-Sierra-support-tp4917181p4922891.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >

Nov. 14, 2016

Re: [Pharo-dev] macOS Sierra support

by Esteban Lorenzano

> On 14 Nov 2016, at 11:01, MartinW <wm(a)fastmail.fm> wrote: > > Can someone put a note to the website (http://pharo.org/download)? It is > frustrating for users to follow the link to > http://files.pharo.org/platform/Pharo5.0-mac.zip from there and get a > defunct Pharo installation. no, in fact that link should work. â¦ and in fact, it worksâ¦ is just that due the changes in sierra, the bundle needs to be put in /Applications to not be copied into a sandbox, readonly place. Iâm working on have this working in a different way: is time to make PharoLauncher the default download. That way it will be in /Applications naturally and your images will be in a correct place naturally (I also would like a âadd command line toolsâ option to install a pharo and pharo-ui in /usr/local/bin). Esteban > > > Sean P. DeNigris wrote >> >> EstebanLM wrote >>> the regular download by zeroconf should give you an usable VM. >> That worked - thanks! > > Yes, this VM works well :) > > > > -- > View this message in context: http://forum.world.st/macOS-Sierra-support-tp4917181p4922891.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Nov. 14, 2016

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

by Esteban Lorenzano

> On 14 Nov 2016, at 10:00, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Revert the new API. It was mistake to integrate it in the code freeze phase. yep, thatâs accurate :) Esteban > > -- Pavel > > 2016-11-14 9:53 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: > > > 2016-11-14 9:42 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>>: > Well, we will revert the change > > > revert the autodeprecation or the new api ? > I made a fix for case 19336 Finder and FileList can now work with the new api. > > -- Pavel > > 2016-11-13 17:33 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: > > > 2016-11-13 10:06 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: > > > 2016-11-11 10:55 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>>: > Hi, > > the API of Pragma was changed in quite dangerous way. > In past we had: > - #selector to access to method selector > - #keyword to access to pragma selector > > now we have: > - #methodSelector to access to method selector > - #selector to access to pragma selector > > That means that the meaning of the message #selector was changed and it can cause some problems (like some currently failing tests [1]). The #selector message was deprecated in the middle of the transition process so most of usages should be already rewritten to #methodSelector but we need to be aware of it. > > [1] https://pharo.fogbugz.com/f/cases/19333/17-more-tests-failing-due-to-MockSe… > > And it broke finder. > 19336 <https://pharo.fogbugz.com/f/cases/19336/Finder-broken-Can-not-search-for-pr…> Finder broken: Can not search for pragmas > > And FileList can not show .cs files anymore. > I think both has something to do with a lock (?) during the transform of the autodeprecation. > > > > Cheers > -- Pavel > > > > >

Nov. 14, 2016

Re: [Pharo-dev] macOS Sierra support

by MartinW

Can someone put a note to the website (http://pharo.org/download)? It is frustrating for users to follow the link to http://files.pharo.org/platform/Pharo5.0-mac.zip from there and get a defunct Pharo installation. Sean P. DeNigris wrote > > EstebanLM wrote >> the regular download by zeroconf should give you an usable VM. > That worked - thanks! Yes, this VM works well :) -- View this message in context: http://forum.world.st/macOS-Sierra-support-tp4917181p4922891.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 14, 2016

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

by Pavel Krivanek

Revert the new API. It was mistake to integrate it in the code freeze phase. -- Pavel 2016-11-14 9:53 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2016-11-14 9:42 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > >> Well, we will revert the change >> >> > revert the autodeprecation or the new api ? > I made a fix for case 19336 Finder and FileList can now work with the new > api. > > >> -- Pavel >> >> 2016-11-13 17:33 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >> >>> >>> >>> 2016-11-13 10:06 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>> >>>> >>>> >>>> 2016-11-11 10:55 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >>>> >>>>> Hi, >>>>> >>>>> the API of Pragma was changed in quite dangerous way. >>>>> In past we had: >>>>> - #selector to access to method selector >>>>> - #keyword to access to pragma selector >>>>> >>>>> now we have: >>>>> - #methodSelector to access to method selector >>>>> - #selector to access to pragma selector >>>>> >>>>> That means that the meaning of the message #selector was changed and >>>>> it can cause some problems (like some currently failing tests [1]). The >>>>> #selector message was deprecated in the middle of the transition process so >>>>> most of usages should be already rewritten to #methodSelector but we >>>>> need to be aware of it. >>>>> >>>>> [1] https://pharo.fogbugz.com/f/cases/19333/17-more-tests-fa >>>>> iling-due-to-MockSettings-class-Object-doesNotUnderstand-moc >>>>> ksystemsettings-SettingTreeBuilder-mocksystemse >>>>> >>>> >>>> And it broke finder. >>>> 19336 >>>> <https://pharo.fogbugz.com/f/cases/19336/Finder-broken-Can-not-search-for-pr…> >>>> Finder broken: Can not search for pragmas >>>> >>> >>> And FileList can not show .cs files anymore. >>> I think both has something to do with a lock (?) during the transform of >>> the autodeprecation. >>> >>> >>>> >>>> >>>>> >>>>> Cheers >>>>> -- Pavel >>>>> >>>> >>>> >>> >> >

Nov. 14, 2016

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

by Nicolai Hess

2016-11-14 9:42 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > Well, we will revert the change > > revert the autodeprecation or the new api ? I made a fix for case 19336 Finder and FileList can now work with the new api. > -- Pavel > > 2016-11-13 17:33 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> >> >> 2016-11-13 10:06 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >> >>> >>> >>> 2016-11-11 10:55 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >>> >>>> Hi, >>>> >>>> the API of Pragma was changed in quite dangerous way. >>>> In past we had: >>>> - #selector to access to method selector >>>> - #keyword to access to pragma selector >>>> >>>> now we have: >>>> - #methodSelector to access to method selector >>>> - #selector to access to pragma selector >>>> >>>> That means that the meaning of the message #selector was changed and it >>>> can cause some problems (like some currently failing tests [1]). The >>>> #selector message was deprecated in the middle of the transition process so >>>> most of usages should be already rewritten to #methodSelector but we >>>> need to be aware of it. >>>> >>>> [1] https://pharo.fogbugz.com/f/cases/19333/17-more-tests-fa >>>> iling-due-to-MockSettings-class-Object-doesNotUnderstand-moc >>>> ksystemsettings-SettingTreeBuilder-mocksystemse >>>> >>> >>> And it broke finder. >>> 19336 >>> <https://pharo.fogbugz.com/f/cases/19336/Finder-broken-Can-not-search-for-pr…> >>> Finder broken: Can not search for pragmas >>> >> >> And FileList can not show .cs files anymore. >> I think both has something to do with a lock (?) during the transform of >> the autodeprecation. >> >> >>> >>> >>>> >>>> Cheers >>>> -- Pavel >>>> >>> >>> >> >

Nov. 14, 2016

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

by Pavel Krivanek

Well, we will revert the change -- Pavel 2016-11-13 17:33 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2016-11-13 10:06 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> >> >> 2016-11-11 10:55 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >> >>> Hi, >>> >>> the API of Pragma was changed in quite dangerous way. >>> In past we had: >>> - #selector to access to method selector >>> - #keyword to access to pragma selector >>> >>> now we have: >>> - #methodSelector to access to method selector >>> - #selector to access to pragma selector >>> >>> That means that the meaning of the message #selector was changed and it >>> can cause some problems (like some currently failing tests [1]). The >>> #selector message was deprecated in the middle of the transition process so >>> most of usages should be already rewritten to #methodSelector but we >>> need to be aware of it. >>> >>> [1] https://pharo.fogbugz.com/f/cases/19333/17-more-tests-fa >>> iling-due-to-MockSettings-class-Object-doesNotUnderstand-moc >>> ksystemsettings-SettingTreeBuilder-mocksystemse >>> >> >> And it broke finder. >> 19336 >> <https://pharo.fogbugz.com/f/cases/19336/Finder-broken-Can-not-search-for-pr…> >> Finder broken: Can not search for pragmas >> > > And FileList can not show .cs files anymore. > I think both has something to do with a lock (?) during the transform of > the autodeprecation. > > >> >> >>> >>> Cheers >>> -- Pavel >>> >> >> >

Nov. 14, 2016

Re: [Pharo-dev] baseline DNU in Pharo6?

by Cyril Ferlicot D.

On 14/11/2016 08:07, phil(a)highoctane.be wrote: > There is a DNU in the build for some reason. > > https://travis-ci.org/DuneSt/MaterialDesignLite/jobs/175623371 > > Works fine in 5.0 > > Clues? > > Phil > Hi! This is caused by the pragma API changes without deprecation. MDL uses the Cypress support from Metacello and thus load the latest Metacello if needed. But the latest Metacello does not have the changes for the pragma. It's for this kind of reason it would be cool to revert those changes and to go by a deprecation phase. -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Nov. 14, 2016