February 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [pharo-project/pharo-core] 3fabea: 40497

by Tudor Girba

It is symmetrical to String>>asClass which proves rather elegant for scripting class lookup. Why is it not good? Doru On Mon, Feb 23, 2015 at 10:59 PM, stepharo <stepharo(a)free.fr> wrote: > > Le 23/2/15 15:53, Sven Van Caekenberghe a Ã©crit : > >> Cool, we're back in business ;-) >> > > yes but why having String>>asPackage is better? > > Stef > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 23, 2015

Re: [Pharo-dev] Athens/Morphic

by stepharo

Le 23/2/15 09:59, Nicolai Hess a Ã©crit : > Load the new configuration of athens (2.9) I could not find it in the ConfigurationBrowser or in the Pharo40 main repo. I thought that it was integrated in Pharo (I used the latest version 40501) > Open an AthensWorld: > AthensWrapWorldMorph new openInWorld > > > Drag and drop some morphs on this athens world. > (Nautilus /Old Workspace should fully work/ GT Inspector and > Playground not) > > > > 2015-02-23 9:51 GMT+01:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > how can I play with that? > > even if I should not. > > Le 20/2/15 08:54, Marcus Denker a Ã©crit : >> Very nice! Works here (on Mac). >> >> I will integrate as soon as the CI is up againâ¦ >> >> Marcus >> >>> On 19 Feb 2015, at 12:44, Nicolai Hess <nicolaihess(a)web.de >>> <mailto:nicolaihess@web.de>> wrote: >>> >>> Most of this (without the test class (AthensTestDisplay)) is now >>> ready for >>> integration. >>> >>> A lot of changes for making Mophic and Text(Morphs) work on Athens >>> (For testing purpose there is also the AthensWrapWorldMorph >>> included). >>> >>> The Canvas wrapper (AthensCanvasWrapper) is not yet included and >>> therefore >>> all Morphs that do not explicit have a proper drawOnAthensCanvas >>> method arent't drawn (or just like rectangles). >>> >>> Should work with any image >= 40490 >>> Just load the latest ConfigurationOfAthens from pharo 40 inbox and >>> load >>> ConfigurationOfAthens loadVersion:'2.9' >>> >>> If this is working (or not:) ) please leave a note on fogbugz: >>> "14954 load new configuration 2.9 (more morphic support)" >>> >>> >>> nicolai >>> >>> >>> 2015-01-31 11:54 GMT+01:00 Alain Plantec >>> <alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com>>: >>> >>> >>>> >>>> Yes the HandMorph is handled like any other Morph, it draws >>>> itself and >>>> after that it draws all its submorphs. (And actually it >>>> does not use any caching, and it is still quite fast) >>> >>> the same in Bloc, no caching and it works just fine :) >>> >>>> But yes, it needs a special drawOnAthens method. >>>> >>>> Do you plane to make a package for it ? >>>> I would like to integrate it in Bloc. >>>> >>>> >>>> What would like to integrate? >>> In fact I do not see any change when in Bloc. >>> So I guess I will have to adapt Bloc to your changes. >>> >>>> I will upload the changes in Athens-Morphic package to >>>> the Athens repository. >>> >>> cool. >>> >>> thanks >>> >>> Alain >>> >>> >> > >

Feb. 23, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 3fabea: 40497

by Sven Van Caekenberghe

> On 23 Feb 2015, at 22:59, stepharo <stepharo(a)free.fr> wrote: > > > Le 23/2/15 15:53, Sven Van Caekenberghe a Ã©crit : >> Cool, we're back in business ;-) > > yes but why having String>>asPackage is better? > > Stef I was commenting on the CI/Integration process, not this particular issue.

Feb. 23, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 3fabea: 40497

by stepharo

Le 23/2/15 15:53, Sven Van Caekenberghe a Ã©crit : > Cool, we're back in business ;-) yes but why having String>>asPackage is better? Stef

Feb. 23, 2015

Re: [Pharo-dev] CI Server still down...

by Tudor Girba

Thanks! Doru On Mon, Feb 23, 2015 at 3:54 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 23 Feb 2015, at 15:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> > >> On 23 Feb 2015, at 15:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> > >> > >>> On 23 Feb 2015, at 15:17, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >>> > >>> So I restarted the slaves, but now the Jenkins is down: > >>> > >>> https://ci.inria.fr/pharo/ > >>> > >>> I already restarted it once, it does not start up again. > >>> > >>> > >> > >> > >> It seems to work now. > >> > > > > and update 497 has been doneâ¦ this means: we are back in business! > > > > Marcus > > Thanks, Marcus ! > > > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 23, 2015

Re: [Pharo-dev] Example implementation of associations with Slots in Pharo 4.0

by Ben Coman

I haven't played with the relation example yet, but will real soon. Just some initial thoughts... I like RelationSlot. To me association seems one-way while a relation is two-way. btw, Is there some reason to not match the syntax of the often cited paper "Flexible Object Layout" ? I see one advantage is that its easier to read all the slot names vertically aligned. Object subclass: #SlotExampleMovie slots: { #name. #year. #director => ToOneRelationSlot opposite: #directedMovies class: #SlotExamplePerson. #actors => ToManyRelationSlot opposite: #actedInMovies class: #SlotExamplePerson. } classVariables: { } category: 'SlotAssociations-Tests-Example' Also maybe an alternative slot class name so that it reads more like a sentence... "#director related to one #directedMovies in class #SlotExamplePerson" Object subclass: #SlotExampleMovie slots: { #name. #year. #director => RelatedToOne inverse: #directedMovies inClass: #SlotExamplePerson. #actors => RelatedToMany inverse: #actedInMovies inClass: #SlotExamplePerson. } classVariables: { } category: 'SlotAssociations-Tests-Example' Or even... Object subclass: #SlotExampleMovie slots: { #name. #year. #director => OneRelatedTo many: #directedMovies inClass: #SlotExamplePerson. #actors => ManyRelatedTo many: #actedInMovies inClass: #SlotExamplePerson. } classVariables: { } category: 'SlotAssociations-Tests-Example' cheers -ben On Tue, Feb 24, 2015 at 2:33 AM, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: > > On Mon, Feb 23, 2015 at 9:59 AM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> >> > On 21 Feb 2015, at 21:11, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: >> > >> > Today I experimented a little with the new Slots feature of Pharo 4.0. >> As an example I implemented support for associations/relationships. >> > >> >> Very nice! Can I add this to Pharo4 as an example? >> >> Sure, cool! > > >> My idea is that at first we add these things as examples, and then later >> take the examples and distill a library of >> generally useful slots. >> >> >> > That sounds like a good approach to get familiar with these kind of new > features. > > Some things I can do to improve the Example > - Add an option to make one side of the association readonly. In most > situations I think it's a good idea to update an association only from one > side to keep things simple. > - Whats a better name AssociationSlot or RelationSlot? I'm not sure > - As StÃ©phane said, isn't there a nicer way to declare the associations? > - Better error handling > > Jan. > > > > > > > > > > > >

Feb. 23, 2015

Re: [Pharo-dev] Example implementation of associations with Slots in Pharo 4.0

by Jan van de Sandt

On Mon, Feb 23, 2015 at 9:59 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 21 Feb 2015, at 21:11, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: > > > > Today I experimented a little with the new Slots feature of Pharo 4.0. > As an example I implemented support for associations/relationships. > > > > Very nice! Can I add this to Pharo4 as an example? > > Sure, cool! > My idea is that at first we add these things as examples, and then later > take the examples and distill a library of > generally useful slots. > > > That sounds like a good approach to get familiar with these kind of new features. Some things I can do to improve the Example - Add an option to make one side of the association readonly. In most situations I think it's a good idea to update an association only from one side to keep things simple. - Whats a better name AssociationSlot or RelationSlot? I'm not sure - As StÃ©phane said, isn't there a nicer way to declare the associations? - Better error handling Jan.

Feb. 23, 2015

[pharo-project/pharo-core]

by GitHub

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

Feb. 23, 2015

[pharo-project/pharo-core] dda98e: 40501

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: dda98ef5205695571f2b39862f54564b25f44cad https://github.com/pharo-project/pharo-core/commit/dda98ef5205695571f2b3986… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-02-23 (Mon, 23 Feb 2015) Changed paths: M Kernel.package/Delay.class/class/class initialization/initialize.st M Kernel.package/Delay.class/class/enable new code/newCodeEnabled.st R Kernel.package/Delay.class/class/enable new code/newCodeEnabled_.st R Kernel.package/Delay.class/class/snapshotting/restoreResumptionTimes.st R Kernel.package/Delay.class/class/snapshotting/saveResumptionTimes.st M Kernel.package/Delay.class/class/snapshotting/shutDown.st M Kernel.package/Delay.class/class/snapshotting/startUp.st M Kernel.package/Delay.class/class/testing/anyActive.st M Kernel.package/Delay.class/class/testing/nextWakeUpTime.st R Kernel.package/Delay.class/class/timer process/handleTimerEvent.st R Kernel.package/Delay.class/class/timer process/runTimerEventLoop.st R Kernel.package/Delay.class/class/timer process/scheduleDelay_.st M Kernel.package/Delay.class/class/timer process/schedulingProcess.st M Kernel.package/Delay.class/class/timer process/startTimerEventLoop.st M Kernel.package/Delay.class/class/timer process/stopTimerEventLoop.st R Kernel.package/Delay.class/class/timer process/unscheduleDelay_.st M Kernel.package/Delay.class/instance/enable new code/newCodeEnabled.st M Kernel.package/Delay.class/instance/private/schedule.st M Kernel.package/Delay.class/instance/private/unschedule.st R Kernel.package/DelayWaitTimeout.class/instance/signaling/signalWaitingProcess.st R Kernel.package/MonitorDelay.class/instance/private/signalWaitingProcess.st M KernelTests.package/extension/Delay/class/testCaseSupportTimingSemaphore.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script501.st M ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40387.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40501.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40501 14942 Delay refactoring (part 2b) - clean out newCodeEnabled wrappers https://pharo.fogbugz.com/f/cases/14942 http://files.pharo.org/image/40/40501.zip

Feb. 23, 2015

[pharo-project/pharo-core]

by GitHub

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

Feb. 23, 2015