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

Re: [Pharo-project] Proposal: adding 261 named colors
by StÃ©phane Ducasse Oct. 24, 2010

Oct. 24, 2010

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

2 1

[Pharo-project] a bit of fun
by StÃ©phane Ducasse Oct. 24, 2010

Oct. 24, 2010

http://www.scribd.com/doc/38648591/About-Coders-new-version Stef

1 0

[Pharo-project] Issue 3152: wrong Monticello package dependencies
by Pavel Krivanek Oct. 24, 2010

Oct. 24, 2010

Hi, please integrate it soon: http://code.google.com/p/pharo/issues/detail?id=3152 Cheers, -- Pavel

1 0

[Pharo-project] [update 1.2] #12212
by Marcus Denker Oct. 24, 2010

Oct. 24, 2010

12212 ----- Issue 3137: Comment in Behavior >> allMethods is wrong Issue 3149: No setting in the setting browser Issue 3150: implementor of and sender of dont retrieve class side methods Issue 2340: Cursor for textEditor or new paragraph -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] some patterns I would like to **kill**
by StÃ©phane Ducasse Oct. 24, 2010

Oct. 24, 2010

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

3 6

[Pharo-project] #3149 and #3150
by Luc Fabresse Oct. 24, 2010

Oct. 24, 2010

A fix for : http://code.google.com/p/pharo/issues/detail?id=3149 http://code.google.com/p/pharo/issues/detail?id=3150 is attached. Tested in 12211. It was a bug introduced by my changes in SystemNavigation. Please, forgive me ;-) More unit tests are needed for SystemNavigation, SystemDictionary and SystemOrganization. I will write some. #Luc

1 0

[Pharo-project] [ANN] pre-build Core#12210
by Marcus Denker Oct. 24, 2010

Oct. 24, 2010

https://gforge.inria.fr/frs/download.php/27677/PharoCore-1.2-12210.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 2

[Pharo-project] [update 1.2] #12211
by Marcus Denker Oct. 24, 2010

Oct. 24, 2010

12211 ----- Issue 3141: nil when writeDefinition computing Issue 3147: How removing a class can broke DataStream/ReferenceStream/SmartRefStream Issue 3106: EToys resources relict in Form >> unhibernate Issue 3146: UIThemeStandardSqueaksmallDebugIcon is calling itself Issue 2525: SystemWindow out of focus color wrong Issue 1766: #objectForDataStream: should be in Package System-Serialization -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Proposal: adding 261 named colors
by StÃ©phane Ducasse Oct. 24, 2010

Oct. 24, 2010

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

1 0

Re: [Pharo-project] Smells looking at collections
by StÃ©phane Ducasse Oct. 23, 2010

Oct. 23, 2010

> > 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 2) well, this is difficult to get the money for the butter and the butter - we are trying. 3) again if nobody does anything and we just all cry on ourselves then nothing will happen. So for now identifying traits and learning is the way. Then we can refactor, redesign Stef

2 1

[Pharo-project] How removing a class can broke DataStream/ReferenceStream/SmartRefStream
by Mariano Martinez Peck Oct. 23, 2010

Oct. 23, 2010

Pharo core version: 12210 In Pharo 1.2, the class SoundBuffer was removed. DataStream >> initilize was modified, and just added an Smalltalk at: ifPresent: for such class. However, this broke DataStream and all its subclasses. This is because DataStream is chryptic, impossible to understand, and impossible to change. The changed affected when trying to write compiled methods (just by chance, because they were after in the list, of SoundBuffer). I've spent 3 hours to fix this bug grrrrr Fix in Inbox: Name: SLICE-Issue-3147-RomovingSoundBufferBrokeDataStream-MarianoMartinezPeck.1 Author: MarianoMartinezPeck Time: 23 October 2010, 10:07:35 pm UUID: c4f1cf01-b8b8-471d-b3c2-e67bdf08d8e5 Ancestors: Dependencies: System-Object Storage-MarianoMartinezPeck.112 Fix to issue 3147 <http://code.google.com/p/pharo/issues/detail?id=3147>

2 1

Re: [Pharo-project] akuhn/SUnit: run faster tests first & step through tests
by StÃ©phane Ducasse Oct. 23, 2010

Oct. 23, 2010

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

2 1

[Pharo-project] Complete an Array
by Simon De Baets Oct. 23, 2010

Oct. 23, 2010

Hello, I use Pharo 1.1 . I want to add a new element in an array that have a part of nil element. I want to add this new element on the first nil case. I produce this code |test isFact| test := Array new:5. isFact := False. test doWithIndex:[ :each :i | ((each isNil) & (isFact = False)) ifTrue:[ test at:i put:'plain'; isFact := True ] ]. test. But it doesn't function because they are two instruction in the ifTrue bolck. So my question is : "How can i put two instructions in an ifTrue block?" Thanks, -- Simon De Baets, Etudiant en MA1 informatique Ã l'ULB

3 2

[Pharo-project] Fwd: [Metacello] Re: problem with metacello in 1.2
by StÃ©phane Ducasse Oct. 23, 2010

Oct. 23, 2010

Begin forwarded message: > From: pharo-project-owner(a)lists.gforge.inria.fr > Date: October 23, 2010 9:31:33 PM GMT+02:00 > To: stephane.ducasse(a)gmail.com > Subject: Re: [Metacello] Re: [Pharo-project] problem with metacello in 1.2 > > You are not allowed to post to this mailing list, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > pharo-project-owner(a)lists.gforge.inria.fr. > > > From: stephane ducasse <stephane.ducasse(a)gmail.com> > Date: October 23, 2010 9:31:23 PM GMT+02:00 > To: metacello(a)googlegroups.com > Cc: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Metacello] Re: [Pharo-project] problem with metacello in 1.2 > > > yes we spent some time trying to find what would be the problem > but we could not identify one version (image, vm) on which we got constantly the problem accross variation. > > Stef > On Oct 23, 2010, at 8:09 PM, Tudor Girba wrote: > >> Several people had the same problem today: Fabrizio and Jorge in Bern, and Jannik in Lille. And they had it with different versions of Pharo 1.2. >> >> Cheers, >> Doru >> >> >> On 23 Oct 2010, at 19:05, Mariano Martinez Peck wrote: >> >>> >>> >>> On Sat, Oct 23, 2010 at 7:05 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >>> Wierd...now I have the same problem :( >>> >>> >>> On Sat, Oct 23, 2010 at 6:06 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >>> I think you were having a problem with the internet connection. Here it is fine. >>> Try again ;) >>> >>> 2010/10/23 Fabrizio Perin <fabrizio.perin(a)gmail.com> >>> Hi all, >>> i was trying to make Moose loadable into a 1.2 i did try to run the configuration of Moose and i got an error at the very beginning caused by the configuration of metacello. Am i missing something or it actually should work? I did expect to have problem but not with the configuration of metacello. >>> >>> I'm using a >>> >>> Pharo image 12203 on a Squeak4.2.5beta1U VM >>> >>> To reproduce the error just open the image and execute in a workspace: >>> >>> Gofer new >>> squeaksource: 'Moose'; >>> package: 'ConfigurationOfMoose'; >>> load. >>> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault >>> >>> Attached the log. >>> >>> Thanks, >>> Fabrizio >>> >>> _______________________________________________ >>> 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 >> >> "One cannot do more than one can do." >> >> >> > > > >

1 0

[Pharo-project] Object>>at:modify:???
by stephane ducasse Oct. 23, 2010

Oct. 23, 2010

I would like to deprecate the following method since nobody use it. What do you think? Stef

3 3

[Pharo-project] problem with metacello in 1.2
by Fabrizio Perin Oct. 23, 2010

Oct. 23, 2010

Hi all, i was trying to make Moose loadable into a 1.2 i did try to run the configuration of Moose and i got an error at the very beginning caused by the configuration of metacello. Am i missing something or it actually should work? I did expect to have problem but not with the configuration of metacello. I'm using a Pharo image 12203 on a Squeak4.2.5beta1U VM To reproduce the error just open the image and execute in a workspace: Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault Attached the log. Thanks, Fabrizio

3 4

Re: [Pharo-project] Pavel can you check :)
by StÃ©phane Ducasse Oct. 23, 2010

Oct. 23, 2010

When I clicked on a package, it got downloaded to the package cache using the writeDefinitions: method writeDefinitions: aCollection "initStream is an ugly hack until we have proper init defs" initializers := Dictionary new. (MCDependencySorter sortItems: aCollection) do: [:ea | ea accept: self] displayingProgress: 'Writing definitions...'. (Class superclassOrder: (initializers keys collect: [:each | Smalltalk classOrTraitNamed: each])) do: [:class | stream nextPutAll: (initializers at: class name) contents ]. Now it is bugging because initializers keys could contain a class that is not in the image and then put nil in the set The previous version of the method was: writeDefinitions: aCollection "initStream is an ugly hack until we have proper init defs" initStream := String new writeStream. (MCDependencySorter sortItems: aCollection) do: [:ea | ea accept: self] displayingProgress: 'Writing definitions...'. stream nextPutAll: initStream contents. - The previous version did not save initializers or may be different - Now the changes does not take into account classes that are not in the image. And this one should still be saved On Oct 23, 2010, at 12:22 PM, StÃ©phane Ducasse wrote: > Apparently when we browse > Compiler-eem.155 from the squeak trunk (ScriptLoader new addExtraRepositories) > > we get a problem because there is a nil in the set. > > Can you have a look? > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] "suggest" for the sprint
by Mariano Martinez Peck Oct. 23, 2010

Oct. 23, 2010

I also agree with Marcus idea: 'lets integrate much make us be more productive and progress faster'. I would love to have the Benjamin work. - Remove "Messages Names" and "Method FInder" and put his new tool. - Put his new changes browser. I would be really really nice to have this, even if it is not perfect yet. People may start to use it, report issues and give feedback. Thanks Mariano

1 0

[Pharo-project] Loading FFI into Pharo?
by Friedrich Dominicus Oct. 23, 2010

Oct. 23, 2010

In the end I'm trying to get ODBC running Pharo 1.1. I checked the docs and this should work: ScriptLoader loadFFI. for loading the FFI stuff. If I try that I get the message that this selector is unkwown. What am I supposed to do to get it known? Regards Friedrich

5 11

Oct. 23, 2010

http://code.google.com/p/pharo/issues/detail?id=3146

1 0

Oct. 23, 2010

smallDebugIcon "Answer a small debug icon." ^self smallDebugIcon Should be turned into ^ self smallErrorIcon Stef

1 0

Oct. 23, 2010

This is in 1.2 :) Stef On Oct 23, 2010, at 4:55 PM, jaayer wrote: > > > > > ---- On Fri, 22 Oct 2010 04:56:28 -0700 NicolÃ¡s Paez wrote ---- > >> Hi, I was looking at collection packages and I found that the class Association inherits from Magnitude.It is really strange for me because inheritance represent a "is-a" relation. >> >> >> So I looked that the documentation of each of these classes: >> >> >> Association: I represent a pair of associated objects--a key and a value. My instances can serve as entries in a dictionary. >> >> >> Magnitude: I'm the abstract class Magnitude that provides common protocol for objects that have >> the ability to be compared along a linear dimension, such as dates or times. >> Subclasses of Magnitude include Date, ArithmeticValue, and Time, as well as >> Character and LookupKey. >> >> >> >> Based on this, I think this relation is conceptually WRONG. >> If the idea is to reuse code then composition should be used instead of inheritance. >> >> >> >> >> What do you think? >> >> Saludos! >> Nico. >> blog: nicopaez.wordpress.com > > 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. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] [update 1.2] #12209
by Marcus Denker Oct. 23, 2010

Oct. 23, 2010

12209 ----- Issue 3049: ClassBuilderTest Issue 1746: ReferenceStream>>readOnlyFileNamed: is missing Issue 1981: Raising DuplicateError Exception in class builder Issue 2525: SystemWindow out of focus color wrong Issue 3143: To mark a test as an expected failure, one has to overwrite expectedFailures -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 2

[Pharo-project] [update 1.2] #12210
by Marcus Denker Oct. 23, 2010

Oct. 23, 2010

12210 ----- Issue 2653: Editor cursor fix Issue 3015: When a test is restarted in the debugger, #tearDown and #setUp and not send Issue 1853: NetNameResolver localHostAddress returns public or private address instead of loopback address. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Smells looking at collections
by NicolÃ¡s Paez Oct. 23, 2010

Oct. 23, 2010

Hi, I was looking at collection packages and I found that the class Association inherits from Magnitude. It is really strange for me because inheritance represent a "is-a" relation. So I looked that the documentation of each of these classes: *Association:* I represent a pair of associated objects--a key and a value. My instances can serve as entries in a dictionary. *Magnitude:* I'm the abstract class Magnitude that provides common protocol for objects that have the ability to be compared along a linear dimension, such as dates or times. Subclasses of Magnitude include Date, ArithmeticValue, and Time, as well as Character and LookupKey. Based on this, I think this relation is conceptually WRONG. If the idea is to reuse code then composition should be used instead of inheritance. What do you think? Saludos! Nico. blog: nicopaez.wordpress.com

4 4