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

[Pharo-project] [update 1.1] #11154

by StÃ©phane Ducasse

11154 ----- - Issue 1788: SMTPClient does not send HELO or EHLO, session is not initiated - Issue 1793: Remove SqueakClipBoard - Issue 1764: remove isPvtSelector Stef

Jan. 13, 2010

[Pharo-project] White rectangles

by Torsten Bergmann

>Yes it is a known issue. This is a bug in the VMs. >It was recently discussed in the thread "Core font" that >you have started. Yes, the interesting thing is that I just had a flickering when we started the above discussion (which was acceptable). Now I get fully painted white rectangles - which is another and now really ugly effect. Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Jan. 13, 2010

Re: [Pharo-project] White rectangles

by Adrian Lienhard

Hi Torsten, Yes it is a known issue. This is a bug in the VMs. It was recently discussed in the thread "Core font" that you have started. I created an issue: http://code.google.com/p/pharo/issues/detail?id=1803 Adrian On Jan 13, 2010, at 13:34 , Torsten Bergmann wrote: > When I drag a window in latest core it is not fully painted. > I get white rectangles at any place where usually text is displayed > (browser code pane, category list and the like). Related to font > changes? > > Any comments? > > Thx > T. > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2010

[Pharo-project] White rectangles

by Torsten Bergmann

When I drag a window in latest core it is not fully painted. I get white rectangles at any place where usually text is displayed (browser code pane, category list and the like). Related to font changes? Any comments? Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Jan. 13, 2010

Re: [Pharo-project] clone vs shallowCopy

by StÃ©phane Ducasse

this someone is busy :) On Jan 13, 2010, at 12:40 PM, Nicolas Cellier wrote: > 2010/1/13 Lukas Renggli <renggli(a)gmail.com>: >>> Now it would be nice to clean that because in VW you have copy, shallowCopy and postCopy and it works. >>> They removed veryDeepCopy and other friends even when they were at the time were they could burn engineering time >>> on that. >> >> +10 >> >>> So for me clone is one too many. >>> And worse cloning and object cannot be a shallowCopy semantics. it should be more a veryDeepInnerVeryCopy (I could not resist sorry) >>> Of course we already clean and remove the veryDeepInnerCopy.... No comment. >> >> The strange thing about #shallowCopy is in SequenceableCollection. It >> overrides #shallowCopy and does not return a shallowCopy. >> >> Lukas >> > > Yes, that sort of strange things forced me to introduce > basicShallowCopy. This was a workaround but not a good fix. > The good fix is in trunk : remove SequenceableCollection>>shallowCopy > and define all the copy in term of postCopy and remove > basicShallowCopy. > > Someone should just cherry pick in trunk. > > Nicolas > > >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2010

Re: [Pharo-project] Object Buffer (implementation tryout)

by CÃ©drick BÃ©ler

cool thanks :) ... Shortcuts were not working in inspector/explorer but I fixed (hacked - override everywhere) it now. (All these shortcuts and menu stuffs really s**ks !!!) Anyway, it works and I'll use that until we got a better clipboard and/or history support :) 2010/1/13 Alexandre Bergel <alexandre(a)bergel.eu> > I tried it and it works. Tests are clean and easy to understand. Look > okay to me. > > Alexandre > > > On 12 Jan 2010, at 13:29, CÃ©drick BÃ©ler wrote: > > > ping :) > > > > See you later, > > > > 2010/1/12 Alexandre Bergel <alexandre(a)bergel.eu> > > Ok, I am waiting for your ping then > > > > Alexandre > > > > On 12 Jan 2010, at 12:17, CÃ©drick BÃ©ler wrote: > > > > > > > > Anyway, feel free to publish whatever changes you find necessary > > > (especially tests :) . I'll do some too) > > > > > > > > > I'm writting some right now... > > > > > > _______________________________________________ > > > 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 > > > > > > > > -- > > CÃ©drick > > _______________________________________________ > > 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 > -- CÃ©drick

Jan. 13, 2010

Re: [Pharo-project] clone vs shallowCopy

by Nicolas Cellier

2010/1/13 Lukas Renggli <renggli(a)gmail.com>: >> Now it would be nice to clean that because in VW you have copy, shallowCopy and postCopy and it works. >> They removed veryDeepCopy and other friends even when they were at the time were they could burn engineering time >> on that. > > +10 > >> So for me clone is one too many. >> And worse cloning and object cannot be a shallowCopy semantics. it should be more a veryDeepInnerVeryCopy (I could not resist sorry) >> Of course we already clean and remove the veryDeepInnerCopy.... No comment. > > The strange thing about #shallowCopy is in SequenceableCollection. It > overrides #shallowCopy and does not return a shallowCopy. > > Lukas > Yes, that sort of strange things forced me to introduce basicShallowCopy. This was a workaround but not a good fix. The good fix is in trunk : remove SequenceableCollection>>shallowCopy and define all the copy in term of postCopy and remove basicShallowCopy. Someone should just cherry pick in trunk. Nicolas > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 13, 2010

Re: [Pharo-project] InputSensor next step cleanup

by Igor Stasenko

2010/1/13 Michael Rueger <m.rueger(a)acm.org>: > On 1/13/2010 11:13 AM, Igor Stasenko wrote: > >> Next step is removing a direct reference to Sensor global, and replace >> it with something like: >> >> self eventSensor > > No, that is fixing a sympton, not the problem. > (John will love this ;-) ) > > You would still be polling the sensor. There should be no references to > Sensor -directly or indirectly- at all. The system should be completely > event driven and not be allowed to ask for anything. I know it is just > so comfortable to do this, but a very bad idea. Totally agree with you. But removing it from use, means changing the logic in places where it using it. And given that you got 166 refs to Sensor.. imagine what amount of work it means. So, see my proposal as an intermediate(transitional) step. > This basically goes back to introducing global references to ActiveHand > etc, something that really needs to be removed as well. > > Michael > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Jan. 13, 2010

Re: [Pharo-project] I cannot believe that Browser is relying on Object>>initialExtent

by StÃ©phane Ducasse

we will believe me :) On Jan 13, 2010, at 10:54 AM, Igor Stasenko wrote: > Kill them , please. :) > I dreaming about the time, when every method in Object will have a > very strong reasons to stay there. > > 2010/1/13 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> hold on :) >> we will kill a lot of them one at a time with a nice chainsaw :) >> >> Stef >> >> On Jan 13, 2010, at 8:58 AM, Lukas Renggli wrote: >> >>> And #defaultColor and #inform: and #modelSleep and #modelWakeUp and >>> #modelWakeUpIn: and ... >>> >>> 2010/1/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> argh....... >>>> May be not putting everything in Object would help. >>>> >>>> Stef >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> http://www.lukas-renggli.ch >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2010

Re: [Pharo-project] Undo/Redo [was: Re: Object Buffer (implementation tryout)]

by StÃ©phane Ducasse

nobody to talk about it but I would really like to see Sophie used in/by smalltalkers On Jan 13, 2010, at 11:25 AM, John M McIntosh wrote: > Ya, I'm sure StÃ©phane said why don't you give a talk on it... > > On 2010-01-13, at 1:02 AM, Serge Stinckwich wrote: >> Advertisement problem ? >> >> -- >> Serge Stinckwich >> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >> Smalltalkers do: [:it | All with: Class, (And love: it)] >> http://doesnotunderstand.org/ > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2010