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

[Pharo-project] [ANN] RevertHTTPSocketSystemWindow

by Gabriel Cotelli

Name: SLICE-RevertHTTPSocketSystemWindow-GabrielOmarCotelli.2 Author: GabrielOmarCotelli Time: 4 June 2009, 8:02:26 pm UUID: 9c77c9bb-bfbb-dd42-90dc-d4f2a61f01e4 Ancestors: SLICE-RevertHTTPSocketSystemWindow-GabrielOmarCotelli.1 Dependencies: Morphic-GabrielOmarCotelli.314, Network-Protocols-GabrielOmarCotelli.8 Reverted conflicting methods to previous versions. Made by Yoshiki in Squeak. HTTPSocket>>logToTranscript SystemWindow>>mouseMove:

June 4, 2009

[Pharo-project] HScaleMorph and VScaleMorph in Polymorph

by Adrian Lienhard

Hi Gary, Recently, I removed the class ScaleMorph because it was not license clean and it was not used. Only now I've noticed that there are indirect subclasses in Polymorph (HScaleMorph and VScaleMorph inheriting from FixedScaleMorph). Can we remove these three classes? They are not referenced and don't have any instances. Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

June 4, 2009

[Pharo-project] [ANN] Update #10325

by Adrian Lienhard

- fix MethodDictionary>>#do: (used by OCompletion) - 863: Disable font scanning at startup - 842: License cleaning: remove SkipList - 842: License cleaning: remove topologicallySortedUsing:, sortTopologically, should:precede:, and their tests ___________________ http://www.adrian-lienhard.ch/

June 4, 2009

Re: [Pharo-project] an odd bug

by Hernan Wilkinson

yes, but not only that... I also create "complete objects" from its very first time. For example, instead of:Date new day:1; moth:1; year: 2009. I do: Date newDay: 1 moth: 1 year: 2009. That way you will never have an invalid Date 2009/6/4 Steve Wirts <stevewirts(a)gmail.com> > That's the Null Object Pattern! > > http://en.wikipedia.org/wiki/Null_Object_pattern > > > 2009/6/4 Hernan Wilkinson <hernan.wilkinson(a)gmail.com> > > I was going to suggest exactly that.As a rule, I never use nil because if >> you do it you will have to check for it somewhere... nil is the root of most >> of the problems! if not, look at all the errors I fixed in the other mail, >> most of them are because nil is being used. >> So, instead of nil, another object has to be use, and like you said in >> this case an empty collection I think will work. I'm just changing that... >> I'll send the changes today (I hope). >> >> Hernan. >> >> >> On Thu, Jun 4, 2009 at 11:32 AM, Michael Rueger <m.rueger(a)acm.org> wrote: >> >>> Sean Allen wrote: >>> >>> > Just as a bit more info. I used squeak for several months without ever >>> > seeing this error. >>> > I used pharo for 3 months without seeing this error. I've only gotten >>> > this error in the latest images >>> > with the latest vm and get it constantly. Not occassionally, I can get >>> > this to happen at least >>> > once every 120 seconds or so, sometimes more often. It would seem to be >>> > as an outsider, >>> > that something must have changed. >>> >>> it definitely sounds like it. >>> Would be good to investigate what might have changed in the call path >>> that *sets* the variable to check why it is ending up being nil. Maybe >>> it shouldn't be set or initialized to nil but to an empty collection in >>> those cases? >>> >>> 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 4, 2009

Re: [Pharo-project] [ANN][Dev-Images] June 2009 versions

by Schwab,Wilhelm K

Damien, All, I tried the web image, and I'm glad I did. I cannot in good conscience rave about the keyboard response, but it is much improved over recent versions, and the anti-aliased text is stunning. <well-intentioned-rant> OmniBrowser is too slow for its own good, at lest in my experience. I recall some mention of backward compatibility with Squeak preventing a refractoring of its handling of packages for efficiency. If that is the last word, then maybe we need to re-think our dependence on it?? Perhaps I am too distant from the details to understand what it does for us, but the several+ second delays are getting old. One reason I had trouble repackaging code was that the command to create a package is not always displayed: in fact, it is _not_ displayed precisely when (by selected item) it is needed most! Specifically, it does not appear when a "non-packaged" item is selected. Another thing that bit me is that, especially in categorizing methods as extensions, I had to re-type the desired category many times. There appears to be some learning of the categories, but it is slow to happen, and did not occur in time to save me from myself. </well-intentioned-rant> Bill

June 4, 2009

Re: [Pharo-project] an odd bug

by Steve Wirts

That's the Null Object Pattern! http://en.wikipedia.org/wiki/Null_Object_pattern 2009/6/4 Hernan Wilkinson <hernan.wilkinson(a)gmail.com> > I was going to suggest exactly that.As a rule, I never use nil because if > you do it you will have to check for it somewhere... nil is the root of most > of the problems! if not, look at all the errors I fixed in the other mail, > most of them are because nil is being used. > So, instead of nil, another object has to be use, and like you said in this > case an empty collection I think will work. I'm just changing that... I'll > send the changes today (I hope). > > Hernan. > > > On Thu, Jun 4, 2009 at 11:32 AM, Michael Rueger <m.rueger(a)acm.org> wrote: > >> Sean Allen wrote: >> >> > Just as a bit more info. I used squeak for several months without ever >> > seeing this error. >> > I used pharo for 3 months without seeing this error. I've only gotten >> > this error in the latest images >> > with the latest vm and get it constantly. Not occassionally, I can get >> > this to happen at least >> > once every 120 seconds or so, sometimes more often. It would seem to be >> > as an outsider, >> > that something must have changed. >> >> it definitely sounds like it. >> Would be good to investigate what might have changed in the call path >> that *sets* the variable to check why it is ending up being nil. Maybe >> it shouldn't be set or initialized to nil but to an empty collection in >> those cases? >> >> 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 4, 2009

Re: [Pharo-project] an odd bug

by Hernan Wilkinson

I was going to suggest exactly that.As a rule, I never use nil because if you do it you will have to check for it somewhere... nil is the root of most of the problems! if not, look at all the errors I fixed in the other mail, most of them are because nil is being used. So, instead of nil, another object has to be use, and like you said in this case an empty collection I think will work. I'm just changing that... I'll send the changes today (I hope). Hernan. On Thu, Jun 4, 2009 at 11:32 AM, Michael Rueger <m.rueger(a)acm.org> wrote: > Sean Allen wrote: > > > Just as a bit more info. I used squeak for several months without ever > > seeing this error. > > I used pharo for 3 months without seeing this error. I've only gotten > > this error in the latest images > > with the latest vm and get it constantly. Not occassionally, I can get > > this to happen at least > > once every 120 seconds or so, sometimes more often. It would seem to be > > as an outsider, > > that something must have changed. > > it definitely sounds like it. > Would be good to investigate what might have changed in the call path > that *sets* the variable to check why it is ending up being nil. Maybe > it shouldn't be set or initialized to nil but to an empty collection in > those cases? > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 4, 2009

Re: [Pharo-project] AutomaticMethodCategorizer in Pharo

by Damien Cassou

2009/6/4 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi folks. I really like the AutomaticMethodCategorizer from Squeak. I see > they are not included in Pharo dev images. Is this just a preference or they > don't work on pharo? I didn't found them in squeaksource. So, how can I > install AutomaticMethodCategorizer and AutomaticMethodCategorizerOB in > Pharo? Please try them and report if it works. Thank you http://www.squeaksource.com/autoMethodCat/AutomaticMethodCategorizer-DF.25.… http://www.squeaksource.com/autoMethodCat/AutomaticMethodCategorizerOB-DF.1… -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 4, 2009

Re: [Pharo-project] an odd bug

by Michael Rueger

Sean Allen wrote: > Just as a bit more info. I used squeak for several months without ever > seeing this error. > I used pharo for 3 months without seeing this error. I've only gotten > this error in the latest images > with the latest vm and get it constantly. Not occassionally, I can get > this to happen at least > once every 120 seconds or so, sometimes more often. It would seem to be > as an outsider, > that something must have changed. it definitely sounds like it. Would be good to investigate what might have changed in the call path that *sets* the variable to check why it is ending up being nil. Maybe it shouldn't be set or initialized to nil but to an empty collection in those cases? Michael

June 4, 2009

Re: [Pharo-project] an odd bug

by Sean Allen

On Thu, Jun 4, 2009 at 3:11 AM, Michael Rueger <m.rueger(a)acm.org> wrote: > StÃ©phane Ducasse wrote: > > Thanks. > > > > I think that for the MouseOverHandler it would be good to know if this > > is related to Sensor changes. > > Mike what you think? > > It shouldn't. On the Morphic side there weren't any changes to process > behavior, it still pulls the events out of the queue in the step cycle. > Just as a bit more info. I used squeak for several months without ever seeing this error. I used pharo for 3 months without seeing this error. I've only gotten this error in the latest images with the latest vm and get it constantly. Not occassionally, I can get this to happen at least once every 120 seconds or so, sometimes more often. It would seem to be as an outsider, that something must have changed.

June 4, 2009