March 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] squeaksource is down....

by StÃ©phane Ducasse

so this is strange they was a Squeak source is down message send an email to squeak mailing-list message ;") On Mar 14, 2010, at 6:48 PM, Lukas Renggli wrote: >> apparently 3 min after showing me the squeaksource is donw it was up again. >> May be the watch dog (if any) was working well :) > > There is no watch dog other than the one that sends out mails if the > web address is not reachable. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 14, 2010

[Pharo-project] Set with nil is fixed and waiting for a nice reviewer

by StÃ©phane Ducasse

during the sprint niko schwarz and oscar nierstrasz fixed the Set in nil entry. Thanks. http://code.google.com/p/pharo/issues/detail?id=1907 Now does somebody with knowledge could have a look because this is a sensitive part of the system and more eyes does not hurt. Stef

March 14, 2010

Re: [Pharo-project] squeaksource is down....

by Lukas Renggli

> apparently 3 min after showing me the squeaksource is donw it was up again. > May be the watch dog (if any) was working well :) There is no watch dog other than the one that sends out mails if the web address is not reachable. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 14, 2010

Re: [Pharo-project] [squeak-dev] Use of #asMorph

by StÃ©phane Ducasse

On Mar 14, 2010, at 3:04 PM, Igor Stasenko wrote: > On 14 March 2010 15:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> I'm not convinced by your argumentation. >> Because >> #('a' 'b') collect: [:each | each asMorph] >> would mean to me that you get StringMorph or some morph representation of the object. > > Yes, exactly like that. > And i want to find a convenient approach how to achieve that. Means , > that from one side we having > a container (list, inspector, panel, window etc) and from other side, > we having a model which is a collection of items. > And i want to find a way, how an object, which you want to represent > in a container, could pick a most appropriate form > of its representation, BUT depending on a nature of container. it smells like a lot of magic or double dispatch? > >> If this is what you want why not but I thought you talk about container containee relationship/ >> > > I am not convinced myself that such way is feasible either. You tell :) > Usually, in most cases, a container dictating how its items should be > displayed and behave. > And usually, a model knows more than a little about items it contains > (for instance a class methods pane contains only methods, not > arbitrary objects). > >> >> >> Stef >> >> >> On Mar 14, 2010, at 2:05 PM, Igor Stasenko wrote: >> >>> On 14 March 2010 14:40, stephane ducasse <stephane.ducasse(a)gmail.com> wrote: >>>> Igor >>>> >>>> I do not know (I'm dizzy after a couple of hours of bus) but >>>> asMorph for me conveys the idea that we get a transformation of the receiver, while if this is just to >>>> change the model of a morph why not model: >>>> >>> Changing a model gives nothing: >>> >>> morph := MyListMorph new. >>> morph model: someModel. >>> >>> now, since my morph is a list, it assumes that someModel object >>> implements a protocol, which allows to extract the >>> items ( #size, #at: etc). >>> The question is, what you would do, if you want to represent each item >>> in a list as a morph, so instead of: >>> >>> strings := model items collect: [:each | each asString ]. >>> >>> you doing: >>> >>> subMorphs := model items collect: [:each | each asMorph ]. >>> ... >>> this gives you a freedom to pick any form how represent each item in a >>> list, instead of bare strings. >>> >>> >>>> >>>> Stef >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 14, 2010

Re: [Pharo-project] squeaksource is down....

by StÃ©phane Ducasse

apparently 3 min after showing me the squeaksource is donw it was up again. May be the watch dog (if any) was working well :) Stef On Mar 14, 2010, at 6:08 PM, Lukas Renggli wrote: > Not for me. > > 2010/3/14 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 14, 2010

Re: [Pharo-project] Fix 2145 - InitialExtent

by StÃ©phane Ducasse

Thanks laurent! I'm eager to see that screencast :) Stef On Mar 14, 2010, at 5:29 PM, laurent laffont wrote: > In Inbox. http://code.google.com/p/pharo/issues/detail?id=2145 > > Laurent Laffont > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 14, 2010

Re: [Pharo-project] squeaksource is down....

by Lukas Renggli

Not for me. 2010/3/14 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

March 14, 2010

Re: [Pharo-project] Collection

by Lukas Renggli

> where after a while you don't know what a given annotation does because > the logic of working is somewhere else. > I prefer a single standardized message, just like "new" and "initialize" > that have well stated intentions and not convert smalltalk in a soup of > annotations like Java currently is. What about selecting the annotation and looking for its senders? The annotation doesn't change *anything* in that regard. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 14, 2010

[Pharo-project] [update 1.1] #11269

by StÃ©phane Ducasse

11269 ----- - Issue 2145: initialExtent of Workspace is not good stef showing to laurent :) Laurent showing to stef how to screencast (stay tuned :)). Stef

March 14, 2010

[Pharo-project] squeaksource is down....

by StÃ©phane Ducasse

March 14, 2010