June 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] call for fix: fixing browser names and stupid dead navigation that works

by StÃ©phane Ducasse

On Jun 13, 2008, at 3:30 PM, Damien Cassou wrote: > On Fri, Jun 13, 2008 at 2:40 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> I send to this list the email I sent to the great omnibrowser >> developer >> list...... >> Really cool features but seems to forget the basic. if it takes me >> more than >> 5 min to find something >> may be the interface is BAD. > > Do you use pharo-dev? Not yet. Why there is a better version of the browser? Stef

June 13, 2008

[Pharo-project] Reintegration of StringSocket

by Damien Cassou

Hi, StringSocket is a class part of Nebraska. You removed that class. However, Universe uses this class to publish packages. Is it possible to reintegrate this class, at least partially to support Universe? Bye -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 13, 2008

Re: [Pharo-project] call for fix: fixing browser names and stupid dead navigation that works

by Damien Cassou

On Fri, Jun 13, 2008 at 2:40 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I send to this list the email I sent to the great omnibrowser developer > list...... > Really cool features but seems to forget the basic. if it takes me more than > 5 min to find something > may be the interface is BAD. Do you use pharo-dev? -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 13, 2008

Re: [Pharo-project] Bug for harvesting

by Damien Cassou

On Thu, Jun 12, 2008 at 3:42 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Fix looks ok. > > Not sure why setting the superclass to nil is actually needed, but else the > test is not green (note, the "requires algorithm" was introduced by David > Vainsencher and was originally implemented by Nathanael; does somebody use > it? maybe in the Squeak-dev image?). Dynamic Protocols use it. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 13, 2008

Re: [Pharo-project] Pharo logos

by StÃ©phane Ducasse

Yes :) and this is cool. Stef > > > I like the blue one! > >> My remark on this one was that it may be better to get two larger >> streams of light. >> > > > One thing to note is that a lighhouse does emit multiple beams at > once that rotate "as a whole". > (not a blinking light, it's a constant light that shines in a couple > of directions (3-5 or so), and then > this whole contraption rotates). This means the light-beams are > never shing up or down, but just > all in one plane. The spacing between the beams is irregular, > mostly, to form the special blinking-pattern > that one sees from far (so one knows which lighthouse it is). > > http://flickr.com/photos/gina_nora_sophia/2541320670/ > http://flickr.com/photos/michaelhuge/2318327440/ > > >> Stef >> >> On Jun 13, 2008, at 1:32 PM, StÃ©phane Ducasse wrote: >> >>> >>> >>> Begin forwarded message: >>> >>>> From: Samuel MORELLO <samuel.morello(a)ouvanous.com> >>>> Date: June 13, 2008 1:27:25 PM CEDT >>>> To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> Subject: Re: [Pharo-project] Pharo logos >>>> >>> <pharo-0.4.4.pdf> >>>> >>>> >>>> Le 13 juin 08 Ã 13:12, StÃ©phane Ducasse a Ã©crit : >>>> >>>>> >>>>> >>>>> Begin forwarded message: >>>>> >>>>>> From: Oscar Nierstrasz <oscar(a)iam.unibe.ch> >>>>>> Date: June 13, 2008 12:29:32 PM CEDT >>>>>> To: An open mailing list to discuss any topics related to an >>>>>> open-source Smalltalk <pharo-project(a)lists.gforge.inria.fr> >>>>>> Subject: Re: [Pharo-project] Pharo logos >>>>>> Reply-To: An open mailing list to discuss any topics related to >>>>>> an open-source Smalltalk <pharo-project(a)lists.gforge.inria.fr> >>>>>> >>>>>> >>>>>> Cool graphics! >>>>>> >>>>>> But ... the first one looks too much like we are struggling in >>>>>> the fog, and the last one looks like we are about to come under >>>>>> the shadow of an eclipse (!). >>>>>> >>>>>> Is it possible to have the fog at the bottom, so the lighthouse >>>>>> is emerging from the fog? >>>>>> >>>>>> - on >>>>>> >>>>>> On Jun 13, 2008, at 11:50, StÃ©phane Ducasse wrote: >>>>>> >>>>>>> Hi guys >>>>>>> >>>>>>> here are some proposals >>>>>>> I like the blue one. But there have something. >>>>>>> Please comment >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> <Picture 2.pdf><Picture 3.pdf><Picture >>>>>>> 1.pdf>_______________________________________________ >>>>>>> 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 > > Marcus > -- > Marcus Denker -- denker(a)iam.unibe.ch > http://www.iam.unibe.ch/~denker > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 13, 2008

[Pharo-project] call for fix: fixing browser names and stupid dead navigation that works

by StÃ©phane Ducasse

Hi guys I send to this list the email I sent to the great omnibrowser developer list...... Really cool features but seems to forget the basic. if it takes me more than 5 min to find something may be the interface is BAD. Stef how with the new browser can I get class Variable refs? I ask this question for OB-Shittynamebrowser and OB- shittynamepackagebrowser. Do you expect that a newbie can find his way with browser named like that? this question quite stupid question reveals that the command if there exist are far from readable for a normal programmer. Of course feel free to think that I'm an idiot. When somebody instead of inventing new features will do a real usability analysis? Stef

June 13, 2008

Re: [Pharo-project] Pharo logos

by Marcus Denker

On 13.06.2008, at 13:43, StÃ©phane Ducasse wrote: I like the blue one! > My remark on this one was that it may be better to get two larger > streams of light. > One thing to note is that a lighhouse does emit multiple beams at once that rotate "as a whole". (not a blinking light, it's a constant light that shines in a couple of directions (3-5 or so), and then this whole contraption rotates). This means the light-beams are never shing up or down, but just all in one plane. The spacing between the beams is irregular, mostly, to form the special blinking-pattern that one sees from far (so one knows which lighthouse it is). http://flickr.com/photos/gina_nora_sophia/2541320670/ http://flickr.com/photos/michaelhuge/2318327440/ > Stef > > On Jun 13, 2008, at 1:32 PM, StÃ©phane Ducasse wrote: > >> >> >> Begin forwarded message: >> >>> From: Samuel MORELLO <samuel.morello(a)ouvanous.com> >>> Date: June 13, 2008 1:27:25 PM CEDT >>> To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> Subject: Re: [Pharo-project] Pharo logos >>> >> <pharo-0.4.4.pdf> >>> >>> >>> Le 13 juin 08 Ã 13:12, StÃ©phane Ducasse a Ã©crit : >>> >>>> >>>> >>>> Begin forwarded message: >>>> >>>>> From: Oscar Nierstrasz <oscar(a)iam.unibe.ch> >>>>> Date: June 13, 2008 12:29:32 PM CEDT >>>>> To: An open mailing list to discuss any topics related to an >>>>> open-source Smalltalk <pharo-project(a)lists.gforge.inria.fr> >>>>> Subject: Re: [Pharo-project] Pharo logos >>>>> Reply-To: An open mailing list to discuss any topics related to >>>>> an open-source Smalltalk <pharo-project(a)lists.gforge.inria.fr> >>>>> >>>>> >>>>> Cool graphics! >>>>> >>>>> But ... the first one looks too much like we are struggling in >>>>> the fog, and the last one looks like we are about to come under >>>>> the shadow of an eclipse (!). >>>>> >>>>> Is it possible to have the fog at the bottom, so the lighthouse >>>>> is emerging from the fog? >>>>> >>>>> - on >>>>> >>>>> On Jun 13, 2008, at 11:50, StÃ©phane Ducasse wrote: >>>>> >>>>>> Hi guys >>>>>> >>>>>> here are some proposals >>>>>> I like the blue one. But there have something. >>>>>> Please comment >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <Picture 2.pdf><Picture 3.pdf><Picture >>>>>> 1.pdf>_______________________________________________ >>>>>> 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 Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

June 13, 2008

Re: [Pharo-project] Pharo logos

by Noury Bouraqadi

I do too. I'm wondering whether it would be better to fill the circle (lighthouse background) in white. Noury On 13 juin 08, at 13:15, Alexandre Bergel wrote: > i like the blue one as well.. > > Alexandre > > > On 13 Jun 2008, at 12:29, Oscar Nierstrasz wrote: > >> >> Cool graphics! >> >> But ... the first one looks too much like we are struggling in the >> fog, and the last one looks like we are about to come under the >> shadow of an eclipse (!). >> >> Is it possible to have the fog at the bottom, so the lighthouse is >> emerging from the fog? >> >> - on >> >> On Jun 13, 2008, at 11:50, StÃ©phane Ducasse wrote: >> >>> Hi guys >>> >>> here are some proposals >>> I like the blue one. But there have something. >>> Please comment >>> >>> Stef >>> >>> >>> >>> >>> <Picture 2.pdf><Picture 3.pdf><Picture >>> 1.pdf>_______________________________________________ >>> 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 >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > Noury Bouraqadi ------------------------------------------------------------------ Dr. Noury Bouraqadi - Enseignant/Chercheur Responsable de l'enseignement de l'informatique ARMINES - Ecole des Mines de Douai - Dept. I.A. http://vst.ensm-douai.fr/noury European Smalltalk Users Group Board http://www.esug.org ------------------------------------------------------------------

June 13, 2008

Re: [Pharo-project] DNU rootsOfTheWorld

by StÃ©phane Ducasse

So Adrian I have the impression that you remove too much :) Stef On Jun 13, 2008, at 1:51 PM, StÃ©phane Ducasse wrote: > Once loaded the latest version and update > > When I open an environment to apply refactoring > I get doesNotUnderstand: #rootsOfTheWorld > > Stef > > > > > > > > From: stephane.ducasse(a)inria.fr > To: squeak-dev(a)lists.squeakfoundation.org > Subject: [BUG]Class class(Object)>>doesNotUnderstand: #rootsOfTheWorld > > here insert explanation of what you were doing, suspect changes > you've made and so forth. > > 13 June 2008 1:50:10 pm > > VM: Mac OS - a SmalltalkImage > Image: Pharo0.1 [latest update: #10037] > > SecurityManager state: > Restricted: false > FileAccess: true > SocketAccess: true > Working Dir /Users/ducasse/Desktop/Pharo/Pharo0.1-10036-2008-06-10 > Trusted Dir /foobar/tooBar/forSqueak/bogus > Untrusted Dir /Users/ducasse/Library/Preferences/Squeak/Internet/My > Squeak > > Class class(Object)>>doesNotUnderstand: #rootsOfTheWorld > Receiver: Class > Arguments and temporary variables: > aMessage: rootsOfTheWorld > Receiver's instance variables: > superclass: ClassDescription > methodDict: a MethodDictionary(#addClassVarName:->a > CompiledMethod (608) #addIn...etc... > format: 156 > instanceVariables: #('subclasses' 'name' 'classPool' > 'sharedPools' 'environment...etc... > organization: ('accessing' basicCategory basicCategory: > basicLocalSelectors bas...etc... > subclasses: an Array(ObjectTracer class PseudoContext class > ProtoObject class) > name: #Class > classPool: a Dictionary() > sharedPools: nil > environment: a SystemDictionary(lots of globals) > category: #'Kernel-Classes' > traitComposition: TBehaviorCategorization > localSelectors: an IdentitySet(#classPool: #sharing: > #removeFromSystemUnlogged ...etc... > > BrowserEnvironment>>allClassesDo: > Receiver: Smalltalk > Arguments and temporary variables: > aBlock: [] in BrowserEnvironment>>classesDo: {[:each | (self > includesClass: eac...etc... > each: nil > Receiver's instance variables: > label: nil > searchStrings: nil > > BrowserEnvironment>>classesDo: > Receiver: Smalltalk > Arguments and temporary variables: > aBlock: [] in BrowserEnvironment>>classesAndSelectorsDo: {[:class > | self sele...etc... > each: nil > Receiver's instance variables: > label: nil > searchStrings: nil > > BrowserEnvironment>>classesAndSelectorsDo: > Receiver: Smalltalk > Arguments and temporary variables: > aBlock: [] in OREnvironmentNode>>selectorEnvironment > {[:class :selector | selec...etc... > class: nil > sel: nil > Receiver's instance variables: > label: nil > searchStrings: nil > > > --- The full stack --- > Class class(Object)>>doesNotUnderstand: #rootsOfTheWorld > BrowserEnvironment>>allClassesDo: > BrowserEnvironment>>classesDo: > BrowserEnvironment>>classesAndSelectorsDo: > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > OREnvironmentNode>>selectorEnvironment > ORSystemBrowser>>setMetaNode:node: > ORSystemBrowser class(OBBrowser > class)>>metaNode:root:selection:panels: > ORSystemBrowser class(OBBrowser class)>>root:selection: > ORSystemBrowser class(OBBrowser class)>>root: > ORSystemBrowser class(OREnvironmentBrowser class)>>on: > ORCmdSpawnEnvironment>>execute > ORCmdSpawnEnvironment(OBCommand)>>perform:orSendTo: > [] in MenuItemMorph>>invokeWithEvent: {[(selArgCount := selector > numArgs) = 0 ifTrue: [target perform: selector] ...]} > BlockContext>>ensure: > CursorWithMask(Cursor)>>showWhile: > MenuItemMorph>>invokeWithEvent: > MenuItemMorph>>mouseUp: > MenuItemMorph>>handleMouseUp: > MouseButtonEvent>>sentTo: > MenuItemMorph(Morph)>>handleEvent: > MorphicEventDispatcher>>dispatchDefault:with: > MorphicEventDispatcher>>dispatchEvent:with: > MenuItemMorph(Morph)>>processEvent:using: > MorphicEventDispatcher>>dispatchDefault:with: > MorphicEventDispatcher>>dispatchEvent:with: > MenuMorph(Morph)>>processEvent:using: > MenuMorph(Morph)>>processEvent: > MenuMorph>>handleFocusEvent: > [] in HandMorph>>sendFocusEvent:to:clear: {[ActiveHand := self. > ActiveEvent := anEvent. result := focusHolder han...]} > [] in PasteUpMorph>>becomeActiveDuring: {[aBlock value]} > BlockContext>>on:do: > PasteUpMorph>>becomeActiveDuring: > HandMorph>>sendFocusEvent:to:clear: > HandMorph>>sendEvent:focus:clear: > HandMorph>>sendMouseEvent: > HandMorph>>handleEvent: > HandMorph>>processEvents > [] in WorldState>>doOneCycleNowFor: {[:h | ActiveHand := h. h > processEvents. ActiveHand := nil]} > Array(SequenceableCollection)>>do: > WorldState>>handsDo: > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: > PasteUpMorph>>doOneCycle > [] in Project class>>spawnNewProcess {[[World doOneCycle. Processor > yield. false] whileFalse. nil]} > [] in BlockContext>>newProcess {[self value. Processor > terminateActive]} > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 13, 2008

[Pharo-project] DNU rootsOfTheWorld

by StÃ©phane Ducasse

Once loaded the latest version and update When I open an environment to apply refactoring I get doesNotUnderstand: #rootsOfTheWorld Stef From: stephane.ducasse(a)inria.fr To: squeak-dev(a)lists.squeakfoundation.org Subject: [BUG]Class class(Object)>>doesNotUnderstand: #rootsOfTheWorld here insert explanation of what you were doing, suspect changes you've made and so forth. 13 June 2008 1:50:10 pm VM: Mac OS - a SmalltalkImage Image: Pharo0.1 [latest update: #10037] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir /Users/ducasse/Desktop/Pharo/Pharo0.1-10036-2008-06-10 Trusted Dir /foobar/tooBar/forSqueak/bogus Untrusted Dir /Users/ducasse/Library/Preferences/Squeak/Internet/My Squeak Class class(Object)>>doesNotUnderstand: #rootsOfTheWorld Receiver: Class Arguments and temporary variables: aMessage: rootsOfTheWorld Receiver's instance variables: superclass: ClassDescription methodDict: a MethodDictionary(#addClassVarName:->a CompiledMethod (608) #addIn...etc... format: 156 instanceVariables: #('subclasses' 'name' 'classPool' 'sharedPools' 'environment...etc... organization: ('accessing' basicCategory basicCategory: basicLocalSelectors bas...etc... subclasses: an Array(ObjectTracer class PseudoContext class ProtoObject class) name: #Class classPool: a Dictionary() sharedPools: nil environment: a SystemDictionary(lots of globals) category: #'Kernel-Classes' traitComposition: TBehaviorCategorization localSelectors: an IdentitySet(#classPool: #sharing: #removeFromSystemUnlogged ...etc... BrowserEnvironment>>allClassesDo: Receiver: Smalltalk Arguments and temporary variables: aBlock: [] in BrowserEnvironment>>classesDo: {[:each | (self includesClass: eac...etc... each: nil Receiver's instance variables: label: nil searchStrings: nil BrowserEnvironment>>classesDo: Receiver: Smalltalk Arguments and temporary variables: aBlock: [] in BrowserEnvironment>>classesAndSelectorsDo: {[:class | self sele...etc... each: nil Receiver's instance variables: label: nil searchStrings: nil BrowserEnvironment>>classesAndSelectorsDo: Receiver: Smalltalk Arguments and temporary variables: aBlock: [] in OREnvironmentNode>>selectorEnvironment {[:class :selector | selec...etc... class: nil sel: nil Receiver's instance variables: label: nil searchStrings: nil --- The full stack --- Class class(Object)>>doesNotUnderstand: #rootsOfTheWorld BrowserEnvironment>>allClassesDo: BrowserEnvironment>>classesDo: BrowserEnvironment>>classesAndSelectorsDo: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - OREnvironmentNode>>selectorEnvironment ORSystemBrowser>>setMetaNode:node: ORSystemBrowser class(OBBrowser class)>>metaNode:root:selection:panels: ORSystemBrowser class(OBBrowser class)>>root:selection: ORSystemBrowser class(OBBrowser class)>>root: ORSystemBrowser class(OREnvironmentBrowser class)>>on: ORCmdSpawnEnvironment>>execute ORCmdSpawnEnvironment(OBCommand)>>perform:orSendTo: [] in MenuItemMorph>>invokeWithEvent: {[(selArgCount := selector numArgs) = 0 ifTrue: [target perform: selector] ...]} BlockContext>>ensure: CursorWithMask(Cursor)>>showWhile: MenuItemMorph>>invokeWithEvent: MenuItemMorph>>mouseUp: MenuItemMorph>>handleMouseUp: MouseButtonEvent>>sentTo: MenuItemMorph(Morph)>>handleEvent: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>dispatchEvent:with: MenuItemMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>dispatchEvent:with: MenuMorph(Morph)>>processEvent:using: MenuMorph(Morph)>>processEvent: MenuMorph>>handleFocusEvent: [] in HandMorph>>sendFocusEvent:to:clear: {[ActiveHand := self. ActiveEvent := anEvent. result := focusHolder han...]} [] in PasteUpMorph>>becomeActiveDuring: {[aBlock value]} BlockContext>>on:do: PasteUpMorph>>becomeActiveDuring: HandMorph>>sendFocusEvent:to:clear: HandMorph>>sendEvent:focus:clear: HandMorph>>sendMouseEvent: HandMorph>>handleEvent: HandMorph>>processEvents [] in WorldState>>doOneCycleNowFor: {[:h | ActiveHand := h. h processEvents. ActiveHand := nil]} Array(SequenceableCollection)>>do: WorldState>>handsDo: WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: PasteUpMorph>>doOneCycle [] in Project class>>spawnNewProcess {[[World doOneCycle. Processor yield. false] whileFalse. nil]} [] in BlockContext>>newProcess {[self value. Processor terminateActive]}

June 13, 2008

Re: [Pharo-project] Pharo logos

by Norbert Hartl

On Fri, 2008-06-13 at 11:50 +0200, StÃ©phane Ducasse wrote: > Hi guys > > here are some proposals > I like the blue one. But there have something. > Please comment > I like the blue one, too. I don't know if it is important but lighthouses don't have just a light bubble in their center. There is a rotating lamp (or many). Without that it is not a lighthouse (the lamps and velocity are a code). Most images, icons and pictograms honor the moving part somehow. Maybe there are ideas to visualize that. Norbert

June 13, 2008

Re: [Pharo-project] Pharo logos

by StÃ©phane Ducasse

My remark on this one was that it may be better to get two larger streams of light. Stef On Jun 13, 2008, at 1:32 PM, StÃ©phane Ducasse wrote: > > > Begin forwarded message: > >> From: Samuel MORELLO <samuel.morello(a)ouvanous.com> >> Date: June 13, 2008 1:27:25 PM CEDT >> To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> Subject: Re: [Pharo-project] Pharo logos >> > <pharo-0.4.4.pdf> >> >> >> Le 13 juin 08 Ã 13:12, StÃ©phane Ducasse a Ã©crit : >> >>> >>> >>> Begin forwarded message: >>> >>>> From: Oscar Nierstrasz <oscar(a)iam.unibe.ch> >>>> Date: June 13, 2008 12:29:32 PM CEDT >>>> To: An open mailing list to discuss any topics related to an open- >>>> source Smalltalk <pharo-project(a)lists.gforge.inria.fr> >>>> Subject: Re: [Pharo-project] Pharo logos >>>> Reply-To: An open mailing list to discuss any topics related to >>>> an open-source Smalltalk <pharo-project(a)lists.gforge.inria.fr> >>>> >>>> >>>> Cool graphics! >>>> >>>> But ... the first one looks too much like we are struggling in >>>> the fog, and the last one looks like we are about to come under >>>> the shadow of an eclipse (!). >>>> >>>> Is it possible to have the fog at the bottom, so the lighthouse >>>> is emerging from the fog? >>>> >>>> - on >>>> >>>> On Jun 13, 2008, at 11:50, StÃ©phane Ducasse wrote: >>>> >>>>> Hi guys >>>>> >>>>> here are some proposals >>>>> I like the blue one. But there have something. >>>>> Please comment >>>>> >>>>> Stef >>>>> >>>>> >>>>> >>>>> >>>>> <Picture 2.pdf><Picture 3.pdf><Picture >>>>> 1.pdf>_______________________________________________ >>>>> 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

June 13, 2008

Fwd: [Pharo-project] Pharo logos

by StÃ©phane Ducasse

Begin forwarded message: > From: Samuel MORELLO <samuel.morello(a)ouvanous.com> > Date: June 13, 2008 1:27:25 PM CEDT > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: [Pharo-project] Pharo logos > > > Le 13 juin 08 Ã 13:12, StÃ©phane Ducasse a Ã©crit : > >> >> >> Begin forwarded message: >> >>> From: Oscar Nierstrasz <oscar(a)iam.unibe.ch> >>> Date: June 13, 2008 12:29:32 PM CEDT >>> To: An open mailing list to discuss any topics related to an open- >>> source Smalltalk <pharo-project(a)lists.gforge.inria.fr> >>> Subject: Re: [Pharo-project] Pharo logos >>> Reply-To: An open mailing list to discuss any topics related to an >>> open-source Smalltalk <pharo-project(a)lists.gforge.inria.fr> >>> >>> >>> Cool graphics! >>> >>> But ... the first one looks too much like we are struggling in the >>> fog, and the last one looks like we are about to come under the >>> shadow of an eclipse (!). >>> >>> Is it possible to have the fog at the bottom, so the lighthouse is >>> emerging from the fog? >>> >>> - on >>> >>> On Jun 13, 2008, at 11:50, StÃ©phane Ducasse wrote: >>> >>>> Hi guys >>>> >>>> here are some proposals >>>> I like the blue one. But there have something. >>>> Please comment >>>> >>>> Stef >>>> >>>> >>>> >>>> >>>> <Picture 2.pdf><Picture 3.pdf><Picture >>>> 1.pdf>_______________________________________________ >>>> 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 >>> >> >

June 13, 2008

Re: [Pharo-project] Pharo logos

by Serge Stinckwich

On Fri, Jun 13, 2008 at 1:15 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > i like the blue one as well.. Yes i also like this one. -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 13, 2008

Re: [Pharo-project] Pharo logos

by Alexandre Bergel

i like the blue one as well.. Alexandre On 13 Jun 2008, at 12:29, Oscar Nierstrasz wrote: > > Cool graphics! > > But ... the first one looks too much like we are struggling in the > fog, and the last one looks like we are about to come under the > shadow of an eclipse (!). > > Is it possible to have the fog at the bottom, so the lighthouse is > emerging from the fog? > > - on > > On Jun 13, 2008, at 11:50, StÃ©phane Ducasse wrote: > >> Hi guys >> >> here are some proposals >> I like the blue one. But there have something. >> Please comment >> >> Stef >> >> >> >> >> <Picture 2.pdf><Picture 3.pdf><Picture >> 1.pdf>_______________________________________________ >> 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 13, 2008

Re: [Pharo-project] Pharo logos

by StÃ©phane Ducasse

:) I thought about that too. I passed the remark to samuel. On Jun 13, 2008, at 12:29 PM, Oscar Nierstrasz wrote: > > Cool graphics! > > But ... the first one looks too much like we are struggling in the > fog, and the last one looks like we are about to come under the > shadow of an eclipse (!). > > Is it possible to have the fog at the bottom, so the lighthouse is > emerging from the fog? > > - on > > On Jun 13, 2008, at 11:50, StÃ©phane Ducasse wrote: > >> Hi guys >> >> here are some proposals >> I like the blue one. But there have something. >> Please comment >> >> Stef >> >> >> >> >> <Picture 2.pdf><Picture 3.pdf><Picture >> 1.pdf>_______________________________________________ >> 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 >

June 13, 2008

Re: [Pharo-project] ScriptLoader

by StÃ©phane Ducasse

> Can somebody explain me what benefit we gain by using > ScriptLoader for updates? What can it do more/better than > just plain changesets? Plain cs are used to load scriptloader version. The idea is that we can gather some logic in a class and metadata for some of the actions performed. Normally scriptloader should not stay in a final image. Then scriptloader is versionned in squeaksource, we want to avoid to have cs around. > Please have a look at > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-June/129234.html > > How we like to deal with? In the past we prefered not to remove updates to have the complete history without having to reload each individual release script. Now I should clean a bit this class. Stef > > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 13, 2008

Re: [Pharo-project] Broken tests

by StÃ©phane Ducasse

On Jun 13, 2008, at 12:06 PM, Norbert Hartl wrote: > On Fri, 2008-06-13 at 11:17 +0200, StÃ©phane Ducasse wrote: >> On Jun 13, 2008, at 11:08 AM, Norbert Hartl wrote: >> >>> And please take into account my posting "Removing ScriptLoader >>> legacy" on squeak-dev. >> >> >> I could not find it. >> Can you point it to me? >> >> > http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-June/129234.html > > In the meantie I uploaded a fix for ReleaseTest>>testUndeclared. It > is called SLICE-ReleaseTestFixUndeclared. > Seldomly a lot of the issues were missing class variables. Even in > newer > code from you. In ScriptLoader you have inboxRepository as instance > var > but in method inboxRepository you use InboxRepository. As the same is > used from the class side I assumed you wanted to use a class var. Yes this is a class variable. I will check what you did. > > > Norbert >>> Especially things in ScriptLoader are subject to >>> Undeclared which lets the ReleaseTest fail. I had a talk on irc >>> and it >>> seems that for 3.10 that were removed (from Undeclared) manually (I >>> have >>> no other idea). I'll have look if ScriptLoader is the only suspect. >>> >> >> >> _______________________________________________ >> 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 >

June 13, 2008

Re: [Pharo-project] Pharo logos

by Oscar Nierstrasz

Cool graphics! But ... the first one looks too much like we are struggling in the fog, and the last one looks like we are about to come under the shadow of an eclipse (!). Is it possible to have the fog at the bottom, so the lighthouse is emerging from the fog? - on On Jun 13, 2008, at 11:50, StÃ©phane Ducasse wrote: > Hi guys > > here are some proposals > I like the blue one. But there have something. > Please comment > > Stef > > > > > <Picture 2.pdf><Picture 3.pdf><Picture > 1.pdf>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 13, 2008

[Pharo-project] ScriptLoader

by Norbert Hartl

Can somebody explain me what benefit we gain by using ScriptLoader for updates? What can it do more/better than just plain changesets? Please have a look at http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-June/129234.html How we like to deal with? Norbert

June 13, 2008

Re: [Pharo-project] Broken tests

by Norbert Hartl

On Fri, 2008-06-13 at 11:17 +0200, StÃ©phane Ducasse wrote: > On Jun 13, 2008, at 11:08 AM, Norbert Hartl wrote: > > > And please take into account my posting "Removing ScriptLoader > > legacy" on squeak-dev. > > > I could not find it. > Can you point it to me? > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-June/129234.html In the meantie I uploaded a fix for ReleaseTest>>testUndeclared. It is called SLICE-ReleaseTestFixUndeclared. Seldomly a lot of the issues were missing class variables. Even in newer code from you. In ScriptLoader you have inboxRepository as instance var but in method inboxRepository you use InboxRepository. As the same is used from the class side I assumed you wanted to use a class var. Norbert > > Especially things in ScriptLoader are subject to > > Undeclared which lets the ReleaseTest fail. I had a talk on irc and it > > seems that for 3.10 that were removed (from Undeclared) manually (I > > have > > no other idea). I'll have look if ScriptLoader is the only suspect. > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 13, 2008

Re: [Pharo-project] Pharo logos

by Norbert Hartl

On Fri, 2008-06-13 at 11:50 +0200, StÃ©phane Ducasse wrote: > Hi guys > > here are some proposals > I like the blue one. But there have something. > Please comment > The circle of the light should be clipped by the darker area below. Otherwise the perpective flips and it appears odd. Norbert

June 13, 2008

Re: [Pharo-project] Need code review

by Norbert Hartl

Stef wrote down subject lines from postings to this list http://lists.gforge.inria.fr/pipermail/pharo-project/2008-June/000238.html http://lists.gforge.inria.fr/pipermail/pharo-project/2008-June/000323.html Norbert On Fri, 2008-06-13 at 11:37 +0200, Alexandre Bergel wrote: > Sorry to weak up so lately, but where the source code is accessible ? > I spent few minutes on looking at: > - PharoInBox > - list of taks on gforge > - list of issues on google > > and I haven't found where the code to review could be... > Any hint? > > Alexandre > > > On 13 Jun 2008, at 11:18, StÃ©phane Ducasse wrote: > > > Hi guys > > > > I would like some other people to have a look at > > > > [Pharo-project] Hunting down nebraska > > [Pharo-project] MVC removal step2 investigations > > > > Can somebody have a look? > > > > Stef > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > >

June 13, 2008

[Pharo-project] Pharo logos

by StÃ©phane Ducasse

Hi guys here are some proposals I like the blue one. But there have something. Please comment Stef

June 13, 2008

Re: [Pharo-project] Need code review

by Alexandre Bergel

Sorry to weak up so lately, but where the source code is accessible ? I spent few minutes on looking at: - PharoInBox - list of taks on gforge - list of issues on google and I haven't found where the code to review could be... Any hint? Alexandre On 13 Jun 2008, at 11:18, StÃ©phane Ducasse wrote: > Hi guys > > I would like some other people to have a look at > > [Pharo-project] Hunting down nebraska > [Pharo-project] MVC removal step2 investigations > > Can somebody have a look? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 13, 2008

[Pharo-project] Need code review

by StÃ©phane Ducasse

Hi guys I would like some other people to have a look at [Pharo-project] Hunting down nebraska [Pharo-project] MVC removal step2 investigations Can somebody have a look? Stef

June 13, 2008

Re: [Pharo-project] Broken tests

by StÃ©phane Ducasse

On Jun 13, 2008, at 11:08 AM, Norbert Hartl wrote: > And please take into account my posting "Removing ScriptLoader > legacy" on squeak-dev. I could not find it. Can you point it to me? > Especially things in ScriptLoader are subject to > Undeclared which lets the ReleaseTest fail. I had a talk on irc and it > seems that for 3.10 that were removed (from Undeclared) manually (I > have > no other idea). I'll have look if ScriptLoader is the only suspect. >

June 13, 2008

Re: [Pharo-project] Broken tests

by StÃ©phane Ducasse

On Jun 13, 2008, at 11:08 AM, Norbert Hartl wrote: > And please take into account my posting "Removing ScriptLoader > legacy" on squeak-dev. Ok I missed it. > Especially things in ScriptLoader are subject to > Undeclared which lets the ReleaseTest fail. Yes We should clean that. > I had a talk on irc and it > seems that for 3.10 that were removed (from Undeclared) manually (I > have > no other idea). I'll have look if ScriptLoader is the only suspect. > > Norbert > > > On Fri, 2008-06-13 at 08:23 +0200, StÃ©phane Ducasse wrote: >> Excellent we are getting there. >> Today I will harvest them and the changes of damien. >> We should take into account the feedback of andreas on Nan. >> >> Stef >> >> On Jun 12, 2008, at 11:24 PM, Adrian Lienhard wrote: >> >>> I've fixed the following 7 tests (see inbox: SLICE-test-fixes.al. >>> 1.mcz): >>> >>> testRootsOfTheWorld -- test removed >>> testLocalMethodWithSameCodeInTrait -- removed duplicated method >>> ClassDescription>>fileOutCategory: >>> testFinalizationOfEquals -- test fixed >>> testHash -- remove all assertions/tests that have hardcoded hash >>> values >>> DateAndTimeEpochTest>>#testHash >>> DateAndTimeLeapTest>>#testHash >>> TimeTest>>#testHash >>> TimespanTest>>#testHash >>> >>> Now 8 tests are still failing. We are getting there... >>> >>> Cheers, >>> Adrian >>> >>> On Jun 11, 2008, at 19:07 , StÃ©phane Ducasse wrote: >>> >>>> excellent! >>>> >>>> Stef >>>> >>>> On Jun 11, 2008, at 4:04 PM, Oscar Nierstrasz wrote: >>>> >>>>> >>>>> Just for phun, I ran all the tests in the Pharo image. There are >>>>> only 13 failures, 2 expected failures, and no errors! >>>>> >>>>> I have started a page to give an overview: >>>>> >>>>> http://code.google.com/p/pharo/wiki/BrokenTests >>>>> >>>>> Please update this page with an appropriate comment if you are >>>>> working on any of these (or if you fix them). >>>>> >>>>> - on >>>>> >>>>> _______________________________________________ >>>>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 13, 2008

Re: [Pharo-project] Broken tests

by Norbert Hartl

And please take into account my posting "Removing ScriptLoader legacy" on squeak-dev. Especially things in ScriptLoader are subject to Undeclared which lets the ReleaseTest fail. I had a talk on irc and it seems that for 3.10 that were removed (from Undeclared) manually (I have no other idea). I'll have look if ScriptLoader is the only suspect. Norbert On Fri, 2008-06-13 at 08:23 +0200, StÃ©phane Ducasse wrote: > Excellent we are getting there. > Today I will harvest them and the changes of damien. > We should take into account the feedback of andreas on Nan. > > Stef > > On Jun 12, 2008, at 11:24 PM, Adrian Lienhard wrote: > > > I've fixed the following 7 tests (see inbox: SLICE-test-fixes.al. > > 1.mcz): > > > > testRootsOfTheWorld -- test removed > > testLocalMethodWithSameCodeInTrait -- removed duplicated method > > ClassDescription>>fileOutCategory: > > testFinalizationOfEquals -- test fixed > > testHash -- remove all assertions/tests that have hardcoded hash > > values > > DateAndTimeEpochTest>>#testHash > > DateAndTimeLeapTest>>#testHash > > TimeTest>>#testHash > > TimespanTest>>#testHash > > > > Now 8 tests are still failing. We are getting there... > > > > Cheers, > > Adrian > > > > On Jun 11, 2008, at 19:07 , StÃ©phane Ducasse wrote: > > > >> excellent! > >> > >> Stef > >> > >> On Jun 11, 2008, at 4:04 PM, Oscar Nierstrasz wrote: > >> > >>> > >>> Just for phun, I ran all the tests in the Pharo image. There are > >>> only 13 failures, 2 expected failures, and no errors! > >>> > >>> I have started a page to give an overview: > >>> > >>> http://code.google.com/p/pharo/wiki/BrokenTests > >>> > >>> Please update this page with an appropriate comment if you are > >>> working on any of these (or if you fix them). > >>> > >>> - on > >>> > >>> _______________________________________________ > >>> 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

June 13, 2008

Re: [Pharo-project] Broken tests

by StÃ©phane Ducasse

Excellent we are getting there. Today I will harvest them and the changes of damien. We should take into account the feedback of andreas on Nan. Stef On Jun 12, 2008, at 11:24 PM, Adrian Lienhard wrote: > I've fixed the following 7 tests (see inbox: SLICE-test-fixes.al. > 1.mcz): > > testRootsOfTheWorld -- test removed > testLocalMethodWithSameCodeInTrait -- removed duplicated method > ClassDescription>>fileOutCategory: > testFinalizationOfEquals -- test fixed > testHash -- remove all assertions/tests that have hardcoded hash > values > DateAndTimeEpochTest>>#testHash > DateAndTimeLeapTest>>#testHash > TimeTest>>#testHash > TimespanTest>>#testHash > > Now 8 tests are still failing. We are getting there... > > Cheers, > Adrian > > On Jun 11, 2008, at 19:07 , StÃ©phane Ducasse wrote: > >> excellent! >> >> Stef >> >> On Jun 11, 2008, at 4:04 PM, Oscar Nierstrasz wrote: >> >>> >>> Just for phun, I ran all the tests in the Pharo image. There are >>> only 13 failures, 2 expected failures, and no errors! >>> >>> I have started a page to give an overview: >>> >>> http://code.google.com/p/pharo/wiki/BrokenTests >>> >>> Please update this page with an appropriate comment if you are >>> working on any of these (or if you fix them). >>> >>> - on >>> >>> _______________________________________________ >>> 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 >

June 13, 2008

Re: [Pharo-project] Broken tests

by Adrian Lienhard

I've fixed the following 7 tests (see inbox: SLICE-test-fixes.al.1.mcz): testRootsOfTheWorld -- test removed testLocalMethodWithSameCodeInTrait -- removed duplicated method ClassDescription>>fileOutCategory: testFinalizationOfEquals -- test fixed testHash -- remove all assertions/tests that have hardcoded hash values DateAndTimeEpochTest>>#testHash DateAndTimeLeapTest>>#testHash TimeTest>>#testHash TimespanTest>>#testHash Now 8 tests are still failing. We are getting there... Cheers, Adrian On Jun 11, 2008, at 19:07 , StÃ©phane Ducasse wrote: > excellent! > > Stef > > On Jun 11, 2008, at 4:04 PM, Oscar Nierstrasz wrote: > >> >> Just for phun, I ran all the tests in the Pharo image. There are >> only 13 failures, 2 expected failures, and no errors! >> >> I have started a page to give an overview: >> >> http://code.google.com/p/pharo/wiki/BrokenTests >> >> Please update this page with an appropriate comment if you are >> working on any of these (or if you fix them). >> >> - on >> >> _______________________________________________ >> 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

June 12, 2008

[Pharo-project] Improving the general quality of package

by StÃ©phane Ducasse

Hi all I would really like to see if it make sense to run SmallLint on packages. Of course we should not naively apply the proposed refactoring (some blind applications of them in the past went against speed in Graphics), still identifying and building a process to produce a bit better code quality would be great. If any of you want to give a try it would be great. I'm also thinking about having a manifesto to each package or group of package so that we can attach information and metainformation to package such as documentation... So far I'm not happy with what I did (cf DrDoc but this is one step in that direction). Stef

June 12, 2008

Re: [Pharo-project] Strange bug in TraitsTest

by Adrian Lienhard

On Jun 12, 2008, at 15:49 , Norbert Hartl wrote: > On Thu, 2008-06-12 at 15:28 +0200, Adrian Lienhard wrote: >> I don't see what could testRootsOfTheWorld be useful for. Anyway, the >> reason why this fails is because for the traits tests I use test >> resources and they are set up before all tests are run and >> testRootsOfTheWorld asserts that there are exactly 3 classes in the >> system that do not have a superclass. >> > I don't think that the test does harm. And I don't really care > about the test. What I don't understand is the "side effect". The > classes are created in TraitsTestCase. The failing test is in > ClassTest. As far as I can see the created classes are removed on > tearDown time. Well, this is how the test runner works... It first sets up all test resources (which in this case creates the offending classes), then it runs all tests, and then it releases the resources. That is, resource allocation and deallocation is "global", therefore ClassTest is affected. Hope that explains it better. Adrian > > > > Norbert > >> There are two simple solutions for this. Either remove >> testRootsOfTheWorld or change the test classes created in >> TraitsRescource to inherit from Object instead of ProtoObject. I >> would >> do the former unless somebody has a convincing argument for keeping >> that test in the image. >> >> Adrian >> >> NB: I'll also fix #testLocalMethodWithSameCodeInTrait when I'm at it >> (this tests that there do not exist duplicated methods between a >> trait >> and a class using the trait) >> >> On Jun 11, 2008, at 19:24 , Norbert Hartl wrote: >> >>> If you open a test runner and select only KernelTests-ClassTest and >>> TraitsTests-TraitsTestCase you may find a failure >>> >>> ClassTest>>testRootsOfTheWorld >>> >>> But I don't understand fully why it appears. I had once >>> the chance to get a debugger on the failure (which does >>> usually not work on this failure) and so I know that the >>> rootsOfTheWorld (which is usually 3) is 6 in size containing >>> additionally classes C3 C4 and C6. The ones which are created >>> by TraitsTestCase (see my last mail "Bug for harvest"). >>> >>> They all have a superclass of nil but they aren't included >>> in the SystemNavigation. (conditions for being included in >>> the rootsOfTheWorld) >>> >>> If you press "Run selected" again the same error occurrs >>> while pressing "Run failures" gives you all green (ok, it >>> is this way in my case) >>> >>> And I can't reproduce the same in a 3.10 image. >>> >>> It seems that there is a timing problem involved. Selecting >>> only the two test cases I get the failure every time (or nearly). >>> Selecting all tests it appears only at random. >>> >>> Any hints? >>> >>> Norbert >>> >>> >>> >>> >>> _______________________________________________ >>> 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

June 12, 2008

Re: [Pharo-project] Strange bug in TraitsTest

by StÃ©phane Ducasse

Hi adrian go for it :) Stef On Jun 12, 2008, at 3:28 PM, Adrian Lienhard wrote: > I don't see what could testRootsOfTheWorld be useful for. Anyway, > the reason why this fails is because for the traits tests I use test > resources and they are set up before all tests are run and > testRootsOfTheWorld asserts that there are exactly 3 classes in the > system that do not have a superclass. > > There are two simple solutions for this. Either remove > testRootsOfTheWorld or change the test classes created in > TraitsRescource to inherit from Object instead of ProtoObject. I > would do the former unless somebody has a convincing argument for > keeping that test in the image. > > Adrian > > NB: I'll also fix #testLocalMethodWithSameCodeInTrait when I'm at it > (this tests that there do not exist duplicated methods between a > trait and a class using the trait) > > On Jun 11, 2008, at 19:24 , Norbert Hartl wrote: > >> If you open a test runner and select only KernelTests-ClassTest and >> TraitsTests-TraitsTestCase you may find a failure >> >> ClassTest>>testRootsOfTheWorld >> >> But I don't understand fully why it appears. I had once >> the chance to get a debugger on the failure (which does >> usually not work on this failure) and so I know that the >> rootsOfTheWorld (which is usually 3) is 6 in size containing >> additionally classes C3 C4 and C6. The ones which are created >> by TraitsTestCase (see my last mail "Bug for harvest"). >> >> They all have a superclass of nil but they aren't included >> in the SystemNavigation. (conditions for being included in >> the rootsOfTheWorld) >> >> If you press "Run selected" again the same error occurrs >> while pressing "Run failures" gives you all green (ok, it >> is this way in my case) >> >> And I can't reproduce the same in a 3.10 image. >> >> It seems that there is a timing problem involved. Selecting >> only the two test cases I get the failure every time (or nearly). >> Selecting all tests it appears only at random. >> >> Any hints? >> >> Norbert >> >> >> >> >> _______________________________________________ >> 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 >

June 12, 2008

[Pharo-project] Fwd: Comment on BrokenTests in pharo

by Pharo Smalltalk

---------- Forwarded message ---------- From: <codesite-noreply(a)google.com> Date: Thu, Jun 12, 2008 at 3:16 AM Subject: Comment on BrokenTests in pharo To: pharo.smalltalk(a)gmail.com Comment by andreas.raab: 3.9 has a different manifest bit pattern for NaN than Pharo. Try this: Float nan hex "<print it>" 3.9: '7FF8000000000000' Pharo: 'FFF8000000000000' It looks like 3.9 was initialized on PPC, Pharo on Intel. Since there is an infinite number of NaN bit patterns the real solution is to use a manifest binary constant in Float initialization, i.e, Float class>>initialize "..." NaN := Float with: 16rFFF80000 with: 0. instead of the computation that is in there today. For more information: http://code.google.com/p/pharo/wiki/BrokenTests

June 12, 2008

[Pharo-project] Which tests broken in Phrao are also broken in 3.9 and 3.10

by Oscar Nierstrasz

I checked all the broken tests. It seems that there are some fixes that we should be able to harvest from 3.10. http://code.google.com/p/pharo/wiki/BrokenTests - on

June 12, 2008

Re: [Pharo-project] Strange bug in TraitsTest

by Norbert Hartl

On Thu, 2008-06-12 at 15:28 +0200, Adrian Lienhard wrote: > I don't see what could testRootsOfTheWorld be useful for. Anyway, the > reason why this fails is because for the traits tests I use test > resources and they are set up before all tests are run and > testRootsOfTheWorld asserts that there are exactly 3 classes in the > system that do not have a superclass. > I don't think that the test does harm. And I don't really care about the test. What I don't understand is the "side effect". The classes are created in TraitsTestCase. The failing test is in ClassTest. As far as I can see the created classes are removed on tearDown time. Norbert > There are two simple solutions for this. Either remove > testRootsOfTheWorld or change the test classes created in > TraitsRescource to inherit from Object instead of ProtoObject. I would > do the former unless somebody has a convincing argument for keeping > that test in the image. > > Adrian > > NB: I'll also fix #testLocalMethodWithSameCodeInTrait when I'm at it > (this tests that there do not exist duplicated methods between a trait > and a class using the trait) > > On Jun 11, 2008, at 19:24 , Norbert Hartl wrote: > > > If you open a test runner and select only KernelTests-ClassTest and > > TraitsTests-TraitsTestCase you may find a failure > > > > ClassTest>>testRootsOfTheWorld > > > > But I don't understand fully why it appears. I had once > > the chance to get a debugger on the failure (which does > > usually not work on this failure) and so I know that the > > rootsOfTheWorld (which is usually 3) is 6 in size containing > > additionally classes C3 C4 and C6. The ones which are created > > by TraitsTestCase (see my last mail "Bug for harvest"). > > > > They all have a superclass of nil but they aren't included > > in the SystemNavigation. (conditions for being included in > > the rootsOfTheWorld) > > > > If you press "Run selected" again the same error occurrs > > while pressing "Run failures" gives you all green (ok, it > > is this way in my case) > > > > And I can't reproduce the same in a 3.10 image. > > > > It seems that there is a timing problem involved. Selecting > > only the two test cases I get the failure every time (or nearly). > > Selecting all tests it appears only at random. > > > > Any hints? > > > > Norbert > > > > > > > > > > _______________________________________________ > > 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

June 12, 2008

Re: [Pharo-project] Bug for harvesting

by Adrian Lienhard

Fix looks ok. Not sure why setting the superclass to nil is actually needed, but else the test is not green (note, the "requires algorithm" was introduced by David Vainsencher and was originally implemented by Nathanael; does somebody use it? maybe in the Squeak-dev image?). Adrian On Jun 11, 2008, at 20:50 , Victor Rodriguez wrote: > On Wed, Jun 11, 2008 at 1:12 PM, Norbert Hartl <norbert(a)hartl.name> > wrote: >> Hi, >> >> I opened a bug a few minutes ago which you may find interesting >> for harvest. >> >> http://bugs.squeak.org/view.php?id=7090 > > I have filed this as Issue 13. I left the state as NEW. > > Saludos, > > Victor. > >> Norbert >> >> >> _______________________________________________ >> 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

June 12, 2008

Re: [Pharo-project] Strange bug in TraitsTest

by Adrian Lienhard

I don't see what could testRootsOfTheWorld be useful for. Anyway, the reason why this fails is because for the traits tests I use test resources and they are set up before all tests are run and testRootsOfTheWorld asserts that there are exactly 3 classes in the system that do not have a superclass. There are two simple solutions for this. Either remove testRootsOfTheWorld or change the test classes created in TraitsRescource to inherit from Object instead of ProtoObject. I would do the former unless somebody has a convincing argument for keeping that test in the image. Adrian NB: I'll also fix #testLocalMethodWithSameCodeInTrait when I'm at it (this tests that there do not exist duplicated methods between a trait and a class using the trait) On Jun 11, 2008, at 19:24 , Norbert Hartl wrote: > If you open a test runner and select only KernelTests-ClassTest and > TraitsTests-TraitsTestCase you may find a failure > > ClassTest>>testRootsOfTheWorld > > But I don't understand fully why it appears. I had once > the chance to get a debugger on the failure (which does > usually not work on this failure) and so I know that the > rootsOfTheWorld (which is usually 3) is 6 in size containing > additionally classes C3 C4 and C6. The ones which are created > by TraitsTestCase (see my last mail "Bug for harvest"). > > They all have a superclass of nil but they aren't included > in the SystemNavigation. (conditions for being included in > the rootsOfTheWorld) > > If you press "Run selected" again the same error occurrs > while pressing "Run failures" gives you all green (ok, it > is this way in my case) > > And I can't reproduce the same in a 3.10 image. > > It seems that there is a timing problem involved. Selecting > only the two test cases I get the failure every time (or nearly). > Selecting all tests it appears only at random. > > Any hints? > > Norbert > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Victor Rodriguez

Replaying to two messages: On Thu, Jun 12, 2008 at 2:47 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > On Wed, 2008-06-11 at 21:22 -0400, Victor Rodriguez wrote: [snip] >> BTW, PharoReady.cs is not available. Stephane, could you please add it? >> > I added it. I've put it into the svn and linked it from there. I don't > think the initial cs has be add inria. > > Norbert On Thu, Jun 12, 2008 at 5:07 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > It is there. > > http://pharo.gforge.inria.fr/PharoReady.cs I would say put the PharoReady.cs on the files section of the INRIA gforge. I would put it right under "Squeak / 3.9.1-7075" so that all the files needed to build Pharo from scratch are together. If we are going to use INRIA gforge for files, lets put *all* the files there, specially "published" files such as this one. If we ever really need to revision something, then we can use the SVN repository. Saludos, Victor Rodriguez. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 12, 2008

Re: [Pharo-project] Trait recent change

by Damien Cassou

On Wed, Jun 11, 2008 at 6:03 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Hi Damien, > > Yes. I recently did a refactoring to reduce the number of traits in the > kernel. That is, most of the traits are flattened down and now are only used > for code reuse between the traits and the classes inheritance branches > (traits count went down from 17 to 6). > > So if your packages change methods in traits that are now gone, you have to > adapt your packages. However, all changes I did are behavior preserving. Thank you -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 12, 2008

Re: [Pharo-project] [ANN] New release

by StÃ©phane Ducasse

It is there. http://pharo.gforge.inria.fr/PharoReady.cs

June 12, 2008

Re: [Pharo-project] Pharo, squeak and the tickets

by StÃ©phane Ducasse

On Jun 12, 2008, at 1:43 AM, Victor Rodriguez wrote: > On Wed, Jun 11, 2008 at 5:49 PM, Norbert Hartl <norbert(a)hartl.name> > wrote: > [snip] >> What would you prefer? >> >> 1. Opening issues where they belong first and let "the others" >> harvest what they think they need? >> 2. Playing back the issues to bugs.squeak.org if we find a bug >> that belongs also to squeak and bring them back by harvesting? > > This is what I propose: > > * If an issue applies to Squeak, file a report on Mantis. > >> How do we want to harvest fixes from other places? >> >> 1. Having a wiki page where issues found are written down? >> 2. Opening tickets on the google tracker for this? This would >> be "to harvest" tickets. > > * File an issue for everything we want to do in Pharo in the google > tracker, *including* for "harvesting" fixes in other projects. Yes I think that having only one flow of fixes is important. > > > Thus, I would still file an issue on the google tracker for Mantis > reports. Such issues should probably follow a template, and have a > label that indicates their origin (in addition to the description). > > As a matter of fact, I think we should file an issue for every fix > listed in the wiki pages in ThreeDotTenFixes, ThreeDotTenDotOneFixes, > etc.. This way, people can assign to themselves a given fix, and we > can more easily keep a handle on things. Yes > > The issue tracker should be the *one* place where you can find what > nees to be done. Yes > > > BTW, this leads to something else I wanted to bring up. Currently, > "harvest" means two things: 1) Put in Pharo a fix available in Squeak > (or Croquet, etc..); and 2) Move a package from the PharoInbox into > the Pharo update stream. Could we come up with a different name for > 2? Something along the lines of 'integrate', 'validate', 'process', > etc.. "Stephane is processing fix X in the PharoInbox". Yes if you have some clearer ideas than me shoot stef > > > Saludos, > > VÃctor RodrÃguez. > > >> Norbert >> >> >> _______________________________________________ >> 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 >

June 12, 2008

Re: [Pharo-project] Bug for harvesting

by StÃ©phane Ducasse

yes you are right. I will ping samuel for a logo and a nice coloring scheme On Jun 11, 2008, at 11:20 PM, Norbert Hartl wrote: > On Wed, 2008-06-11 at 14:50 -0400, Victor Rodriguez wrote: >> On Wed, Jun 11, 2008 at 1:12 PM, Norbert Hartl <norbert(a)hartl.name> >> wrote: >>> Hi, >>> >>> I opened a bug a few minutes ago which you may find interesting >>> for harvest. >>> >>> http://bugs.squeak.org/view.php?id=7090 >> >> I have filed this as Issue 13. I left the state as NEW. >> > I don't think it is good to open tickets in two different bug > trackers. I opened it on squeak.org because it is a defect that > doesn't belong to pharo. Things get messed quickly this way. > There is a wiki page MantisBugsHarvested. Why shouldn't we have > another page for bugs supposed to be harvested. They exist for > 3.10 already. > > Norbert > > P.S.: I cannot create pages in the wiki. Can someone add me, please! > The account is my email address. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Norbert Hartl

It turns a 3.9.1 image into pharo image which is able to receive the pharo update stream. It's just were everything began :) Norbert On Thu, 2008-06-12 at 10:23 +0200, Serge Stinckwich wrote: > Sorry what is the purpose of this file ? > > 2008/6/12 Norbert Hartl <norbert(a)hartl.name>: > > On Wed, 2008-06-11 at 21:22 -0400, Victor Rodriguez wrote: > >> On Wed, Jun 11, 2008 at 7:54 PM, Victor Rodriguez <victorr(a)gmail.com> wrote: > >> > On Wed, Jun 11, 2008 at 3:51 PM, StÃ©phane Ducasse > >> > <stephane.ducasse(a)inria.fr> wrote: > >> > [snip] > >> >> Is is politically really important that we use the inria infrastructure. > >> >> It will help us building Smalltalk presence inside INRIA. > >> >> So at then end we will not use the forge but only the file because we need > >> >> these counters > >> >> at that place :) > >> > > >> > Fair enough. I have disabled the "Downloads" tab in googlecode. > >> > >> I thought things better and just turned the "Downloads" tab into a > >> wiki page to redirect people to the right place. > >> > >> BTW, PharoReady.cs is not available. Stephane, could you please add it? > >> > > I added it. I've put it into the svn and linked it from there. I don't > > think the initial cs has be add inria. > > > > Norbert > > > >> Thanks, > >> > >> Victor. > >> > >> > >> > VÃctor. > >> > > >> >>> I will volunteer again and move all the existing files over. (As a > >> >>> matter of fact, I had been thinking of moving the files then proposing > >> >>> the change, but I just haven't had a chance to do it.) > >> >> > >> >> Please don't there are issues more complex under the surface but this is not > >> >> linked with pharo by itself. > >> >> > >> >>> > >> >>> > >> >>> Victor. > >> >>> > >> >>> > >> >>>> On Jun 11, 2008, at 1:39 PM, Oscar Nierstrasz wrote: > >> >>>> > >> >>>>> > >> >>>>> Ah, I thought it *was* a pharo-dev image -- it was listed under > >> >>>>> "pharo-dev" on the downloads page. > >> >>>>> > >> >>>>> http://gforge.inria.fr/frs/?group_id=1299 > >> >>>>> > >> >>>>> - on > >> >>>>> > >> >>>>> On Jun 11, 2008, at 11:12, Damien Cassou wrote: > >> >>>>> > >> >>>>>> On Wed, Jun 11, 2008 at 9:56 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> > >> >>>>>> wrote: > >> >>>>>>> > >> >>>>>>> Great! > >> >>>>>>> > >> >>>>>>> Just noticed two things: > >> >>>>>>> > >> >>>>>>> - Test Runner is missing from the Tools flap -- shouldn't it be there? > >> >>>>>> > >> >>>>>> > >> >>>>>> I think Pharo should not care about such things. Just use pharo-dev if > >> >>>>>> you want a prepared pharo image for developers. > >> >>>>>> > >> >>>>>> -- > >> >>>>>> Damien Cassou > >> >>>>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > >> >>>>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > >> >>>>>> > >> >>>>>> _______________________________________________ > >> >>>>>> 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 > >> >>> > >> >> > >> >> > >> >> _______________________________________________ > >> >> 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 > > > > > > -- > Serge Stinckwich > Smalltalkers do: [:it | All with: Class, (And love: it)] > http://blog.doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Serge Stinckwich

Sorry what is the purpose of this file ? 2008/6/12 Norbert Hartl <norbert(a)hartl.name>: > On Wed, 2008-06-11 at 21:22 -0400, Victor Rodriguez wrote: >> On Wed, Jun 11, 2008 at 7:54 PM, Victor Rodriguez <victorr(a)gmail.com> wrote: >> > On Wed, Jun 11, 2008 at 3:51 PM, StÃ©phane Ducasse >> > <stephane.ducasse(a)inria.fr> wrote: >> > [snip] >> >> Is is politically really important that we use the inria infrastructure. >> >> It will help us building Smalltalk presence inside INRIA. >> >> So at then end we will not use the forge but only the file because we need >> >> these counters >> >> at that place :) >> > >> > Fair enough. I have disabled the "Downloads" tab in googlecode. >> >> I thought things better and just turned the "Downloads" tab into a >> wiki page to redirect people to the right place. >> >> BTW, PharoReady.cs is not available. Stephane, could you please add it? >> > I added it. I've put it into the svn and linked it from there. I don't > think the initial cs has be add inria. > > Norbert > >> Thanks, >> >> Victor. >> >> >> > VÃctor. >> > >> >>> I will volunteer again and move all the existing files over. (As a >> >>> matter of fact, I had been thinking of moving the files then proposing >> >>> the change, but I just haven't had a chance to do it.) >> >> >> >> Please don't there are issues more complex under the surface but this is not >> >> linked with pharo by itself. >> >> >> >>> >> >>> >> >>> Victor. >> >>> >> >>> >> >>>> On Jun 11, 2008, at 1:39 PM, Oscar Nierstrasz wrote: >> >>>> >> >>>>> >> >>>>> Ah, I thought it *was* a pharo-dev image -- it was listed under >> >>>>> "pharo-dev" on the downloads page. >> >>>>> >> >>>>> http://gforge.inria.fr/frs/?group_id=1299 >> >>>>> >> >>>>> - on >> >>>>> >> >>>>> On Jun 11, 2008, at 11:12, Damien Cassou wrote: >> >>>>> >> >>>>>> On Wed, Jun 11, 2008 at 9:56 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> >> >>>>>> wrote: >> >>>>>>> >> >>>>>>> Great! >> >>>>>>> >> >>>>>>> Just noticed two things: >> >>>>>>> >> >>>>>>> - Test Runner is missing from the Tools flap -- shouldn't it be there? >> >>>>>> >> >>>>>> >> >>>>>> I think Pharo should not care about such things. Just use pharo-dev if >> >>>>>> you want a prepared pharo image for developers. >> >>>>>> >> >>>>>> -- >> >>>>>> Damien Cassou >> >>>>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> >>>>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> >>>>>> >> >>>>>> _______________________________________________ >> >>>>>> 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 >> >>> >> >> >> >> >> >> _______________________________________________ >> >> 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 > -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 12, 2008

Re: [Pharo-project] Pharo, squeak and the tickets

by Serge Stinckwich

2008/6/12 Victor Rodriguez <victorr(a)gmail.com>: > On Wed, Jun 11, 2008 at 5:49 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > [snip] >> What would you prefer? >> >> 1. Opening issues where they belong first and let "the others" >> harvest what they think they need? >> 2. Playing back the issues to bugs.squeak.org if we find a bug >> that belongs also to squeak and bring them back by harvesting? > > This is what I propose: > > * If an issue applies to Squeak, file a report on Mantis. Yes we could be nice with Squeak ;-) >> How do we want to harvest fixes from other places? >> >> 1. Having a wiki page where issues found are written down? >> 2. Opening tickets on the google tracker for this? This would >> be "to harvest" tickets. > > * File an issue for everything we want to do in Pharo in the google > tracker, *including* for "harvesting" fixes in other projects. > > Thus, I would still file an issue on the google tracker for Mantis > reports. Such issues should probably follow a template, and have a > label that indicates their origin (in addition to the description). > > As a matter of fact, I think we should file an issue for every fix > listed in the wiki pages in ThreeDotTenFixes, ThreeDotTenDotOneFixes, > etc.. This way, people can assign to themselves a given fix, and we > can more easily keep a handle on things. > > The issue tracker should be the *one* place where you can find what > nees to be done. I agree with this plan. > BTW, this leads to something else I wanted to bring up. Currently, > "harvest" means two things: 1) Put in Pharo a fix available in Squeak > (or Croquet, etc..); and 2) Move a package from the PharoInbox into > the Pharo update stream. Could we come up with a different name for > 2? Something along the lines of 'integrate', 'validate', 'process', > etc.. "Stephane is processing fix X in the PharoInbox". > Yes and after the vocabulary is fixed, can we document this vocabulary and the harvesting process in the Wiki. I think we need something like a workflow. -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 12, 2008

Re: [Pharo-project] Behaviour>>hash is missing!

by Marcus Denker

On 11.06.2008, at 18:03, Adrian Lienhard wrote: > IIRC Marcus introduced Behavior>>hash in 3.9 and later realized that > this is not a good idea. The reason is that names of behaviors are > not constant because when a class is deleted its name is changed to > AnAbsolete..., which makes the name not suitable for hashing. > Yes, that was the reason. > Looking through ScriptLoader, #update10020 is where Behavior>>hash > is removed again. Unfortunately the changes log is a bit unspecific > as it mentions only: "changes from Reflectivity"... > I will try to be more specific next time... > Cheers, > Adrian > > On Jun 10, 2008, at 22:54 , Oscar Nierstrasz wrote: > >> >> What was his fix? >> >> How can I tell what was changed? >> >> Is Behaviour>>hash missing in your image too? I don't trust >> anything anymore. >> >> - on >> >> On Jun 10, 2008, at 10:13 PM, StÃ©phane Ducasse wrote: >> >>> Marcus should have a look since this is fix he reverted. >>> >>> Stef >>> >>> On Jun 10, 2008, at 10:04 PM, Oscar Nierstrasz wrote: >>> >>>> >>>> These tests are fine in Squeak 3.9 too. >>>> >>>> Further investigation reveals that Behaviour>>hash is missing in >>>> Pharo! >>>> >>>> So hash reverts to Object>>hash, which sends Object>>identityHash. >>>> >>>> In Pharo: >>>> >>>> Array hash --> 2455 >>>> Object identityHash --> 2274 >>>> >>>> In Squeak: >>>> >>>> Array hash --> 259007228 >>>> Object identityHash --> 2274 >>>> >>>> Looks like someone removed >>>> >>>> Behaviour>>hash >>>> ^ self name hash >>>> >>>> - on >>>> >>>> On Jun 10, 2008, at 9:43 PM, StÃ©phane Ducasse wrote: >>>> >>>>> Excellent! >>>>> may be this is the hash of class that changed. Marcus >>>>> retrochanged the hash behavior that we harvested in 3.9. >>>>> And may be in 3.10 they changed class hash too. >>>>> >>>>> Now I do not know if in 3.9 these tests were broken. >>>>> >>>>> Stef >>>>> >>>>> On Jun 10, 2008, at 9:32 PM, Oscar Nierstrasz wrote: >>>>> >>>>>> >>>>>> OK, I investigated more deeply. >>>>>> >>>>>> It appears that SequenceableCollection>>hash behaves >>>>>> differently in Pharo and Squeak 3.10. >>>>>> >>>>>> Squeak: >>>>>> >>>>>> #(1) hash --> 22516953 >>>>>> >>>>>> Pharo: >>>>>> >>>>>> #(1) hash --> 61541560 >>>>>> >>>>>> Since DateAndTime>>hash is ultimately implemented in terms of >>>>>> Array>>hash (inherited from SequenceableCollection), this test >>>>>> fails. >>>>>> >>>>>> Not yet sure why these two behave differently ... >>>>>> >>>>>> Already the first line (self species hash) is different: >>>>>> >>>>>> Squeak: >>>>>> >>>>>> Array hash --> 259007228 >>>>>> >>>>>> Pharo: >>>>>> >>>>>> Array hash --> 2455 >>>>>> >>>>>> - on >>>>>> >>>>>> On Jun 10, 2008, at 6:34 PM, StÃ©phane Ducasse wrote: >>>>>> >>>>>>> We checked with lukas what is strange is that the same tests >>>>>>> are green in 3.10. >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> On Jun 10, 2008, at 3:48 PM, Oscar Nierstrasz wrote: >>>>>>> >>>>>>>> >>>>>>>> I have posted some patches to the inbox to make the Kernel >>>>>>>> Number tests run, and in the Issues page I propose to delete >>>>>>>> a bunch of nonsensical testHash tests. With these changes >>>>>>>> the Kernel tests should all be green. >>>>>>>> >>>>>>>> - on >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

June 12, 2008

Re: [Pharo-project] Behaviour>>hash is missing!

by Marcus Denker

On 11.06.2008, at 19:11, StÃ©phane Ducasse wrote: > Yes I have the impression that this would be a good things to do > because > they do not have add that much important information. > > Yes, that is my impression too. > On Jun 11, 2008, at 6:11 PM, Oscar Nierstrasz wrote: > >> >> OK, so that is why all these silly testHash tests are broken. They >> depend on Behaviour>>#hash to return a specific hash value. I >> suggest trashing them as the tests are not robust. >> >> - on >> >> >> On Jun 11, 2008, at 6:03 PM, Adrian Lienhard wrote: >> >>> IIRC Marcus introduced Behavior>>hash in 3.9 and later realized >>> that this is not a good idea. The reason is that names of >>> behaviors are not constant because when a class is deleted its >>> name is changed to AnAbsolete..., which makes the name not >>> suitable for hashing. >>> >>> Looking through ScriptLoader, #update10020 is where Behavior>>hash >>> is removed again. Unfortunately the changes log is a bit >>> unspecific as it mentions only: "changes from Reflectivity"... >>> >>> Cheers, >>> Adrian >>> >>> On Jun 10, 2008, at 22:54 , Oscar Nierstrasz wrote: >>> >>>> >>>> What was his fix? >>>> >>>> How can I tell what was changed? >>>> >>>> Is Behaviour>>hash missing in your image too? I don't trust >>>> anything anymore. >>>> >>>> - on >>>> >>>> On Jun 10, 2008, at 10:13 PM, StÃ©phane Ducasse wrote: >>>> >>>>> Marcus should have a look since this is fix he reverted. >>>>> >>>>> Stef >>>>> >>>>> On Jun 10, 2008, at 10:04 PM, Oscar Nierstrasz wrote: >>>>> >>>>>> >>>>>> These tests are fine in Squeak 3.9 too. >>>>>> >>>>>> Further investigation reveals that Behaviour>>hash is missing >>>>>> in Pharo! >>>>>> >>>>>> So hash reverts to Object>>hash, which sends >>>>>> Object>>identityHash. >>>>>> >>>>>> In Pharo: >>>>>> >>>>>> Array hash --> 2455 >>>>>> Object identityHash --> 2274 >>>>>> >>>>>> In Squeak: >>>>>> >>>>>> Array hash --> 259007228 >>>>>> Object identityHash --> 2274 >>>>>> >>>>>> Looks like someone removed >>>>>> >>>>>> Behaviour>>hash >>>>>> ^ self name hash >>>>>> >>>>>> - on >>>>>> >>>>>> On Jun 10, 2008, at 9:43 PM, StÃ©phane Ducasse wrote: >>>>>> >>>>>>> Excellent! >>>>>>> may be this is the hash of class that changed. Marcus >>>>>>> retrochanged the hash behavior that we harvested in 3.9. >>>>>>> And may be in 3.10 they changed class hash too. >>>>>>> >>>>>>> Now I do not know if in 3.9 these tests were broken. >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> On Jun 10, 2008, at 9:32 PM, Oscar Nierstrasz wrote: >>>>>>> >>>>>>>> >>>>>>>> OK, I investigated more deeply. >>>>>>>> >>>>>>>> It appears that SequenceableCollection>>hash behaves >>>>>>>> differently in Pharo and Squeak 3.10. >>>>>>>> >>>>>>>> Squeak: >>>>>>>> >>>>>>>> #(1) hash --> 22516953 >>>>>>>> >>>>>>>> Pharo: >>>>>>>> >>>>>>>> #(1) hash --> 61541560 >>>>>>>> >>>>>>>> Since DateAndTime>>hash is ultimately implemented in terms of >>>>>>>> Array>>hash (inherited from SequenceableCollection), this >>>>>>>> test fails. >>>>>>>> >>>>>>>> Not yet sure why these two behave differently ... >>>>>>>> >>>>>>>> Already the first line (self species hash) is different: >>>>>>>> >>>>>>>> Squeak: >>>>>>>> >>>>>>>> Array hash --> 259007228 >>>>>>>> >>>>>>>> Pharo: >>>>>>>> >>>>>>>> Array hash --> 2455 >>>>>>>> >>>>>>>> - on >>>>>>>> >>>>>>>> On Jun 10, 2008, at 6:34 PM, StÃ©phane Ducasse wrote: >>>>>>>> >>>>>>>>> We checked with lukas what is strange is that the same tests >>>>>>>>> are green in 3.10. >>>>>>>>> >>>>>>>>> Stef >>>>>>>>> >>>>>>>>> On Jun 10, 2008, at 3:48 PM, Oscar Nierstrasz wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> I have posted some patches to the inbox to make the Kernel >>>>>>>>>> Number tests run, and in the Issues page I propose to >>>>>>>>>> delete a bunch of nonsensical testHash tests. With these >>>>>>>>>> changes the Kernel tests should all be green. >>>>>>>>>> >>>>>>>>>> - on >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>> >> >> >> _______________________________________________ >> 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 Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Norbert Hartl

On Wed, 2008-06-11 at 21:22 -0400, Victor Rodriguez wrote: > On Wed, Jun 11, 2008 at 7:54 PM, Victor Rodriguez <victorr(a)gmail.com> wrote: > > On Wed, Jun 11, 2008 at 3:51 PM, StÃ©phane Ducasse > > <stephane.ducasse(a)inria.fr> wrote: > > [snip] > >> Is is politically really important that we use the inria infrastructure. > >> It will help us building Smalltalk presence inside INRIA. > >> So at then end we will not use the forge but only the file because we need > >> these counters > >> at that place :) > > > > Fair enough. I have disabled the "Downloads" tab in googlecode. > > I thought things better and just turned the "Downloads" tab into a > wiki page to redirect people to the right place. > > BTW, PharoReady.cs is not available. Stephane, could you please add it? > I added it. I've put it into the svn and linked it from there. I don't think the initial cs has be add inria. Norbert > Thanks, > > Victor. > > > > VÃctor. > > > >>> I will volunteer again and move all the existing files over. (As a > >>> matter of fact, I had been thinking of moving the files then proposing > >>> the change, but I just haven't had a chance to do it.) > >> > >> Please don't there are issues more complex under the surface but this is not > >> linked with pharo by itself. > >> > >>> > >>> > >>> Victor. > >>> > >>> > >>>> On Jun 11, 2008, at 1:39 PM, Oscar Nierstrasz wrote: > >>>> > >>>>> > >>>>> Ah, I thought it *was* a pharo-dev image -- it was listed under > >>>>> "pharo-dev" on the downloads page. > >>>>> > >>>>> http://gforge.inria.fr/frs/?group_id=1299 > >>>>> > >>>>> - on > >>>>> > >>>>> On Jun 11, 2008, at 11:12, Damien Cassou wrote: > >>>>> > >>>>>> On Wed, Jun 11, 2008 at 9:56 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> > >>>>>> wrote: > >>>>>>> > >>>>>>> Great! > >>>>>>> > >>>>>>> Just noticed two things: > >>>>>>> > >>>>>>> - Test Runner is missing from the Tools flap -- shouldn't it be there? > >>>>>> > >>>>>> > >>>>>> I think Pharo should not care about such things. Just use pharo-dev if > >>>>>> you want a prepared pharo image for developers. > >>>>>> > >>>>>> -- > >>>>>> Damien Cassou > >>>>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > >>>>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > >>>>>> > >>>>>> _______________________________________________ > >>>>>> 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 > >>> > >> > >> > >> _______________________________________________ > >> 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

June 12, 2008