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

Re: [Pharo-project] [Fwd: [squeak-dev] Re: Bug in object finalization?]

by Adrian Lienhard

Hi Norbert, We do this kind of scripts in the ScriptLoader. Just let me know when you published your slice and I will prepare the ScriptLoader update script which Stef can then push into the update stream. Adrian On Jun 18, 2008, at 19:30 , Norbert Hartl wrote: > So, > > now I'm all for fixing it and ressurect the test case. > I'll upload something to PharoInbox. Afterwards it needs > to be reinitialized. What is the preferred way of having > doits in the update stream? > > Anyway I uploaded SLICE-WeakRegistryAndFinalizerTestFix > to PharoInbox. > > afterwards a > > WeakRegistry default initialize: WeakRegistry default size > > will be necessary. > > Norbert > > From: Andreas Raab <andreas.raab(a)gmx.de> > Date: June 18, 2008 7:02:11 PM GMT+02:00 > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > Subject: [squeak-dev] Re: Bug in object finalization? > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > > > Norbert Hartl wrote: >> On Wed, 2008-06-18 at 09:22 -0700, Andreas Raab wrote: >>> Norbert Hartl wrote: >>>> There was a test in 3.9 testing this (it failed). In 3.10 >>>> the test got removed but I think it is a bug. >>>> >>>> What do you think? >>> The test itself is buggy (see http://bugs.squeak.org/view.php?id=6347) >>> but once you fix the test it illustrates a problem in >>> WeakRegistry which needs to use a WeakIdentityKeyDictionary >>> instead of a WeakKeyDictionary. >>> >> Ok, what I said. Do you see an harmful side effects by exchanging >> the dictionary? > > No - we've fixed this a long time ago in our code base. > > Cheers, > - Andreas > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 18, 2008

[Pharo-project] [Fwd: [squeak-dev] Re: Bug in object finalization?]

by Norbert Hartl

So, now I'm all for fixing it and ressurect the test case. I'll upload something to PharoInbox. Afterwards it needs to be reinitialized. What is the preferred way of having doits in the update stream? Anyway I uploaded SLICE-WeakRegistryAndFinalizerTestFix to PharoInbox. afterwards a WeakRegistry default initialize: WeakRegistry default size will be necessary. Norbert

June 18, 2008

Re: [Pharo-project] Logos

by Norbert Hartl

On Wed, 2008-06-18 at 12:52 -0400, Victor Rodriguez wrote: > On Wed, Jun 18, 2008 at 12:34 PM, Michael Rueger <m.rueger(a)acm.org> wrote: > > Victor Rodriguez wrote: > >> > >> On Wed, Jun 18, 2008 at 8:05 AM, Damien Pollet <damien.pollet(a)gmail.com> > >> wrote: > >> ... > >>> > >>> Maybe make the white stripes thinner than the dark ones ? > >>> Also without the circle it misses some kind of base, maybe a wave that > >>> would suggest the curvature of the circle if it were there ? > >>> > >>> The red eye looks a little Terminator-esque, somewhat menacing :-) > >> > >> I think you mean Tolkien-esque, the eye of Sauron anyone? :-) > > > > Yes, that was the first thing I noticed. Maybe making it more a > > yellow/orange tone would help? > > I thought about yellow too, but didn't say anything since yellow might > become hard to see in lgiht backgrounds. > Which is exactly as it is. A light background could be called day light. As the light is hard to see when it is day they switch it off :) That is the main problem I think. In the day light you can see the lighthouse building but no light. At night there is only a shape of a building but light. So it is difficult to show both at the same time. Norbert > Indeed, I shouldn't say anything at all, since I don't really know > about graphical design. :-) Which is why I really appreciate Samuel > Morello's work, thanks! > > Victor. > > > Michael > > > > _______________________________________________ > > 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 18, 2008

Re: [Pharo-project] Logos

by Victor Rodriguez

On Wed, Jun 18, 2008 at 12:34 PM, Michael Rueger <m.rueger(a)acm.org> wrote: > Victor Rodriguez wrote: >> >> On Wed, Jun 18, 2008 at 8:05 AM, Damien Pollet <damien.pollet(a)gmail.com> >> wrote: >> ... >>> >>> Maybe make the white stripes thinner than the dark ones ? >>> Also without the circle it misses some kind of base, maybe a wave that >>> would suggest the curvature of the circle if it were there ? >>> >>> The red eye looks a little Terminator-esque, somewhat menacing :-) >> >> I think you mean Tolkien-esque, the eye of Sauron anyone? :-) > > Yes, that was the first thing I noticed. Maybe making it more a > yellow/orange tone would help? I thought about yellow too, but didn't say anything since yellow might become hard to see in lgiht backgrounds. Indeed, I shouldn't say anything at all, since I don't really know about graphical design. :-) Which is why I really appreciate Samuel Morello's work, thanks! Victor. > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 18, 2008

Re: [Pharo-project] Logos

by Michael Rueger

Victor Rodriguez wrote: > On Wed, Jun 18, 2008 at 8:05 AM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > ... >> Maybe make the white stripes thinner than the dark ones ? >> Also without the circle it misses some kind of base, maybe a wave that >> would suggest the curvature of the circle if it were there ? >> >> The red eye looks a little Terminator-esque, somewhat menacing :-) > > I think you mean Tolkien-esque, the eye of Sauron anyone? :-) Yes, that was the first thing I noticed. Maybe making it more a yellow/orange tone would help? Michael

June 18, 2008

[Pharo-project] Fwd: [squeak-dev] to:do: optimization is wrong when the block modifies the limit

by StÃ©phane Ducasse

Begin forwarded message: > From: nicolas cellier <ncellier(a)ifrance.com> > Date: June 13, 2008 3:28:25 AM CEDT > To: squeak-dev(a)lists.squeakfoundation.org > Subject: [squeak-dev] to:do: optimization is wrong when the block > modifies the limit > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > > While browsing #to:do: optimization implementation i noticed this: > > | n | > n := 2. > 1 to: n do: [:i | (n := n+1)>10 ifTrue: [self halt: 'Should I get > here?']]. > ^n > > When you think in term of message send, well NO, YOU SHOULD NOT GET > HERE. > > Optimization is such a subtle thing that: > > | n | > 1 to: (n := 2) do: [:i | n := n+1. n>10 ifTrue: [self halt: 'You > won''t get there']]. > ^n > > Ha Ha, it's really fun! > Of course, if one corrects this bug, there is a pending Decompiler > issue: > > testDecompileToDoWithMovingLimit > | n i | > n := 4. > i := 1. > [i <= n] whileTrue: [ > n := n - 1. > i := i + 1]. > > would decompile into: > | n | > n := 4. > 1 > to: n > do: [:i | n := n - 1] > > This is worth a http://bugs.squeak.org/view.php?id=7093 > Ah i wonder what would a NewCompiler do to to:do: > > Nicolas > > >

June 18, 2008

Re: [Pharo-project] Logos

by StÃ©phane Ducasse

I'm eager to see that. I like the thrash style of geeky surfers :) Stef On Jun 18, 2008, at 3:02 PM, Samuel MORELLO wrote: > Hi Damien, > > I have made some tests with the O at the same size , and it was not > conclusive. > The circle is finer than the text weight and at the same size, it > loose consistency. > > Regarding the mail of Victor, i will to try to simplify the top of the > lighthouse and give a less frightening look to the light ;-) > > Samuel > > > On Wed, Jun 18, 2008 at 1:39 PM, Damien Cassou <damien.cassou(a)gmail.com > > wrote: >> On Wed, Jun 18, 2008 at 1:37 PM, Adrian Lienhard <adi(a)netstyle.ch> >> wrote: >>> I suggest to show the logo to people that do not know the name >>> already. Will >>> they not read it as "Phar" without "o"? I fear its not obvious >>> that the >>> large circle is part of the name. >> >> I think it could be better to make the $o the same size of the text. >> >> >> -- >> 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 >> > > > > -- > Samuel > +33 (0)6 20 65 22 99 > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 18, 2008

Re: [Pharo-project] Logos

by Samuel MORELLO

Hi Damien, I have made some tests with the O at the same size , and it was not conclusive. The circle is finer than the text weight and at the same size, it loose consistency. Regarding the mail of Victor, i will to try to simplify the top of the lighthouse and give a less frightening look to the light ;-) Samuel On Wed, Jun 18, 2008 at 1:39 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Wed, Jun 18, 2008 at 1:37 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: >> I suggest to show the logo to people that do not know the name already. Will >> they not read it as "Phar" without "o"? I fear its not obvious that the >> large circle is part of the name. > > I think it could be better to make the $o the same size of the text. > > > -- > 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 > -- Samuel +33 (0)6 20 65 22 99

June 18, 2008

Re: [Pharo-project] Logos

by Victor Rodriguez

On Wed, Jun 18, 2008 at 8:05 AM, Damien Pollet <damien.pollet(a)gmail.com> wrote: ... > > Maybe make the white stripes thinner than the dark ones ? > Also without the circle it misses some kind of base, maybe a wave that > would suggest the curvature of the circle if it were there ? > > The red eye looks a little Terminator-esque, somewhat menacing :-) I think you mean Tolkien-esque, the eye of Sauron anyone? :-) I think the logos are looking great, and I have zero artistic talent, but I will venture a suggestion nonetheless: what about simplifying the top of the lighthouse? If the shape was simpler (perhaps like an "n") and the light bigger, then perhaps the logo would be more distinct even at small sizes. Best Regards, Victor Rodriguez. >> 2008/6/18 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> >>> >>> Begin forwarded message: >>> >>>> From: Samuel MORELLO <samuel.morello(a)ouvanous.com> >>>> Date: June 18, 2008 10:55:19 AM CEDT >>>> To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> Subject: Re: [OUVANOUS] Re: Nouvelle version >>>> >>>> les voici ;-) >>>> >>>> Le 18 juin 08 Ã 10:39, StÃ©phane DUCASSE a Ã©crit : >>>> >>>>> --- Reply ABOVE THIS LINE to post a comment to the project --- >>>>> >>>>> Company: Smalltalk >>>>> Project: Pharo >>>>> Link: https://ouvanous.projectpath.com/C18821220 >>>>> >>>>> StÃ©phane DUCASSE said: >>>>> >>>>> ou cela :) >>>>> >>>>> >>>>> .......................................................................... >>>>> >>>>> Read the original message, view this comment, and download attachments >>>>> at: >>>>> https://ouvanous.projectpath.com/C18821220 >>>>> >>>>> You can always check the Overview for the latest project activity: >>>>> https://ouvanous.projectpath.com/projects/1873269/project/log >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

June 18, 2008

Re: [Pharo-project] Logos

by Damien Pollet

On Wed, Jun 18, 2008 at 1:02 PM, Serge Stinckwich <serge.stinckwich(a)doesnotunderstand.org> wrote: > When the icon is small, the lighthouse is not easily recognizable. Maybe make the white stripes thinner than the dark ones ? Also without the circle it misses some kind of base, maybe a wave that would suggest the curvature of the circle if it were there ? The red eye looks a little Terminator-esque, somewhat menacing :-) > 2008/6/18 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >> >> Begin forwarded message: >> >>> From: Samuel MORELLO <samuel.morello(a)ouvanous.com> >>> Date: June 18, 2008 10:55:19 AM CEDT >>> To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> Subject: Re: [OUVANOUS] Re: Nouvelle version >>> >>> les voici ;-) >>> >>> Le 18 juin 08 Ã 10:39, StÃ©phane DUCASSE a Ã©crit : >>> >>>> --- Reply ABOVE THIS LINE to post a comment to the project --- >>>> >>>> Company: Smalltalk >>>> Project: Pharo >>>> Link: https://ouvanous.projectpath.com/C18821220 >>>> >>>> StÃ©phane DUCASSE said: >>>> >>>> ou cela :) >>>> >>>> >>>> .......................................................................... >>>> >>>> Read the original message, view this comment, and download attachments >>>> at: >>>> https://ouvanous.projectpath.com/C18821220 >>>> >>>> You can always check the Overview for the latest project activity: >>>> https://ouvanous.projectpath.com/projects/1873269/project/log >> >> >> >> _______________________________________________ >> 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 > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

June 18, 2008

Re: [Pharo-project] Logos

by Damien Cassou

On Wed, Jun 18, 2008 at 1:39 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Wed, Jun 18, 2008 at 1:37 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: >> I suggest to show the logo to people that do not know the name already. Will >> they not read it as "Phar" without "o"? I fear its not obvious that the >> large circle is part of the name. > > I think it could be better to make the $o the same size of the text. I've just asked my colleague and he reads "pharo" so it is ok. -- 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 18, 2008

Re: [Pharo-project] Logos

by Damien Cassou

On Wed, Jun 18, 2008 at 1:37 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > I suggest to show the logo to people that do not know the name already. Will > they not read it as "Phar" without "o"? I fear its not obvious that the > large circle is part of the name. I think it could be better to make the $o the same size of the text. -- 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 18, 2008

Re: [Pharo-project] Logos

by Adrian Lienhard

I suggest to show the logo to people that do not know the name already. Will they not read it as "Phar" without "o"? I fear its not obvious that the large circle is part of the name. Adrian On Jun 18, 2008, at 11:33 , StÃ©phane Ducasse wrote: > > > Begin forwarded message: > >> From: Samuel MORELLO <samuel.morello(a)ouvanous.com> >> Date: June 18, 2008 10:55:19 AM CEDT >> To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> Subject: Re: [OUVANOUS] Re: Nouvelle version >> >> les voici ;-) >> >> Le 18 juin 08 Ã 10:39, StÃ©phane DUCASSE a Ã©crit : >> >>> --- Reply ABOVE THIS LINE to post a comment to the project --- >>> >>> Company: Smalltalk >>> Project: Pharo >>> Link: https://ouvanous.projectpath.com/C18821220 >>> >>> StÃ©phane DUCASSE said: >>> >>> ou cela :) >>> >>> .......................................................................... >>> >>> Read the original message, view this comment, and download >>> attachments at: >>> https://ouvanous.projectpath.com/C18821220 >>> >>> You can always check the Overview for the latest project activity: >>> https://ouvanous.projectpath.com/projects/1873269/project/log > <pharo-0.7.5.pdf><pharo-0.7.7.pdf> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 18, 2008

Re: [Pharo-project] Logos

by Samuel MORELLO

Hello, For little things, you can may be only use the lighthouse without the text and the circle. It take less size and you can make it larger Cheers, Samuel Le 18 juin 08 Ã 13:02, Serge Stinckwich a Ã©crit : > When the icon is small, the lighthouse is not easily recognizable. > > 2008/6/18 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >> >> Begin forwarded message: >> >>> From: Samuel MORELLO <samuel.morello(a)ouvanous.com> >>> Date: June 18, 2008 10:55:19 AM CEDT >>> To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> Subject: Re: [OUVANOUS] Re: Nouvelle version >>> >>> les voici ;-) >>> >>> Le 18 juin 08 Ã 10:39, StÃ©phane DUCASSE a Ã©crit : >>> >>>> --- Reply ABOVE THIS LINE to post a comment to the project --- >>>> >>>> Company: Smalltalk >>>> Project: Pharo >>>> Link: https://ouvanous.projectpath.com/C18821220 >>>> >>>> StÃ©phane DUCASSE said: >>>> >>>> ou cela :) >>>> >>>> >>>> .......................................................................... >>>> >>>> Read the original message, view this comment, and download >>>> attachments >>>> at: >>>> https://ouvanous.projectpath.com/C18821220 >>>> >>>> You can always check the Overview for the latest project activity: >>>> https://ouvanous.projectpath.com/projects/1873269/project/log >> >> >> >> _______________________________________________ >> 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 18, 2008

Re: [Pharo-project] Logos

by Serge Stinckwich

When the icon is small, the lighthouse is not easily recognizable. 2008/6/18 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > > Begin forwarded message: > >> From: Samuel MORELLO <samuel.morello(a)ouvanous.com> >> Date: June 18, 2008 10:55:19 AM CEDT >> To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> Subject: Re: [OUVANOUS] Re: Nouvelle version >> >> les voici ;-) >> >> Le 18 juin 08 Ã 10:39, StÃ©phane DUCASSE a Ã©crit : >> >>> --- Reply ABOVE THIS LINE to post a comment to the project --- >>> >>> Company: Smalltalk >>> Project: Pharo >>> Link: https://ouvanous.projectpath.com/C18821220 >>> >>> StÃ©phane DUCASSE said: >>> >>> ou cela :) >>> >>> >>> .......................................................................... >>> >>> Read the original message, view this comment, and download attachments >>> at: >>> https://ouvanous.projectpath.com/C18821220 >>> >>> You can always check the Overview for the latest project activity: >>> https://ouvanous.projectpath.com/projects/1873269/project/log > > > > _______________________________________________ > 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 18, 2008

[Pharo-project] Logos

by StÃ©phane Ducasse

Begin forwarded message: > From: Samuel MORELLO <samuel.morello(a)ouvanous.com> > Date: June 18, 2008 10:55:19 AM CEDT > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: [OUVANOUS] Re: Nouvelle version > > les voici ;-) > > Le 18 juin 08 Ã 10:39, StÃ©phane DUCASSE a Ã©crit : > >> --- Reply ABOVE THIS LINE to post a comment to the project --- >> >> Company: Smalltalk >> Project: Pharo >> Link: https://ouvanous.projectpath.com/C18821220 >> >> StÃ©phane DUCASSE said: >> >> ou cela :) >> >> .......................................................................... >> >> Read the original message, view this comment, and download >> attachments at: >> https://ouvanous.projectpath.com/C18821220 >> >> You can always check the Overview for the latest project activity: >> https://ouvanous.projectpath.com/projects/1873269/project/log

June 18, 2008

Re: [Pharo-project] Missing PluggableTextController and PluggableTextView

by Damien Cassou

On Wed, Jun 18, 2008 at 9:32 AM, Alain Plantec <alain.plantec(a)free.fr> wrote: > On Tuesday 17 June 2008 14:43:29 Alain Plantec wrote: >> On Tuesday 17 June 2008 14:25:28 Damien Cassou wrote: >>> >> I've found another problem related to view instance variable + OB. >> I will report it tonight. > Hi Damien and Andrew, > Controller 'view' instance variable has been removed. > In pharo-dev, Undeclared shows a 'view' key which is referenced from OBTextMorphEditor, > OBTextMorphEditorWithShout and TextMorphForShoutEditor. > I've attached 2 separated fixes (for OB and for shout). Are these fixes compatible with the new Shout (published yesterday)? Are these fixes compatible with Squeak? If both answers are yes, please commit your fix to OB directly to source.wiresong.ca/ob (no need for a password). And send the Shout fix to Andrew. 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 18, 2008

Re: [Pharo-project] Reintegration of StringSocket

by Damien Cassou

On Tue, Jun 17, 2008 at 3:41 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > I've just published a new version of Universes which includes > StringSocket and its super class ObjectSocket (renamed > StringSocketStream and ObjectSocketStream). I have also replaced > direct references to other Nebraska classes (CanvasEncoder and > NebraskaDebuger) to: > > Smalltalk at: #NebraskaDebugger ifPresent: [:debug | debug ...]. > > It seems to me these classes were only used to log things. Do you agree Lex? >From Lex who is not on the list: Â«Yes, that looks like a great change. Also, I like the general strategy of splitting StringSocket from Nebraska. StringSocket was always meant to be usable by itself.Â» -- 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 18, 2008

Re: [Pharo-project] Missing PluggableTextController and PluggableTextView

by Alain Plantec

On Tuesday 17 June 2008 14:43:29 Alain Plantec wrote: > On Tuesday 17 June 2008 14:25:28 Damien Cassou wrote: >> > I've found another problem related to view instance variable + OB. > I will report it tonight. Hi Damien and Andrew, Controller 'view' instance variable has been removed. In pharo-dev, Undeclared shows a 'view' key which is referenced from OBTextMorphEditor, OBTextMorphEditorWithShout and TextMorphForShoutEditor. I've attached 2 separated fixes (for OB and for shout). Cheers alain > > cheers > alain > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

June 18, 2008

Re: [Pharo-project] Re: Re: Re: MissingPluggableTextControllerandPluggableTextView

by StÃ©phane Ducasse

Excellent! Excellent! I like this feeling. Soon (more or less) we will be able to focus on the making of new things (versus the cleaning). Please note that I truly respect what was done (even if I can have really harsh statement), I'm not idiot and know that building is far more difficult than removing them. It would be good to think about a first release of pharo the milestone says: - tests green Stef On Jun 17, 2008, at 4:37 PM, Damien Cassou wrote: > On Tue, Jun 17, 2008 at 4:34 PM, Damien Cassou <damien.cassou(a)gmail.com > > wrote: >>> Unfortunately, I can't add it to Universes > > Done > > -- > 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 >

June 17, 2008

Re: [Pharo-project] Re: Missing PluggableTextController andPluggableTextView

by StÃ©phane Ducasse

this would be really cool :) Stef On Jun 17, 2008, at 2:37 PM, Andrew Tween wrote: > I'll take a look and see if I can create a Pharo compatible Shout, > > Andy > > > "Damien Cassou" <damien.cassou(a)gmail.com> wrote in message news:6ac749c10806170525r2da65fbr17a00ce24f0cd041@mail.gmail.com > ... > I've just update my image to 10041 and tried to generate a pharo-dev > from it. However, the process failed while trying to install Shout > because it depends on PluggableTextController and PluggableTextView > which are not in the image anymore. > > -- > 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 >

June 17, 2008

Re: [Pharo-project] New pharo-dev based on latest version

by StÃ©phane Ducasse

cooool On Jun 17, 2008, at 3:47 PM, Damien Cassou wrote: > I've just published a new pharo-dev version on: > http://code.google.com/p/pharo/wiki/Downloads?tm=2. It is based on > version 10041 which contains cleaning of MVC. > > -- > 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 >

June 17, 2008

Re: [Pharo-project] [ANN] MVC removal step two harvested

by StÃ©phane Ducasse

good that someone is chekcing, I was in a meeting. We should really define a process that should be run by me and after a machine automatically before updates :) Stef On Jun 17, 2008, at 2:23 PM, Norbert Hartl wrote: > On Tue, 2008-06-17 at 13:35 +0200, StÃ©phane Ducasse wrote: >> Hi all >> >> I harvested the changes proposed by alain for the removal of MVC. >> Please test pharo since it was a large change. >> > tests run as expected. There is one obsolete class left which > is referenced by MvcTextEditor. That sounds like it is to be > removed anyway ;) > > Otherwise a > > AppRegistry removeObsolete > > will do. > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 17, 2008

Re: [Pharo-project] ObjectFinalizerTests understanding problems

by Norbert Hartl

On Tue, 2008-06-17 at 16:16 +0200, Adrian Lienhard wrote: > Hi Norbert > > Since there was nobody else replying on the Squeak-dev mailing list, > what do we do? At least, my "fix" is not satisfying as it just works > around the actual problem. But then I don't feel like diving into the > finalization mechanism to fix it. I don't think its critical. I think > we should just remove the test (like they did in 3.10). > I agree. At the moment there is only one method that calls it and that method itself does not have a sender. The only other solution I can see is to change Object>>finalizationRegistry and I wouldn't dare :) +1 Norbert > Cheers, > Adrian > > On Jun 14, 2008, at 12:23 , Norbert Hartl wrote: > > > On Sat, 2008-06-14 at 12:18 +0200, StÃ©phane Ducasse wrote: > >> No idea :) > >> > >> may be ask in the squeak mailing-list? > >> > > You are right :) > > > > Norbert > >> On Jun 14, 2008, at 12:03 PM, Norbert Hartl wrote: > >> > >>> Before I recognized that Adrian fixed the > >>> > >>> ObjectFinalizerTests>>testFinalizationOfEquals > >>> > >>> I gave it try myself. I came to the same conclusion as Adrian > >>> how to fix. But now after knowing how it works I do not know > >>> why the test succeeds :) > >>> > >>> The test uses > >>> > >>> 1 to: 5 do: [:n | o := Object new. bag add: n. o toFinalizeSend: > >>> #remove: to: bag with: n]. > >>> 1 to: 5 do: [:n | o := Object new. bag add: n. o toFinalizeSend: > >>> #remove: to: bag with: n]. > >>> > >>> My problem is that toFinalizeSend:to:with adds an Objectfinalizer > >>> to the finalizationRegistry of the instance. But > >>> > >>> Object>>finalizationRegistry > >>> "Answer the finalization registry associated with the receiver." > >>> ^WeakRegistry default > >>> > >>> returns a global object which is WeakKeyDictionary. And > >>> > >>> | d | > >>> d := WeakKeyDictionary new. > >>> d at: (1 asString copy) put: $a. > >>> d at: (1 asString copy) put: $b. > >>> d size > >>> > >>> prints 1. To me that would exchange every entry from the first > >>> run by the second run (because the objects are equal). > >>> > >>> So I would assume that if there does not happen a run of the > >>> garbagecollector between the two loops the objects of the first > >>> loop should be still contained in the bag. But the test is named > >>> finalizationOfEquals so I have to assume: self doesNotUnderstand > >>> > >>> Can someone explain it to me, please? > >>> > >>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 17, 2008

Re: [Pharo-project] Re: Re: Re: MissingPluggableTextControllerandPluggableTextView

by Damien Cassou

On Tue, Jun 17, 2008 at 4:34 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: >> Unfortunately, I can't add it to Universes Done -- 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 17, 2008

Re: [Pharo-project] Re: Re: Re: MissingPluggableTextControllerandPluggableTextView

by Damien Cassou

On Tue, Jun 17, 2008 at 4:03 PM, Andrew Tween <amtween(a)hotmail.com> wrote: > I have created the http://www.squeaksource.com/shout/Shout.3.15-tween.71.mcz > package which no longer contains MVC stuff. Thank you very much > Unfortunately, I can't add it to Universes - the Universe editor tells me it > is owned by someone else :( It's probably me :-). > I agree with your suggestion of not supporting MVC in squeak-dev images > anymore. Cool -- 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 17, 2008

Re: [Pharo-project] ObjectFinalizerTests understanding problems

by Adrian Lienhard

Hi Norbert Since there was nobody else replying on the Squeak-dev mailing list, what do we do? At least, my "fix" is not satisfying as it just works around the actual problem. But then I don't feel like diving into the finalization mechanism to fix it. I don't think its critical. I think we should just remove the test (like they did in 3.10). Cheers, Adrian On Jun 14, 2008, at 12:23 , Norbert Hartl wrote: > On Sat, 2008-06-14 at 12:18 +0200, StÃ©phane Ducasse wrote: >> No idea :) >> >> may be ask in the squeak mailing-list? >> > You are right :) > > Norbert >> On Jun 14, 2008, at 12:03 PM, Norbert Hartl wrote: >> >>> Before I recognized that Adrian fixed the >>> >>> ObjectFinalizerTests>>testFinalizationOfEquals >>> >>> I gave it try myself. I came to the same conclusion as Adrian >>> how to fix. But now after knowing how it works I do not know >>> why the test succeeds :) >>> >>> The test uses >>> >>> 1 to: 5 do: [:n | o := Object new. bag add: n. o toFinalizeSend: >>> #remove: to: bag with: n]. >>> 1 to: 5 do: [:n | o := Object new. bag add: n. o toFinalizeSend: >>> #remove: to: bag with: n]. >>> >>> My problem is that toFinalizeSend:to:with adds an Objectfinalizer >>> to the finalizationRegistry of the instance. But >>> >>> Object>>finalizationRegistry >>> "Answer the finalization registry associated with the receiver." >>> ^WeakRegistry default >>> >>> returns a global object which is WeakKeyDictionary. And >>> >>> | d | >>> d := WeakKeyDictionary new. >>> d at: (1 asString copy) put: $a. >>> d at: (1 asString copy) put: $b. >>> d size >>> >>> prints 1. To me that would exchange every entry from the first >>> run by the second run (because the objects are equal). >>> >>> So I would assume that if there does not happen a run of the >>> garbagecollector between the two loops the objects of the first >>> loop should be still contained in the bag. But the test is named >>> finalizationOfEquals so I have to assume: self doesNotUnderstand >>> >>> Can someone explain it to me, please? >>> >>> 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 17, 2008

[Pharo-project] Re: Re: Re: MissingPluggableTextControllerandPluggableTextView

by Andrew Tween

I have created the http://www.squeaksource.com/shout/Shout.3.15-tween.71.mcz package which no longer contains MVC stuff. Unfortunately, I can't add it to Universes - the Universe editor tells me it is owned by someone else :( I agree with your suggestion of not supporting MVC in squeak-dev images anymore. "Damien Cassou" <damien.cassou(a)gmail.com> wrote in message news:6ac749c10806170637t7343f960h7ccb2791b268bf3e@mail.gmail.com... On Tue, Jun 17, 2008 at 3:25 PM, Andrew Tween <amtween(a)hotmail.com> wrote: > > "Damien Cassou" <damien.cassou(a)gmail.com> > wrote in message > news:6ac749c10806170613p3edfb55h3fddcaf61fca4f0c@mail.gmail.com... > On Tue, Jun 17, 2008 at 2:37 PM, Andrew Tween > <amtween(a)hotmail.com> wrote: >> >> I'll take a look and see if I can create a Pharo compatible Shout, > >> Do you think it can be possible to have Shout compatible with both >> Pharo and Squeak at the same time? Otherwise, we will have to maintain >> a separate universe which will complicate my work a lot. > > I plan to remove MVC from Shout. > And create a separate, optional, ShoutMVC package that can be loaded after > loading the main Shout package. This is the best solution I think. > Will you be able to load ShoutMVC into Squeak images, but not load it into > Pharo? It is possible yes but no straightforward. The simplest solution is not to support MVC anymore in squeak-dev images. What do you think? > If not, then I can create a .sar installer which checks for the existance > of > MVC before loading ShoutMVC It is the simplest solution for me, but not for you :-). Do you think ShoutMVC could be of interest to anyone? -- 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 17, 2008

[Pharo-project] New pharo-dev based on latest version

by Damien Cassou

I've just published a new pharo-dev version on: http://code.google.com/p/pharo/wiki/Downloads?tm=2. It is based on version 10041 which contains cleaning of MVC. -- 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 17, 2008

Re: [Pharo-project] Reintegration of StringSocket

by Damien Cassou

On Sat, Jun 14, 2008 at 9:25 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Ok but what is the solution right now to make universe work? > Damien may be you should include StringSocket into the Universe package. > Because it is strange to rely on nebraska. I've just published a new version of Universes which includes StringSocket and its super class ObjectSocket (renamed StringSocketStream and ObjectSocketStream). I have also replaced direct references to other Nebraska classes (CanvasEncoder and NebraskaDebuger) to: Smalltalk at: #NebraskaDebugger ifPresent: [:debug | debug ...]. It seems to me these classes were only used to log things. Do you agree Lex? -- 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 17, 2008

Re: [Pharo-project] Re: Re: Missing PluggableTextControllerandPluggableTextView

by Damien Cassou

On Tue, Jun 17, 2008 at 3:25 PM, Andrew Tween <amtween(a)hotmail.com> wrote: > > "Damien Cassou" <damien.cassou(a)gmail.com> wrote in message > news:6ac749c10806170613p3edfb55h3fddcaf61fca4f0c@mail.gmail.com... > On Tue, Jun 17, 2008 at 2:37 PM, Andrew Tween <amtween(a)hotmail.com> wrote: >> >> I'll take a look and see if I can create a Pharo compatible Shout, > >> Do you think it can be possible to have Shout compatible with both >> Pharo and Squeak at the same time? Otherwise, we will have to maintain >> a separate universe which will complicate my work a lot. > > I plan to remove MVC from Shout. > And create a separate, optional, ShoutMVC package that can be loaded after > loading the main Shout package. This is the best solution I think. > Will you be able to load ShoutMVC into Squeak images, but not load it into > Pharo? It is possible yes but no straightforward. The simplest solution is not to support MVC anymore in squeak-dev images. What do you think? > If not, then I can create a .sar installer which checks for the existance of > MVC before loading ShoutMVC It is the simplest solution for me, but not for you :-). Do you think ShoutMVC could be of interest to anyone? -- 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 17, 2008

[Pharo-project] Re: Re: Missing PluggableTextControllerandPluggableTextView

by Andrew Tween

"Damien Cassou" <damien.cassou(a)gmail.com> wrote in message news:6ac749c10806170613p3edfb55h3fddcaf61fca4f0c@mail.gmail.com... On Tue, Jun 17, 2008 at 2:37 PM, Andrew Tween <amtween(a)hotmail.com> wrote: > I'll take a look and see if I can create a Pharo compatible Shout, >Do you think it can be possible to have Shout compatible with both >Pharo and Squeak at the same time? Otherwise, we will have to maintain >a separate universe which will complicate my work a lot. I plan to remove MVC from Shout. And create a separate, optional, ShoutMVC package that can be loaded after loading the main Shout package. Will you be able to load ShoutMVC into Squeak images, but not load it into Pharo? If not, then I can create a .sar installer which checks for the existance of MVC before loading ShoutMVC Andy -- 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 17, 2008

Re: [Pharo-project] Re: Missing PluggableTextController andPluggableTextView

by Damien Cassou

On Tue, Jun 17, 2008 at 2:37 PM, Andrew Tween <amtween(a)hotmail.com> wrote: > I'll take a look and see if I can create a Pharo compatible Shout, Do you think it can be possible to have Shout compatible with both Pharo and Squeak at the same time? Otherwise, we will have to maintain a separate universe which will complicate my work a lot. -- 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 17, 2008

Re: [Pharo-project] Missing PluggableTextController and PluggableTextView

by Alain Plantec

On Tuesday 17 June 2008 14:25:28 Damien Cassou wrote: > I've just update my image to 10041 and tried to generate a pharo-dev > from it. However, the process failed while trying to install Shout > because it depends on PluggableTextController and PluggableTextView > which are not in the image anymore. > Hi Damien, yes, I guess the problem concerns PluggableShoutView and PluggableShoutViewController. PluggableShoutViewController is the default mvc controller class for PluggableShoutView. (and PluggableShoutView is not referenced anywhere in pharo-dev). I've found another problem related to view instance variable + OB. I will report it tonight. cheers alain

June 17, 2008

[Pharo-project] Re: Missing PluggableTextController andPluggableTextView

by Andrew Tween

I'll take a look and see if I can create a Pharo compatible Shout, Andy "Damien Cassou" <damien.cassou(a)gmail.com> wrote in message news:6ac749c10806170525r2da65fbr17a00ce24f0cd041@mail.gmail.com... I've just update my image to 10041 and tried to generate a pharo-dev from it. However, the process failed while trying to install Shout because it depends on PluggableTextController and PluggableTextView which are not in the image anymore. -- 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 17, 2008

Re: [Pharo-project] Missing PluggableTextController and PluggableTextView

by Alexandre Bergel

Arg.. These classes were removed by Alain's change. Can you identify which packages requires those classes? Cheers, Alexandre On 17 Jun 2008, at 14:25, Damien Cassou wrote: > I've just update my image to 10041 and tried to generate a pharo-dev > from it. However, the process failed while trying to install Shout > because it depends on PluggableTextController and PluggableTextView > which are not in the image anymore. > > -- > 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 17, 2008

[Pharo-project] Missing PluggableTextController and PluggableTextView

by Damien Cassou

I've just update my image to 10041 and tried to generate a pharo-dev from it. However, the process failed while trying to install Shout because it depends on PluggableTextController and PluggableTextView which are not in the image anymore. -- 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 17, 2008

Re: [Pharo-project] [ANN] MVC removal step two harvested

by Norbert Hartl

On Tue, 2008-06-17 at 13:35 +0200, StÃ©phane Ducasse wrote: > Hi all > > I harvested the changes proposed by alain for the removal of MVC. > Please test pharo since it was a large change. > tests run as expected. There is one obsolete class left which is referenced by MvcTextEditor. That sounds like it is to be removed anyway ;) Otherwise a AppRegistry removeObsolete will do. Norbert

June 17, 2008

[Pharo-project] [ANN] MVC removal step two harvested

by StÃ©phane Ducasse

Hi all I harvested the changes proposed by alain for the removal of MVC. Please test pharo since it was a large change. stef

June 17, 2008

[Pharo-project] Fwd: [Seaside] Timespan bug

by StÃ©phane Ducasse

Begin forwarded message: > From: "David T. Lewis" <lewis(a)mail.msen.com> > Date: June 17, 2008 2:50:58 AM CEDT > To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org> > Subject: Re: [Seaside] Timespan bug > Reply-To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org > > > > On Mon, Jun 16, 2008 at 01:50:43PM +1000, Steve Aldred wrote: >> Sorry for posting this here but I don't use Squeak itself and hence >> aren't on the main squeak list. >> >> As a VW Seaside user I do use Squeak extensions. There is a bug in >> Timespan as shown below: >> >> (Year starting: (DateAndTime year: 2008 month: 1 day:1)) previous >> >> The result should be 2007 but it returns 2006. >> >> Year should implement previous the same as Month does. > > Steve, > > Thanks for reporting this issue. I was going to enter a report on your > behalf in the Squeak bug tracking system, but it looks like Brent is > already on top of it :) > > http://bugs.squeak.org/view.php?id=7097 > > The bug report includes a proposed fix, which is straightforward if > you > want to include it in your image: > > http://bugs.squeak.org/file_download.php?file_id=3386&type=bug > > Brent's fix is as follows: > > Year>>previous > "This implementation handles leap years correctly" > ^ self class year: (self year - 1) > > Dave > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

June 17, 2008

[Pharo-project] Fwd: getting class variable access

by StÃ©phane Ducasse

Begin forwarded message: > From: Colin Putney <cputney(a)wiresong.ca> > Date: June 16, 2008 12:08:33 AM CEDT > To: OmniBrowser developers <ob-dev(a)wiresong.ca> > Subject: Re: getting class variable access > Reply-To: OmniBrowser developers <ob-dev(a)wiresong.ca> > > > On 15-Jun-08, at 11:57 AM, stephane ducasse wrote: > >> still having good name in the registration would help because OB >> adaptor sucks > > Agreed. Unfortunately, the registration mechanism doesn't let you > choose the name displayed in the menu. It just uses the name of the > class being registered. Also, the protocol expected by the > registration mechanism is particularly twisted, which is why I had to > create a separate class for it, instead of using OBSystemBrowser > directly. > > Colin > _______________________________________________ > ob-dev mailing list > ob-dev(a)wiresong.ca > http://mail.wiresong.ca/mailman/listinfo/ob-dev >

June 17, 2008

Re: [Pharo-project] Namespaces?

by StÃ©phane Ducasse

alex I reread what we did and I do not like it I can tell you tomorrow why. Stef On Jun 16, 2008, at 8:53 PM, Alexandre Bergel wrote: > Few years ago Stef and I worked on an implementation. It is working > fairly well. Unfortunately, we did not push it for an inclusion. > http://www.squeaksource.com/Namespace > > I just tried it. 'Namespace install' to install it. > Test are green in my seaside image. > > Cheers, > Alexandre > > On 16 Jun 2008, at 19:14, Michael Rueger wrote: > >> Hi all, >> >> asking the unmentionable ;-) >> >> Are there any plans for (simple) name spaces in Pharo? >> Reason I'm asking is that it would make moving code between e.g. VW >> and Pharo easier IMHO. >> >> Michael >> >> _______________________________________________ >> 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 >

June 16, 2008

Re: [Pharo-project] Namespaces?

by StÃ©phane Ducasse

On Jun 16, 2008, at 7:14 PM, Michael Rueger wrote: > Hi all, > > asking the unmentionable ;-) :) > Are there any plans for (simple) name spaces in Pharo? This is not that I would not like but really I'm thorn apart because really having something simple would be nice but after we have the tools and I'm not sure that having that orthogonal to packages would be good. I reread recently the proposal of goran but I do not like the idea that we would have Goo::Point in the code everywhere instead of Point or GooPoint. Now I would like to know whether we can factor that at the "border" of package but this have the prices of import statements. Now I have the impression that for pharo first having some nice clean packages is the first step. > > Reason I'm asking is that it would make moving code between e.g. VW > and Pharo easier IMHO. I would only do it in one way :) Stef

June 16, 2008

Re: [Pharo-project] Namespaces?

by StÃ©phane Ducasse

But I would change it. Stef On Jun 16, 2008, at 8:53 PM, Alexandre Bergel wrote: > Few years ago Stef and I worked on an implementation. It is working > fairly well. Unfortunately, we did not push it for an inclusion. > http://www.squeaksource.com/Namespace > > I just tried it. 'Namespace install' to install it. > Test are green in my seaside image. > > Cheers, > Alexandre > > On 16 Jun 2008, at 19:14, Michael Rueger wrote: > >> Hi all, >> >> asking the unmentionable ;-) >> >> Are there any plans for (simple) name spaces in Pharo? >> Reason I'm asking is that it would make moving code between e.g. VW >> and Pharo easier IMHO. >> >> Michael >> >> _______________________________________________ >> 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 >

June 16, 2008

Re: [Pharo-project] Namespaces?

by Alexandre Bergel

Few years ago Stef and I worked on an implementation. It is working fairly well. Unfortunately, we did not push it for an inclusion. http://www.squeaksource.com/Namespace I just tried it. 'Namespace install' to install it. Test are green in my seaside image. Cheers, Alexandre On 16 Jun 2008, at 19:14, Michael Rueger wrote: > Hi all, > > asking the unmentionable ;-) > > Are there any plans for (simple) name spaces in Pharo? > Reason I'm asking is that it would make moving code between e.g. VW > and Pharo easier IMHO. > > Michael > > _______________________________________________ > 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 16, 2008

[Pharo-project] Namespaces?

by Michael Rueger

Hi all, asking the unmentionable ;-) Are there any plans for (simple) name spaces in Pharo? Reason I'm asking is that it would make moving code between e.g. VW and Pharo easier IMHO. Michael

June 16, 2008

Re: [Pharo-project] Need code review

by StÃ©phane Ducasse

Ok I will try to harvest it today. Stef On Jun 16, 2008, at 2:23 PM, Alexandre Bergel wrote: > Ah ok.. > I see now... > > As I said, your removal makes fully sense to me... > > Alexandre > > > On 16 Jun 2008, at 14:13, Alain Plantec wrote: > >> Hi Alexandre, >> thanks for this review. >> >> On Monday 16 June 2008 09:34:26 Alexandre Bergel wrote: >>>> http://lists.gforge.inria.fr/pipermail/pharo-project/2008-June/000323.html >>>>>> [Pharo-project] MVC removal step2 investigations >> ... >>> Few questions: >>> - Inspector>>openOn: anObject withEvalPane: withEval withLabel: >>> label >>> valueViewClass: valueViewClass seems to be called by FormInspectView >>> class>>openOn: aFormDictionary withLabel: aLabel >>> Don't you think that removing this method might be a problem? >> FormInspectView class is removed >>> - Why have you removed PasteUpMorph>>open ? >> Here is it's code: >> PasteUpMorph>>open >> "Open a view on this WorldMorph." >> MorphWorldView openOn: self. >> MorphWorldView is a subclass of View (MVC) which is removed. >> So PasteUpMorph>>open makes sense only in MVC context. >>> >>> Je n'ai vu aucun problÃ¨me aprÃ¨s avoir chargÃ© le removal. >>> I favour an inclusion. >> I would only insist on the following point: >> One big change concerns the Controller hierarchy which was >> Controller #('model' 'view' 'sensor' 'lastActivityTime') >> MouseMenuController #('redButtonMenu' 'redButtonMessages') >> ScrollController #('scrollBar' 'marker' 'savedArea' 'menuBar' >> 'savedMenuBarArea') >> ParagraphEditor #('paragraph' 'startBlock' 'stopBlock' >> 'beginTypeInBlock' ' >> and which becomes: >> Controller #('model' 'sensor' 'lastActivityTime') >> ParagraphEditor #('paragraph' 'startBlock' 'stopBlock' >> 'beginTypeInBlock' 'emphasisHere' 'initialText' 'selectionShowing' >> 'otherInterval' 'lastParentLocation') >> >> as you can see, MouseMenuController and ScrollController are >> removed and ParagraphEditor is now a direct subclass of Controller. >> Controller is now more simple because of 'view' instance variable >> removeal. >> I think that 'lastActivityTime' can be removed too and I've also >> noticed more cleaning possibilities implied by this changeset. >> Especially in class ScreenController which holds a lot of menu >> methods which are not used anymore >> (world menu equivalent methods but in the context of MVC). >> I will provide a changeset or a slice later. >> >> alain >>> >>> Cheers, >>> Alexandre >>> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > 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 >

June 16, 2008

Re: [Pharo-project] Need code review

by Alexandre Bergel

Ah ok.. I see now... As I said, your removal makes fully sense to me... Alexandre On 16 Jun 2008, at 14:13, Alain Plantec wrote: > Hi Alexandre, > thanks for this review. > > On Monday 16 June 2008 09:34:26 Alexandre Bergel wrote: >>> http://lists.gforge.inria.fr/pipermail/pharo-project/2008-June/000323.html >>>>> [Pharo-project] MVC removal step2 investigations > ... >> Few questions: >> - Inspector>>openOn: anObject withEvalPane: withEval withLabel: >> label >> valueViewClass: valueViewClass seems to be called by FormInspectView >> class>>openOn: aFormDictionary withLabel: aLabel >> Don't you think that removing this method might be a problem? > FormInspectView class is removed >> - Why have you removed PasteUpMorph>>open ? > Here is it's code: > PasteUpMorph>>open > "Open a view on this WorldMorph." > MorphWorldView openOn: self. > MorphWorldView is a subclass of View (MVC) which is removed. > So PasteUpMorph>>open makes sense only in MVC context. >> >> Je n'ai vu aucun problÃ¨me aprÃ¨s avoir chargÃ© le removal. >> I favour an inclusion. > I would only insist on the following point: > One big change concerns the Controller hierarchy which was > Controller #('model' 'view' 'sensor' 'lastActivityTime') > MouseMenuController #('redButtonMenu' 'redButtonMessages') > ScrollController #('scrollBar' 'marker' 'savedArea' 'menuBar' > 'savedMenuBarArea') > ParagraphEditor #('paragraph' 'startBlock' 'stopBlock' > 'beginTypeInBlock' ' > and which becomes: > Controller #('model' 'sensor' 'lastActivityTime') > ParagraphEditor #('paragraph' 'startBlock' 'stopBlock' > 'beginTypeInBlock' 'emphasisHere' 'initialText' 'selectionShowing' > 'otherInterval' 'lastParentLocation') > > as you can see, MouseMenuController and ScrollController are removed > and ParagraphEditor is now a direct subclass of Controller. > Controller is now more simple because of 'view' instance variable > removeal. > I think that 'lastActivityTime' can be removed too and I've also > noticed more cleaning possibilities implied by this changeset. > Especially in class ScreenController which holds a lot of menu > methods which are not used anymore > (world menu equivalent methods but in the context of MVC). > I will provide a changeset or a slice later. > > alain >> >> Cheers, >> Alexandre >> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 16, 2008

Re: [Pharo-project] Need code review

by Alain Plantec

Hi Alexandre, thanks for this review. On Monday 16 June 2008 09:34:26 Alexandre Bergel wrote: > > http://lists.gforge.inria.fr/pipermail/pharo-project/2008-June/000323.html > >>> [Pharo-project] MVC removal step2 investigations ... > Few questions: > - Inspector>>openOn: anObject withEvalPane: withEval withLabel: label > valueViewClass: valueViewClass seems to be called by FormInspectView > class>>openOn: aFormDictionary withLabel: aLabel > Don't you think that removing this method might be a problem? FormInspectView class is removed > - Why have you removed PasteUpMorph>>open ? Here is it's code: PasteUpMorph>>open "Open a view on this WorldMorph." MorphWorldView openOn: self. MorphWorldView is a subclass of View (MVC) which is removed. So PasteUpMorph>>open makes sense only in MVC context. > > Je n'ai vu aucun problÃ¨me aprÃ¨s avoir chargÃ© le removal. > I favour an inclusion. I would only insist on the following point: One big change concerns the Controller hierarchy which was Controller #('model' 'view' 'sensor' 'lastActivityTime') MouseMenuController #('redButtonMenu' 'redButtonMessages') ScrollController #('scrollBar' 'marker' 'savedArea' 'menuBar' 'savedMenuBarArea') ParagraphEditor #('paragraph' 'startBlock' 'stopBlock' 'beginTypeInBlock' ' and which becomes: Controller #('model' 'sensor' 'lastActivityTime') ParagraphEditor #('paragraph' 'startBlock' 'stopBlock' 'beginTypeInBlock' 'emphasisHere' 'initialText' 'selectionShowing' 'otherInterval' 'lastParentLocation') as you can see, MouseMenuController and ScrollController are removed and ParagraphEditor is now a direct subclass of Controller. Controller is now more simple because of 'view' instance variable removeal. I think that 'lastActivityTime' can be removed too and I've also noticed more cleaning possibilities implied by this changeset. Especially in class ScreenController which holds a lot of menu methods which are not used anymore (world menu equivalent methods but in the context of MVC). I will provide a changeset or a slice later. alain > > Cheers, > Alexandre >

June 16, 2008

RE: [Pharo-project] Reintegration of StringSocket

by Gary Chambers

I notice that StringSocket inherits from ObjectSocket and then Stream... so StringSocketStream might have been a better name for it.... Gary. > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr]On Behalf Of Michael > Rueger > Sent: 14 June 2008 3:52 AM > To: An open mailing list to discuss any topics related to an > open-sourceSmalltalk > Subject: Re: [Pharo-project] Reintegration of StringSocket > > > StÃ©phane Ducasse wrote: > > sure > > can you publish it somewhere? > > > > Stef > > > > On Jun 13, 2008, at 3:39 PM, Damien Cassou wrote: > > > >> 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? > > I would rather vote for rewrite Universes to not use. > Special subclasses of Socket are plain evil ;-) > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 16, 2008