- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3153: MCVersionReader uses FileList registration

by Pavel Krivanek

http://code.google.com/p/pharo/issues/detail?id=3153 This is the next important patch that enables to load Monticello to PharoKernel. Cheers -- Pavel

Oct. 24, 2010

Re: [Pharo-project] Smells looking at collections

by Johan Brichau

On 24 Oct 2010, at 08:42, StÃ©phane Ducasse wrote: >> 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. PolyMorphic also uses traits. There are non-core projects that also use them, for example WebTester. I can also name several occassions in the development of our application, where we considered using traits to avoid code duplication. The only reason we didn't was because of a need for portability to GS. But if I understood correctly, it's quite possible that GS will support them in the future. Traits are being added to many other languages as well (e.g. traitsjs.org) It would be a shame to remove them from Squeak/Pharo Smalltalk now. just my 2 cents, Johan

Oct. 24, 2010

Re: [Pharo-project] Smells looking at collections

by Levente Uzonyi

On Sun, 24 Oct 2010, StÃ©phane Ducasse wrote: >>>> >> 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 If you mean that a CompiledMethod of a trait cannot be added to the class' method dictionary, than that's not an issue. The current Trait implementation was changed, because shared CompiledMethods caused other problems. If you mean that the same bytecodes can't be used, than that's neither a problem, because you can and should be compile the method again. Sharing trailer bytes may cause problems. So adding a method from a trait to a class is simply recompiling it in the class' context. Instance variables should be used by name during compilation. If there's a name collision then use the instance variable map I mentioned above. > - initialization of instances variables at the trait level and the composition at the class levele You can always rename a trait's method in your class. So if the trait has an #initialize method, then simply rename it to #initializeFooBar and send it from the class' #initialize method. Levente > >> >>> 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 > _______________________________________________ > 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

Yes there are some fun names in there: ice, yelowish, midnight, barney. Also some very 'human-excreta-related' ones: puke, vomit, poo, booger, ... But I chose not to pass a watch-out-for-the-children filter. (What would I do with Barney for example ? :-P ) On 24 Oct 2010, at 03:46, StÃ©phane Ducasse wrote: > 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 > > > _______________________________________________ > 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] Proposal: adding 261 named colors

by Johan Fabry

Yes if it doesn't make it in Pharo, it would be great that it gets in Moose. Stef, you closed the bug, does this mean it will be integrated ? On 24 Oct 2010, at 04:12, Tudor Girba wrote: > 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! > -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Oct. 24, 2010

[Pharo-project] a bit of fun

by StÃ©phane Ducasse

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

Oct. 24, 2010

[Pharo-project] problem with metacello in 1.2

by StÃ©phane Ducasse

Dale did something change on the server side? This is strange 199 - Issue 3048: MC method cache fix. Thanks Igor Stasenko 200 - Issue 2653: Editor cursor fix: remove autoclose in texteditor. - Issue 3128: AuthorRequestImprovement. Thanks Alain Plantec - Issue 3099: Create method in the debugger does not provides getter/setters implementors. Thanks Hernan Wilkinson 201 - Issue 1800: MenuIcons and ThemeIcons should be merged. Big thanks to alain plantec!!! 202 - Issue 3070: weird replacements in TextEditor. Thanks Alain Plantec!!! 203 - Issue 654: inconsistent highlight color. Thanks Alain Plantec - Issue 3101: Wrong Monticello packages initialization order. Thanks Pavel Krivanek 204 - Issue 2868: allClassesUsingPool: allClassesUsingPoolVariable: for systemNavigation - Issue 3046: BUG: LineMorph class>>from:to:color:width: returns a PolygonMorph - Issue 3130: MethodReference >> #isLocalSelector should not be part of Monticello package - Issue 3095: Character isLiteral is in wrong category - Issue 3134: Cleaning uniclasses from smartRefStream Jannik can you check with the Utilities trick I sent you to try Utilities readServer: Utilities serverUrls updatesThrough: 12200 saveLocally: false updateImage: true 199 200 201 202 203 204 so that we try to identify the problem Stef

Oct. 24, 2010

Re: [Pharo-project] What happened to demo mode?

by Alain Plantec

Le 24/10/2010 18:30, Serge Stinckwich a Ã©crit : > > > Le 24 oct. 2010 Ã 16:23, laurent laffont <laurent.laffont(a)gmail.com > <mailto:laurent.laffont@gmail.com>> a Ã©crit : > >> Added: http://book.pharo-project.org/book/CustomizingPharo/ > > Thank you Laurent, but i guess there is still a problem with demo mode > under Mac os x (the font used in browser code pane is not correct). yes ! unfortunately see Issue 2986. <http://code.google.com/p/pharo/issues/detail?id=2986> Alain > > -- Serge Stinckwich > > > _______________________________________________ > 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

[Pharo-project] Issue 3152: wrong Monticello package dependencies

by Pavel Krivanek

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

Oct. 24, 2010

Re: [Pharo-project] What happened to demo mode?

by Serge Stinckwich

Le 24 oct. 2010 Ã 16:23, laurent laffont <laurent.laffont(a)gmail.com> a Ã©crit : > Added: http://book.pharo-project.org/book/CustomizingPharo/ Thank you Laurent, but i guess there is still a problem with demo mode under Mac os x (the font used in browser code pane is not correct). -- Serge Stinckwich

Oct. 24, 2010