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

[Pharo-project] recategorizing all the categories...

by StÃ©phane Ducasse

hi guys I wanted to know if one you try tried to automatically recategorized all the methods of the system. Because I'm tired to get this as yet unclassified in my face. I looks to my like dirt in the street. Wanna get clean... Stef

March 17, 2010

Re: [Pharo-project] eCompletion works on Pharo 1.1

by StÃ©phane Ducasse

Excellent!!!! This is good when you write your phd, because you could even clean the fridge or anything else :). Lukas what could be good is to check the current user of preferences in Pharo1.1 Stef On Mar 17, 2010, at 8:29 PM, Lukas Renggli wrote: > I fixed eCompletion (and all its long broken tests) to work on Pharo > 1.0 and 1.1. > > http://source.lukas-renggli.ch/unsorted/ECompletion-lr.113 > > Similar to the refactoring engine the new settings framework is used > now. This means to set the preferences you either use Pharo 1.1 or > manually use the accessors on the class side of ECPreference. > > Name: ECompletion-lr.113 > Author: lr > Time: 17 March 2010, 8:20:03 pm > UUID: 0d16cf1e-ff4b-4674-8045-d10cfc2e25d6 > Ancestors: ECompletion-lr.112 > > - fixed all tests > - updated to Pharo 1.1 > > Lukas > > -- > 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

March 17, 2010

[Pharo-project] [update 1.1] #11277

by stephane ducasse

11277 ----- - Issue 2151: Cleaning of and test for MessageTally. Thanks Alexandre - Issue 2158: Pharo 1.1 deprecation fixes for Refactoring Engine. Thanks Lukas. - SunitGUI fixed priority of coloring test result: if there are errors then red else if there are failures then yellow else -> green - implemented RxMatcher>>split: thanks Fabrizio Stef

March 17, 2010

[Pharo-project] eCompletion works on Pharo 1.1

by Lukas Renggli

I fixed eCompletion (and all its long broken tests) to work on Pharo 1.0 and 1.1. http://source.lukas-renggli.ch/unsorted/ECompletion-lr.113 Similar to the refactoring engine the new settings framework is used now. This means to set the preferences you either use Pharo 1.1 or manually use the accessors on the class side of ECPreference. Name: ECompletion-lr.113 Author: lr Time: 17 March 2010, 8:20:03 pm UUID: 0d16cf1e-ff4b-4674-8045-d10cfc2e25d6 Ancestors: ECompletion-lr.112 - fixed all tests - updated to Pharo 1.1 Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 17, 2010

Re: [Pharo-project] Pharo 1.1 deprecation fixes for Refactoring Engine

by StÃ©phane Ducasse

Thanks lukas I will integrate that. I'm going over SystemDictionary and checking everything carefully. Stef On Mar 17, 2010, at 7:32 PM, Lukas Renggli wrote: > Please integrate: <http://code.google.com/p/pharo/issues/detail?id=2158> > > Name: System-Support-LukasRenggli.263 > Author: lr > Time: 17 March 2010, 7:30:53 pm > UUID: a7e86013-b12d-4d66-bc45-92990f5813f5 > Ancestors: System-Support-StephaneDucasse.262 > > - added 3 more deprecated methods that are required in SmalltalkImage > by the refactoring engine: #keyAtValue:, #keysAndValuesDo: and > #select: > > -- > 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

March 17, 2010

Re: [Pharo-project] Keep GOING (was: Remove Pen and PenPointRecorder ??)

by Alexandre Bergel

Very well said Stef Alexandre On 17 Mar 2010, at 13:54, StÃ©phane Ducasse wrote: > Thanks Brian. > Brian you know we are not against Squeak. We are for beauty and > quality. :) (I always liked etoys but hated its implementation). > So welcomed on pharo. > > Now I said that I will not be negative against squeak and I will > apply my resolution (which is easy because I cleaned some of > my rancor recently - I have a red pill for those interested :)) > > I think that if Squeak would build the next century multimedia > system I would be **really** happy. Now if they would build it > on take pharocore as a core then we could join forced. I do not say > that for my ego or for the fame of Pharo but more > in regards to people such as nicolas that published in both > communities. > > Now we know where pharo is heading but this is not clear for Squeak. > May be they like that (no pun) and this is good for them, > this is ok too. > Now if they would take the Multimedia space and make it excellent (I > men truly excellent, clean and lean code), good abstraction (cairo, > pango....) then we would be in a win-win situation. We could focus > on the infrastructure and they would be the sexy Squeak. > But for this to happen people should decide to do it and accept that > they are not alone. > > Stef > > >>>> Hi folks, what do you think about removing Pen and >>>> PenPointRecorder ? >>>> At least, to remove it from the core and let them somewhere in a >>>> repository. >>> >>> Yes please, kill that crap. >>> >> >> Haha! This is why Pharo is going in the right direction! Keep up >> the good work of cleaning, cleaning, cleaning, harvesting good >> ideas and making the system better. >> >> A friend of mine who worked with Squeak several years ago just a >> few days ago was looking at the object model in Pharo and said >> "Wow! That is so much cleaner and easier to look through now!" >> >> These are worthy directions that we go in. Thanks Stef, Lukas, >> Alexandre, Mariano, Doru, Marcus, Torsten, Henrik, Sig, Damien, >> etc, etc, etc... >> >> - Brian >> >> >> >>> There seem to be a couple of references though. >>> >>> Lukas >>> >>> -- >>> 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 > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 17, 2010

[Pharo-project] Pharo 1.1 deprecation fixes for Refactoring Engine

by Lukas Renggli

Please integrate: <http://code.google.com/p/pharo/issues/detail?id=2158> Name: System-Support-LukasRenggli.263 Author: lr Time: 17 March 2010, 7:30:53 pm UUID: a7e86013-b12d-4d66-bc45-92990f5813f5 Ancestors: System-Support-StephaneDucasse.262 - added 3 more deprecated methods that are required in SmalltalkImage by the refactoring engine: #keyAtValue:, #keysAndValuesDo: and #select: -- Lukas Renggli http://www.lukas-renggli.ch

March 17, 2010

Re: [Pharo-project] [Seaside-dev] [ANN] Gofer Project Loader 1.0 (BETA)

by Miguel Enrique CobÃ¡ Martinez

El miÃ©, 17-03-2010 a las 18:26 +0000, Michael Roberts escribiÃ³: > Pharo core is in release candidate phase so only critical bug fixes > should go in. Thanks mike Ok, just curious :) > > On Wednesday, March 17, 2010, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: > > > > > > > > Cool, very good work. > > Now, what is the possibility to add this to the PharoCore 1.0 release? > > > > > > > > Look the conversation in Pharo maling list. > > > > Form my opinion, it shouldn't be loaded in core and I wouldn't put it in PharoDev 1.0, but in 1.1. > > > > Cheers > > > > Mariano > > > > > >> > >> > >> Cheers, > >> Esteban > > > > -- > > Miguel CobÃ¡ > > http://miguel.leugim.com.mx > > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 17, 2010

Re: [Pharo-project] [Seaside-dev] [ANN] Gofer Project Loader 1.0 (BETA)

by Michael Roberts

Pharo core is in release candidate phase so only critical bug fixes should go in. Thanks mike On Wednesday, March 17, 2010, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > Cool, very good work. > Now, what is the possibility to add this to the PharoCore 1.0 release? > > > > Look the conversation in Pharo maling list. > > Form my opinion, it shouldn't be loaded in core and I wouldn't put it in PharoDev 1.0, but in 1.1. > > Cheers > > Mariano > > >> >> >> Cheers, >> Esteban > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > >

March 17, 2010

Re: [Pharo-project] Faster Sets and Pharo 1.1?

by StÃ©phane Ducasse

Thanks Ralph Levente, nicolas, henrik can you help us to take a good decision. I'm not precise enough on that topic and its implications. What I would love it to have Faster Set Levente is it dependent on hash changes that martin is working on? Stef On Mar 17, 2010, at 6:39 PM, Ralph Boland wrote: > When I released my FasterSets package it was too late > for consideration for Pharo 1.0 so it was stated that it would be reconsidered > for Pharo 1.1. > > Of course, since my release, Levente has rewritten my version of FasterSets > from scratch and also made many other changes to Sets. > > So I am wondering what the status of FasterSets is with respect to Pharo 1.1: > > a) FasterSets is not wanted in Pharo. > b) You will use my version of FasterSets in Pharo 1.1. > c) You will use Levente's version of FasterSets and perhaps his many other > changes to Sets/Dictionaries in Pharo 1.1. > > Regards, > > Ralph Boland > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 17, 2010