April 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Please publish Slice

by Nicolas Cellier

OK Stef, sorry I didn't follow the procedure. This is because the annoying fact that running some of the tests result in dirty packages... Nicolas 2009/4/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > because after this is much more difficult for me to integrate > For example now I have new event mixed with closure fixes.... > This is simple to publish a slice you create it and add the dirty > packages as dependent. > > Stef > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2009

Re: [Pharo-project] Arg assignement [Fwd: how can we sync]

by Nicolas Cellier

Correct, all the fixes are in PharoInbox. You choose to integrate them or not, they are minor. But I expect you can integrate them all in less than 1 hour. Cheers Nicolas 2009/4/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > ok do I understand correctly that I do not have to have a look > at 'closure usage fixes' :) > > Stef > > On Apr 16, 2009, at 11:51 AM, Nicolas Cellier wrote: > >> No, after a full review of 'Closure Usage Fixes.1.cs', I verified >> this file only fix minor case of blocks writing in outside temps, >> not the case of blocks writing their own arguments. >> >> Nicolas >> >> 2009/4/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> Thanks nicolas >>> You are talking about >>> Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=742 >>> >>> Stef >>> >>> On Apr 15, 2009, at 11:10 PM, Nicolas Cellier wrote: >>> >>>> I published very trivials cleanups from Eliots abount Sounds package >>>> in PharoInbox >>>> I will continue reviewing tomorrow. >>>> Bye >>>> >>>> 2009/4/15 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>>>> Oops, I just miss the attachments :( >>>>> >>>>> 2009/4/15 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>>>>> >>>>>> Is there a more recent version? >>>>>> >>>>>> Nicolas >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2009

Re: [Pharo-project] New event Sensor

by StÃ©phane Ducasse

ok so I will focus on nicolas fixes first On Apr 16, 2009, at 12:24 PM, Michael Rueger wrote: > On Thu, Apr 16, 2009 at 12:22 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Mike >> >> is it safe to use System-Support (what will happen to inputSensor). > > The packages in the inbox have not been tested yet, but should be > ready later today or tomorrow. > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2009

[Pharo-project] Please publish Slice

by StÃ©phane Ducasse

because after this is much more difficult for me to integrate For example now I have new event mixed with closure fixes.... This is simple to publish a slice you create it and add the dirty packages as dependent. Stef

April 16, 2009

Re: [Pharo-project] New event Sensor

by Michael Rueger

On Thu, Apr 16, 2009 at 12:22 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Mike > > is it safe to use System-Support (what will happen to inputSensor). The packages in the inbox have not been tested yet, but should be ready later today or tomorrow. Michael

April 16, 2009

[Pharo-project] New event Sensor

by StÃ©phane Ducasse

Mike is it safe to use System-Support (what will happen to inputSensor). Stef

April 16, 2009

Re: [Pharo-project] The System Package

by StÃ©phane Ducasse

Now in http://code.google.com/p/pharo/issues/detail?id=746 Stef On Apr 16, 2009, at 10:16 AM, Lukas Renggli wrote: > I don't have a package registered called 'System', however there are > some other packaging related problems in the latest Pharo. The classes > BlockClosuresTestCase, ClosureTests, CollectionCombinator, and > DecompilerTests are in no package. > > I used the following script, that is part of code critics: > > | packages | > packages := MCWorkingCopy allManagers > collect: [ :each | each packageInfo ]. > SystemNavigation default allClassesAndTraits > do: [ :class | > (packages count: [ :package | package includesSystemCategory: class > category ]) ~= 1 > ifTrue: [ Transcript show: class name; show: ' ('; show: class > category; show: ')'; cr ] > ifFalse: [ [ :mclass | > mclass selectors do: [ :selector | > (packages count: [ :package | package includesMethod: selector > ofClass: mclass ]) ~= 1 > ifTrue: [ Transcript show: mclass name; show: '>>'; show: > selector; cr ] ] ] value: class; value: class class ] ] > displayingProgress: 'Checking Packages'

April 16, 2009

Re: [Pharo-project] New Pharo-dev based on 10277

by Damien Cassou

On Wed, Apr 15, 2009 at 11:27 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > It's nice to not be the only one nagging you for updates of Pharo-web :) Â However, I'm the first to admit that if comes down to running a script or two on top of Pharo-dev, that should do the job. Is it ok if I only once a month? -- Damien Cassou http://damiencassou.seasidehosting.st

April 16, 2009

Re: [Pharo-project] Arg assignement [Fwd: how can we sync]

by StÃ©phane Ducasse

ok do I understand correctly that I do not have to have a look at 'closure usage fixes' :) Stef On Apr 16, 2009, at 11:51 AM, Nicolas Cellier wrote: > No, after a full review of 'Closure Usage Fixes.1.cs', I verified > this file only fix minor case of blocks writing in outside temps, > not the case of blocks writing their own arguments. > > Nicolas > > 2009/4/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Thanks nicolas >> You are talking about >> http://code.google.com/p/pharo/issues/detail?id=742 >> >> Stef >> >> On Apr 15, 2009, at 11:10 PM, Nicolas Cellier wrote: >> >>> I published very trivials cleanups from Eliots abount Sounds package >>> in PharoInbox >>> I will continue reviewing tomorrow. >>> Bye >>> >>> 2009/4/15 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>>> Oops, I just miss the attachments :( >>>> >>>> 2009/4/15 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>>>> >>>>> Is there a more recent version? >>>>> >>>>> Nicolas >>>>> >>>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2009

Re: [Pharo-project] Fonts working great

by StÃ©phane Ducasse

On Apr 16, 2009, at 1:25 AM, Geert wrote: > > > disaser seems a strong word. > > > Nothing bad intended here, I thought the "bit of" would have > softened the "user experience disaster" :) > > I was only referring to the fact that how system (or should they be > called image?) preferences are currently managed is far from > intuitive or user-friendly. The Pharo team's priorities are > understandably elsewhere at the moment and it probably is more an > issue which will be tackled by the Hermion project I assume? > not really Hermion is the project of david and of course everything that we can get from him is cool but I do not expect him to work on preferences. Stef > > > > > > > > -- > View this message in context: http://n2.nabble.com/Fonts-working-great-tp2466458p2641284.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2009