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

[Pharo-project] What happened to demo mode?

by Oscar Nierstrasz

There used to be a fast way to set LARGE FONTS for showing a demo with Pharo. Is that hidden away somewhere now? I can only find individual settings for the fonts in multiple places. Demo mode is really, *really* important! Please put it back if it is missing, and make it really easy to find! - on

Oct. 24, 2010

Re: [Pharo-project] Proposal: adding 261 named colors

by Tudor Girba

Hi Johan, I would definitely be interested in getting this as an external library around Mondrian and Moose. Cheers, Doru On 24 Oct 2010, at 07:09, Johan Fabry wrote: > If you instantiate a color but dont see it, does it matter that the color is not what you wanted? It's like considering the classical 'tree falls in the forest' question. > > Or if you prefer a more implementation-based view: if a morph cannot be drawn, do you halt the system? Right now it is not the case, a rectangle with a cross is drawn. > > In any case, I am open to suggestions for improvement! > > On 23 Oct 2010, at 18:46, Schwab,Wilhelm K wrote: > >> I don't like the idea of instantiating red if the name is not recognized. Since you don't have selectors (900+ might be a bit much), the compiler/Shout won't catch mistakes, and it will be an ongoing source of silent failures. >> >> >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Johan Fabry [jfabry(a)dcc.uchile.cl] >> Sent: Saturday, October 23, 2010 5:29 PM >> To: Pharo Development >> Subject: [Pharo-project] Proposal: adding 261 named colors >> >> Hi all, >> >> in the work of AspectMaps I was a bit let down by the named colors Pharo provides (Color red et cetera). Now I am happy to say that thanks to the XKCD color survey I was able to improve on this. I can now use 261 named colors thanks to a XKCDColor class, and I'd like to share the code, ideally to be included into Pharo. The code is available in bugreport http://code.google.com/p/pharo/issues/detail?id=3148 >> >> Here is the class comment fo XKCDColor: >> >> ---snip--- >> A color named according to the XKCD color survey, as published in http://blog.xkcd.com/2010/05/03/color-survey-results/ ("Over five million colors were named across 222,500 user sessions.") >> >> Of the full table of 954 colors that is published only those were selected that did not have a space in their name, ignoring e.g. electric lime, nasty green, macaroni and cheese, pinkish tan, but also light light blue, strong blue. This results in a table of 261 named colors, but with duplicates such as ochre and ocre. These were left in since as they are common misspellings it is more convenient for the user. >> >> To instantiate: XCDColor named: aString where aString is one of the 261 named colors. If the name is not known, the color red is instantiated. Instances of XKCDColor know their XKCD color name, returned by the name accessor. >> >> Thanks to Randall Monroe of http://xkcd.com for providing the data. >> ---snip--- >> >> And here is a picture of all the colors (Generated with Mondrian :-) ) >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Johan Fabry > jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Beauty is where we see it."

Oct. 24, 2010

Re: [Pharo-project] Proposal: adding 261 named colors

by StÃ©phane Ducasse

ok I read the code :) I like 'swamp' Stef On Oct 23, 2010, at 11:30 PM, Johan Fabry wrote: > Hi all, > > in the work of AspectMaps I was a bit let down by the named colors Pharo provides (Color red et cetera). Now I am happy to say that thanks to the XKCD color survey I was able to improve on this. I can now use 261 named colors thanks to a XKCDColor class, and I'd like to share the code, ideally to be included into Pharo. The code is available in bugreport http://code.google.com/p/pharo/issues/detail?id=3148 > > Here is the class comment fo XKCDColor: > > ---snip--- > A color named according to the XKCD color survey, as published in http://blog.xkcd.com/2010/05/03/color-survey-results/ ("Over five million colors were named across 222,500 user sessions.") > > Of the full table of 954 colors that is published only those were selected that did not have a space in their name, ignoring e.g. electric lime, nasty green, macaroni and cheese, pinkish tan, but also light light blue, strong blue. This results in a table of 261 named colors, but with duplicates such as ochre and ocre. These were left in since as they are common misspellings it is more convenient for the user. > > To instantiate: XCDColor named: aString where aString is one of the 261 named colors. If the name is not known, the color red is instantiated. Instances of XKCDColor know their XKCD color name, returned by the name accessor. > > Thanks to Randall Monroe of http://xkcd.com for providing the data. > ---snip--- > > And here is a picture of all the colors (Generated with Mondrian :-) ) > > <Colors.png> > > -- > Johan Fabry > jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 24, 2010

Re: [Pharo-project] Proposal: adding 261 named colors

by StÃ©phane Ducasse

johan what is the principle? There was a package on squeaksource or squeak map that adds a lot 512 or so color names. Stef

Oct. 24, 2010

Re: [Pharo-project] Smells looking at collections

by StÃ©phane Ducasse

>>> > Not trivial? Maybe not, but only a little bit harder than trivial. We are open to suggestions believe me :) > >> 2) well, this is difficult to get the money for the butter and the butter - we are trying. > > If you can compose classes the way you can add a trait to a class now with class and optional method level instance+class variable mapping, then you're done. It would be a lot simpler to use it _and_ it would also be a lot easier to implement it. Especially the tools part. I'm interested to hear more about that. Tell us more. The problem we faced was - offset access = you cannot reuse bytecode of a trait because the order of the offset can be different in each trait users - initialization of instances variables at the trait level and the composition at the class levele > >> 3) again if nobody does anything and we just all cry on ourselves then nothing will happen. > > Tools are a must. No tools - no users. Exact. >> So for now identifying traits and learning is the way. Then we can refactor, redesign > > Well, Traits are in Squeak since 2006, IIRC they were available a few years earlier. So in the last X (at least 4) years the only good candidate to become a Trait was Magnitude. Come on. I will not answer to such statement because I'm positive thinking. Stef

Oct. 24, 2010

Re: [Pharo-project] akuhn/SUnit: run faster tests first & step through tests

by StÃ©phane Ducasse

Lack of maintainers, too many unwanted features, lack of explanation, large changes... And this is not that several persons did not look at the code. It got more than the average. Now I'm thinking that with discussion and care we should really get another testing framework with the same API that SUnit because if we want that PharoSunit is the same as Sunit then we are doomed to be backward compatible and no real improvements. Stef On Oct 23, 2010, at 10:58 PM, Adrian Kuhn wrote: > Sad to hear that. > > Technical difficulties, or just lack of customers? ^^ > > --AA > > On Oct 23, 2010, at 08:05 , StÃ©phane Ducasse wrote: > >> It was too difficult to integrate. >> >> Stef >> >> On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote: >> >>> What's the status of akuhn/SUnit? I couldn't find his code in 1.2 core. >>> >>> Niko >>> >>> On Wed, Feb 3, 2010 at 1:13 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> this loads well in the latest 1,1 core :) >>>> so now we should really have a look and these cool changes >>>> >>>> Stef >>>> >>>> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: >>>> >>>>> SystemChangeNotifier uniqueInstance >>>>> noMoreNotificationsFor: TestCase. >>>>> Gofer it >>>>> disablePackageCache; >>>>> squeaksource: 'akuhn'; >>>>> package: 'SUnit'; >>>>> package: 'SUnitGUI'; >>>>> load. >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> http://scg.unibe.ch/staff/Schwarz >>> twitter.com/nes1983 >>> Tel: +41 076 235 8683 >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

Oct. 24, 2010

Re: [Pharo-project] Proposal: adding 261 named colors

by Johan Fabry

If you instantiate a color but dont see it, does it matter that the color is not what you wanted? It's like considering the classical 'tree falls in the forest' question. Or if you prefer a more implementation-based view: if a morph cannot be drawn, do you halt the system? Right now it is not the case, a rectangle with a cross is drawn. In any case, I am open to suggestions for improvement! On 23 Oct 2010, at 18:46, Schwab,Wilhelm K wrote: > I don't like the idea of instantiating red if the name is not recognized. Since you don't have selectors (900+ might be a bit much), the compiler/Shout won't catch mistakes, and it will be an ongoing source of silent failures. > > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Johan Fabry [jfabry(a)dcc.uchile.cl] > Sent: Saturday, October 23, 2010 5:29 PM > To: Pharo Development > Subject: [Pharo-project] Proposal: adding 261 named colors > > Hi all, > > in the work of AspectMaps I was a bit let down by the named colors Pharo provides (Color red et cetera). Now I am happy to say that thanks to the XKCD color survey I was able to improve on this. I can now use 261 named colors thanks to a XKCDColor class, and I'd like to share the code, ideally to be included into Pharo. The code is available in bugreport http://code.google.com/p/pharo/issues/detail?id=3148 > > Here is the class comment fo XKCDColor: > > ---snip--- > A color named according to the XKCD color survey, as published in http://blog.xkcd.com/2010/05/03/color-survey-results/ ("Over five million colors were named across 222,500 user sessions.") > > Of the full table of 954 colors that is published only those were selected that did not have a space in their name, ignoring e.g. electric lime, nasty green, macaroni and cheese, pinkish tan, but also light light blue, strong blue. This results in a table of 261 named colors, but with duplicates such as ochre and ocre. These were left in since as they are common misspellings it is more convenient for the user. > > To instantiate: XCDColor named: aString where aString is one of the 261 named colors. If the name is not known, the color red is instantiated. Instances of XKCDColor know their XKCD color name, returned by the name accessor. > > Thanks to Randall Monroe of http://xkcd.com for providing the data. > ---snip--- > > And here is a picture of all the colors (Generated with Mondrian :-) ) > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Oct. 24, 2010

Re: [Pharo-project] some patterns I would like to **kill**

by Igor Stasenko

On 23 October 2010 21:47, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Hey, I want some credit here - for coming to Squeak's possible defense :) > > All I am saying is that there is a possible space/speed tradeoff with a twist. Â There was a fair amount written about these decisions, which is why I know anything at all about them. Â Adding an instance variable for a rarely used sub-morph of a widely-instantiated morph might be an opportunity to fail to learn from history. Â Most likely, the patterns Stef has noticed are simply mis-uses of sparse storage. Â The best way to proceed would be to find an example of it that has many instances in the image, profile, fix, and profile again to see if the fix hurts performance (or perhaps helps it). Â The usual caveats about benchmarking being really hard to do well apply, of course. > I did some experiment(s) with Morphic, placing many morph aspects into properties dictioary (such as color, border, borderwidth etc), and these values are used in rendering all the time. And i didn't noticed heavy speed degradation. > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua(a)gmail.com] > Sent: Saturday, October 23, 2010 11:00 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] some patterns I would like to **kill** > > On 23 October 2010 17:13, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: >> Stef, >> >> Of course. Â But in terms of avoiding unintended consequences, just consider the points I raised. Â Some of the avoidance of instance variables (extensions, etc.) might have been a good idea with the gc at the time but is now an ugly hack, or that sparse storage tricks were over-used. >> > Well, one way or another you have to tame the complexity somehow. > Be it extra instvar, or putting it into extensions doesn't changes the > model's concept: you need a reference to some object > which is responsible for some specific stuff. > > >> Bill >> >> >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] >> Sent: Saturday, October 23, 2010 7:33 AM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] some patterns I would like to **kill** >> >> I think that if you have a container that contains morphs probably findA and other queries are useful. >> Now for a button that is also at the same place a field is the best. >> >> Stef >> >> >> On Oct 22, 2010, at 11:14 PM, Schwab,Wilhelm K wrote: >> >>> Stef, >>> >>> #respondsTo: - no argument. Â More defensive programming (aka masked bugs). Â Tests like this have their place, but are over-used in Squeak. >>> >>> Using #submorphs *might* be easier to defend. Â Morphs were designed to be usable in large numbers, and one might argue (playing Devil's Advocate here) that lookups are cheaper than the additional gc load. Â An instance variable could also cache stale information. Â Of course, for something that is accessed frequently, an instance variable avoids the lookup and I agree that it is cleaner and easier to read. >>> >>> Bill >>> >>> >>> >>> ________________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of stephane ducasse [stephane.ducasse(a)free.fr] >>> Sent: Thursday, October 21, 2010 4:47 PM >>> To: Pharo Development >>> Subject: [Pharo-project] some patterns I would like to **kill** >>> >>> Hi >>> >>> I was reading Pluggable and friends >>> I identified some patterns. >>> >>> >>> The respondsTo plague >>> Examples: >>> >>> color := self fillStyle asColor. >>> Â Â Â Â (self labelMorph respondsTo: #enabled:) >>> Â Â Â Â Â Â Â Â ifTrue: [self labelMorph enabled: self enabled]. >>> Â Â Â Â (self labelMorph respondsTo: #interactionState:) >>> Â Â Â Â Â Â Â Â ifTrue: [self labelMorph interactionState: self interactionState] >>> >>> (self labelMorph respondsTo: #enabled:) ifTrue: [ >>> Â Â Â Â self labelMorph enabled: aBoolean]. >>> >>> (self enabled not and: [self label isMorph and: [(self label respondsTo: #enabled:) not]]) >>> >>> >>> by construction a labelObject should be a morph and it should answer enabled: and the case where this is not the case should be fixed. >>> >>> >>> Using submorphs to avoid one single inst var makes code quite ugly to read: >>> >>> >>> labelMorph >>> Â Â Â Â "Answer the actual label morph." >>> >>> Â Â Â Â self hasSubmorphs ifFalse: [^nil]. >>> Â Â Â Â self firstSubmorph hasSubmorphs ifFalse: [^nil]. >>> Â Â Â Â ^self firstSubmorph firstSubmorph >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > 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 > > _______________________________________________ > 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.

Oct. 24, 2010

[Pharo-project] Deprecation policy (was: Re: Object>>at:modify:???)

by Levente Uzonyi

On Sat, 23 Oct 2010, Mariano Martinez Peck wrote: > On Sat, Oct 23, 2010 at 1:32 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr >> wrote: > >> Ok we can deprecate it. >> >> > ys, but please please please use deprecated: anExplanationString on: date > in: version Wouldn't it be easier to rely on method timestamps + a version cache, than spreading redundant information all over the place? Something like: Object >> deprecated: anExplanationString "Warn that the sending method has been deprecated." (Deprecation method: thisContext sender method explanation: anExplanationString on: (TimeStamp fromMethodTimeStamp: thisContext sender method timeStamp) date "Or something nicer") signal Deprecation class >> method: aCompiledMethod explanation: anExplanationString on: date ^self new method: aCompiledMethod explanation: anExplanationString on: date asString in: (SystemVersion alphaVersionAt: date) Someone has to implement #alphaVersionAt: (which is easy, but SystemVersion has to be modified). Finally the developement process has to follow some simple rules. Levente > > cheers > > mariano > > >> On Oct 22, 2010, at 11:04 PM, Hernan Wilkinson wrote: >> >>> In a 1.1 image I have, the class HttpRequest is using that message... >>> >>> On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse < >> stephane.ducasse(a)free.fr> wrote: >>> I would like to deprecate the following method since nobody use it. >>> What do you think? >>> >>> Stef >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> >>> -- >>> HernÃ¡n Wilkinson >>> Agile Software Development, Teaching & Coaching >>> Mobile: +54 - 911 - 4470 - 7207 >>> email: hernan.wilkinson(a)10Pines.com >>> site: http://www.10Pines.com >>> >>> _______________________________________________ >>> 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 >> >

Oct. 24, 2010

Re: [Pharo-project] Smells looking at collections

by Levente Uzonyi

On Sat, 23 Oct 2010, StÃ©phane Ducasse wrote: >> >> There was a discussion here a few weeks ago concerning a Trait I proposed called TComparable. It is the protocol of Magnitude bundled separately as a Trait, so any class can behave like Magnitude without having to inherit from Magnitude or use composition. You need only add "uses: TComparable" to the class template and then override its abstract methods as needed, and instances of your class will now be comparable. Association could use TComparable rather than inheriting from Magnitude, and, if the build system permits, Magnitude itself could be rewritten to use TComparable. Stef. approved of the idea and expressed a desire to see it in upcoming versions of Pharo, but I am not sure what the current status is. >> >> >> That's a nice solution, but it means that Traits have to be in the Kernel. I have three problems with Traits: >> 1) they are stateless >> 2) they are different from classes >> 3) incomplete tools support (this may be fixed in Pharo, but I doubt it is) > > 1) we build some code to see if we really need state and this is not that obvious and adding state is not trivial Not trivial? Maybe not, but only a little bit harder than trivial. > 2) well, this is difficult to get the money for the butter and the butter - we are trying. If you can compose classes the way you can add a trait to a class now with class and optional method level instance+class variable mapping, then you're done. It would be a lot simpler to use it _and_ it would also be a lot easier to implement it. Especially the tools part. > 3) again if nobody does anything and we just all cry on ourselves then nothing will happen. Tools are a must. No tools - no users. > > So for now identifying traits and learning is the way. Then we can refactor, redesign Well, Traits are in Squeak since 2006, IIRC they were available a few years earlier. So in the last X (at least 4) years the only good candidate to become a Trait was Magnitude. Levente > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 23, 2010