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

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

by StÃ©phane Ducasse

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

March 17, 2010

Re: [Pharo-project] Remove Pen and PenPointRecorder ??

by StÃ©phane Ducasse

+ 1! Even with a bit of nostalgia :) But this is the way to go. Propose a change/slice + a ticket and we get it in. Stef On Mar 17, 2010, at 2:33 PM, Mariano Martinez Peck wrote: > 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. > > Cheers > > Mariano > _______________________________________________ > 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] Code Freeze 1.1?

by StÃ©phane Ducasse

Yes but 1.0 should be out any time soon :) and if we say end of march may be it will be end of april :) Stef > <stephane.ducasse(a)inria.fr> wrote: >> this is parallel and orthogonal. >> and freezing means less radical changes, stabilization. > > The problem I see is that as soon as 1.1 gets frozen, people will move > toward 1.2 to add the cool stuffs and 1.0 will get even less interest > than now (which is already quite low compared to what 1.1 gets). At > some point, we have to do the remaining 2% that close the stuff and > let us move forward. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > 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] Faster Sets and Pharo 1.1?

by Ralph Boland

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

March 17, 2010

Re: [Pharo-project] MethodProperties question

by StÃ©phane Ducasse

yeap open a ticket Stef On Mar 17, 2010, at 4:46 PM, Mariano Martinez Peck wrote: > Hi folks (Marcus ?). > > I saw this class was removed, however: > > 1) The class MethodPropertiesTest is still alive. Shouldn't we remove it ? > > 2) After evaluating "ScriptLoader new cleanUpForRelease" > > if I inspect > > SystemNavigation default obsoleteClasses > > I have a "AnObsoleteMethodProperties" > > Cheers > > Mariano > > _______________________________________________ > 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 Brian Brown

On Mar 17, 2010, at 7:38 AM, Lukas Renggli wrote: >> 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 >

March 17, 2010

Re: [Pharo-project] Code Freeze 1.1?

by Damien Cassou

On Wed, Mar 17, 2010 at 1:20 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > this is parallel and orthogonal. > and freezing means less radical changes, stabilization. The problem I see is that as soon as 1.1 gets frozen, people will move toward 1.2 to add the cool stuffs and 1.0 will get even less interest than now (which is already quite low compared to what 1.1 gets). At some point, we have to do the remaining 2% that close the stuff and let us move forward. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

March 17, 2010

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

by Alexandre Bergel

>> >> Excellent! >> When you load something, it would be nice to provide some feedback >> on which version is loaded, and which one is available. >> I am picky, I know :-) > > Belongs in complimentary UI / Logging packages, imo. > As long as the ProjectLoader raises appropriate announcements (cough > cough), it shouldn't be hard to separate (optional) feedback from > the actual loading actions. Exactly. For the MooseLoader, we have a transcript that shows up with the relevant information. This is not perfect, but it is useful. Indeed, having a set of announcement will definitly be a good move. >>> upgrade >>> >>> loads new versions of an already present project (if there are >>> newer versions on a configuration). >> >> But is there a situation where I would prefer an upgrade instead of >> a load? > > It doesn't reinstall if the latest version is already loaded? > Also, if mcd's between two versions were available, it could > potentially install much faster :) Yes, but load: could not check whether the package is already installed, and in that case just do an upgrade? Alexandre > > Cheers, > Henry > _______________________________________________ > 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

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

by Mariano Martinez Peck

> > 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] [Metacello] [ANN] Gofer Project Loader 1.0 (BETA)

by Miguel Enrique CobÃ¡ Martinez

El miÃ©, 17-03-2010 a las 10:38 -0300, Esteban Lorenzano escribiÃ³: > Hi, > I want to announce the immediate release of GoferProjectLoader, a > Gofer extension to manage Metacello configurations. > For all who want to know quickly what is this, here is a small > synopsis: > > > GoferProjectLoader is a loader for Metacello configurations > (A metacello configuration is a full project load tool, > including package/project dependencies with it corresponding > versions). > GoferProjectLoader automatically scan projects stored > on MetacelloRepository, but you can add your private repositories as > well. > GoferProjectLoader responsibilities include: > > > 1) Install project versions and keep track of them. > 2) Update configurations and upgrade projects (if desired). > > > GoferProjectLoader relies on Metacello and Gofer to perform this > tasks (In fact, It can be thought as a Gofer extension to > understand Metacello packages). > > > To load GoferProjectLoader, you need to do: > > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfGoferProjectLoader'; > load. > > > ConfigurationOfGoferProjectLoader project lastVersion load. > > > With this... you'll never need again to perform once and again > this repetitive configuration... instead, you can do things like: > > > Gofer project > load: 'Seaside30'; > load: 'Pier2'. > > > You can see the full documentation here: > http://www.smallworks.com.ar/en/community/GoferProjectLoader > > > Now I'm working on the promised page for configurations... Cool, very good work. Now, what is the possibility to add this to the PharoCore 1.0 release? > > > Cheers, > Esteban -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 17, 2010