December 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] 19430 promoting DelaySpinScheduler from experimental

by Marcus Denker

I have cleaned up and re-done 60327. It is in the build queue. Marcus > On 15 Dec 2016, at 12:40, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Yes, the update failed strangely (not related to anything inside). After the MacOS update, > ssh asked for credentials, and that lead to a update failing, which made update I did not work. > > Will be fixed. > > >> On 15 Dec 2016, at 12:35, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: >> >> >> Case 19430 was closed "Integrated In 60326" >> but that build doesn't include the code. >> The build 60326 log message doesn't reference slice 19430 >> http://forum.world.st/pharo-project-pharo-core-1a2e47-60326-td4927011.html <http://forum.world.st/pharo-project-pharo-core-1a2e47-60326-td4927011.html> >> >> cheers -ben >> >> >> On Tue, Dec 13, 2016 at 10:07 PM, Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: >> tx ben for the explanation because I was a bit worry to change something that late in our process :) >> >> On Tue, Dec 13, 2016 at 2:12 PM, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: >> A long time ago the current delay scheduler had been operating long enough to no longer consider it experimental. I've finally got around to renaming the class here.... >> https://pharo.fogbugz.com/f/cases/19430/Promote-DelaySpinScheduler-from-exp… <https://pharo.fogbugz.com/f/cases/19430/Promote-DelaySpinScheduler-from-exp…> >> >> But trying to do... >> Delay delaySchedulerClass: DelaySpinScheduler >> in the post-load is a problem for the CI monkey. >> >> That post-load might work fine with the integrator. Or otherwise can someone manually execute it in the image after the slice is integrated. >> >> cheers -ben >> >> >

Dec. 15, 2016

Re: [Pharo-dev] [ANN] Pharo Association has a new Website!

by Marcus Denker

> > > Sadly I had to remove everything as BitPay is not compatible with the legal > structure of the association right now (dealing with US based companies wrt. > money is getting very hard these days). > > So for us, using bitpay is sadly no option at this point. > I will explore http://coinwidget.com <http://coinwidget.com/> the next weeks, this seems to be much more what we need actually. Marcus

Dec. 15, 2016

Re: [Pharo-dev] [ANN] Pharo Association has a new Website!

by Marcus Denker

> On 12 Dec 2016, at 17:42, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 8 Dec 2016, at 15:59, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> >>> >>>> Accepting Bitcoin payments would be a plus ;-) (https://bitpay.com/tour <https://bitpay.com/tour>) >>>> >>> >> >> Hi, >> >> I have setup bitpay. This means we can now accept bitcoin, to pay by bitcoin, >> for now please select âofflineâ payment and then send a mail to >> association(a)pharo.org <mailto:association@pharo.org> >> >> and we will generate a bitcoin invoice. (we can integrate it a bit better later). >> > > Hello, > > I now > - added a link to donate by bitpay to https://association.pharo.org/Donate <https://association.pharo.org/Donate> > - added payments links to the invoice that the system generates > for paying the membership. Hi, Sadly I had to remove everything as BitPay is not compatible with the legal structure of the association right now (dealing with US based companies wrt. money is getting very hard these days). So for us, using bitpay is sadly no option at this point. Marcus

Dec. 15, 2016

Re: [Pharo-dev] 19430 promoting DelaySpinScheduler from experimental

by Marcus Denker

Yes, the update failed strangely (not related to anything inside). After the MacOS update, ssh asked for credentials, and that lead to a update failing, which made update I did not work. Will be fixed. > On 15 Dec 2016, at 12:35, Ben Coman <btc(a)openinworld.com> wrote: > > > Case 19430 was closed "Integrated In 60326" > but that build doesn't include the code. > The build 60326 log message doesn't reference slice 19430 > http://forum.world.st/pharo-project-pharo-core-1a2e47-60326-td4927011.html <http://forum.world.st/pharo-project-pharo-core-1a2e47-60326-td4927011.html> > > cheers -ben > > > On Tue, Dec 13, 2016 at 10:07 PM, Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: > tx ben for the explanation because I was a bit worry to change something that late in our process :) > > On Tue, Dec 13, 2016 at 2:12 PM, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: > A long time ago the current delay scheduler had been operating long enough to no longer consider it experimental. I've finally got around to renaming the class here.... > https://pharo.fogbugz.com/f/cases/19430/Promote-DelaySpinScheduler-from-exp… <https://pharo.fogbugz.com/f/cases/19430/Promote-DelaySpinScheduler-from-exp…> > > But trying to do... > Delay delaySchedulerClass: DelaySpinScheduler > in the post-load is a problem for the CI monkey. > > That post-load might work fine with the integrator. Or otherwise can someone manually execute it in the image after the slice is integrated. > > cheers -ben > >

Dec. 15, 2016

Re: [Pharo-dev] 19430 promoting DelaySpinScheduler from experimental

by Ben Coman

Case 19430 was closed "Integrated In 60326" but that build doesn't include the code. The build 60326 log message doesn't reference slice 19430 http://forum.world.st/pharo-project-pharo-core-1a2e47-60326-td4927011.html cheers -ben On Tue, Dec 13, 2016 at 10:07 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > tx ben for the explanation because I was a bit worry to change something > that late in our process :) > > On Tue, Dec 13, 2016 at 2:12 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> A long time ago the current delay scheduler had been operating long >> enough to no longer consider it experimental. I've finally got around to >> renaming the class here.... >> https://pharo.fogbugz.com/f/cases/19430/Promote-DelaySpinSch >> eduler-from-experimental-status-part-1 >> >> But trying to do... >> Delay delaySchedulerClass: DelaySpinScheduler >> in the post-load is a problem for the CI monkey. >> >> That post-load might work fine with the integrator. Or otherwise can >> someone manually execute it in the image after the slice is integrated. >> >> cheers -ben >> > >

Dec. 15, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60326 Home: https://github.com/pharo-project/pharo-core

Dec. 15, 2016

[pharo-project/pharo-core] 1a2e47: 60326

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 1a2e4746b15cea131fc7294ec93ed971f34d8411 https://github.com/pharo-project/pharo-core/commit/1a2e4746b15cea131fc7294e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-15 (Thu, 15 Dec 2016) Changed paths: A Kernel.package/CompiledMethod.class/instance/accessing-tags/tagWith_.st A Kernel.package/CompiledMethod.class/instance/accessing-tags/tags.st A Kernel.package/CompiledMethod.class/instance/accessing-tags/untagFrom_.st A Kernel.package/CompiledMethod.class/instance/testing/isTaggedWith_.st A RPackage-Core.package/RPackage.class/instance/simple symbol tags/classesTaggedWith_.st A RPackage-Core.package/RPackage.class/instance/simple symbol tags/tagsForClasses.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60325.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60326.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60325.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60326.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Traits.package/TClassDescription.class/instance/accessing tags/addMethodTag_.st A Traits.package/TClassDescription.class/instance/accessing tags/methodsTaggedWith_.st A Traits.package/TClassDescription.class/instance/accessing tags/removeMethodTag_.st A Traits.package/TClassDescription.class/instance/accessing tags/tagWith_.st A Traits.package/TClassDescription.class/instance/accessing tags/tags.st A Traits.package/TClassDescription.class/instance/accessing tags/tagsForMethods.st A Traits.package/TClassDescription.class/instance/accessing tags/untagFrom_.st A Traits.package/TClassDescription.class/instance/testing/isLocalMethodsProtocol_.st A Traits.package/TClassDescription.class/instance/testing/isTaggedWith_.st Log Message: ----------- 60326 19341 New class and method tags API https://pharo.fogbugz.com/f/cases/19341 http://files.pharo.org/image/60/60326.zip

Dec. 15, 2016

Re: [Pharo-dev] [Pharo-users] A little prototype kernel in 9 methods :)

by stepharong

> Nice! > > Is there any good reason why during cloning you do not set the > delegation too? Because I wanted to be able to have two low level operations that you can compose or not. > > -- Pavel > > 2016-12-11 21:13 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> I sent the wrong file of course. Here is the chapter :) >> >> >> On Sun, Dec 11, 2016 at 8:52 PM, <serge.stinckwich(a)gmail.com> wrote: >>> Great works ! I will add some contents for Actalk chapter. >>> >>> BTW I update a little bit the PolyMath book. There was some sections >>> missing. >>> >>> >>> EnvoyÃ© de mon iPhone >>> >>>> Le 11 dÃ©c. 2016 Ã 20:33, stepharong <stepharong(a)free.fr> a Ã©crit : >>>> >>>> Hi guys >>>> >>>> I'm thinking to package some of my language design knowledge in a >>>> kind of book. Probably to be used to give a lecture on >>>> OOP languages. I have class-based reflective kernel. This is several >>>> years that I was thinking about prototype kernels >>>> and I decided to relax and implement one for fun over the week-end. >>>> I will probably look at mixins, traits, talents, split objects in the >>>> future. >>>> >>>> Since I cannot compile the book on jenkins, I join the pdf. >>>> >>>> Stef >>>> >>>> PS: I will finish Pharo by example now and focus on Learning OOP with >>>> Pharo. >>>> >>>> -- >>>> Using Opera's mail client: http://www.opera.com/mail/ >>>> <book.pdf> >>> >> > -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 14, 2016

Re: [Pharo-dev] inconsistent FileLocator behavior

by Andrei Chis

Hi Henry, On Wed, Dec 14, 2016 at 4:20 PM, Henrik Johansen < henrik.s.johansen(a)veloxit.no> wrote: > > > On 14 Dec 2016, at 10:13 , Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > > Because now I always end up doing FileLocator home asFileReference, > which feels superfluous. > > > > What is the use case that you don't want to resolve it yet? > > To illustrate the benefit of keeping things as FileLocator instances > rather than resolved paths until needed, you could try: > 1) Open a playground. > 2) Save image. > 3) Quit, open image on different platform. > > In Pharo 5, your image will simply error on trying to open new > Playgrounds, on Pharo6 you lose any custom locations selected in the > settings for storing cache/stash. > The amount of workaround code dealing with cache/stashDirectories being > FileReferences instead of FileLocators is an interesting read - not to > mention implemented in 2 different ways for cacheDirectory/stashDirectory; > one never lets you keep a custom value (resetting to nil at startup), and > the other discards any custom path when transitioning platforms. (is it not > nil? does it exist? If not, reset to default) > This is an interesting observation. I'd love to simplify the code in that part. Can you open a bug report with this info so it's not lost. Cheers, Andrei > > TL;DR: The use-case for FileLocators is persistently stored relative paths > that need to work cross-platform. > > Cheers, > Henry >

Dec. 14, 2016

Re: [Pharo-dev] inconsistent FileLocator behavior

by Henrik Johansen

> On 14 Dec 2016, at 10:13 , Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > Because now I always end up doing FileLocator home asFileReference, which feels superfluous. > > What is the use case that you don't want to resolve it yet? To illustrate the benefit of keeping things as FileLocator instances rather than resolved paths until needed, you could try: 1) Open a playground. 2) Save image. 3) Quit, open image on different platform. In Pharo 5, your image will simply error on trying to open new Playgrounds, on Pharo6 you lose any custom locations selected in the settings for storing cache/stash. The amount of workaround code dealing with cache/stashDirectories being FileReferences instead of FileLocators is an interesting read - not to mention implemented in 2 different ways for cacheDirectory/stashDirectory; one never lets you keep a custom value (resetting to nil at startup), and the other discards any custom path when transitioning platforms. (is it not nil? does it exist? If not, reset to default) TL;DR: The use-case for FileLocators is persistently stored relative paths that need to work cross-platform. Cheers, Henry

Dec. 14, 2016