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

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

by Alexandre Bergel

> Hi Alexandre, > > load: > > ...already loads latest stable version, but if the project hasn't > any declared stable version, it will throw a "no stable version > found" error, and you'll need to look for a version (using > #availableVersionsOf:) > of course, this can be improved... I will think on a way to do it. 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 :-) > 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? > > and no, I didn't implement a project remove... because metacello > (afaik) doesn't have it, and it was outside the scope of the loader. > Of course, I think it is a very important feature, but it will be > added in the future. Sure, no problem. Alexandre > > > On 2010-03-17 11:42:21 -0300, Alexandre Bergel <alexandre(a)bergel.eu> > said: > >> Hi Esteban, >> It looks cool. I tried and I was seen apparent problems. >> I think it would be useful to add >> loadLastVersionOf: >> loadLastStableVersionOf: >> I am not aware of Metacello details, but where is there a distinction >> between loading and upgrading? >> You do not have removeProject: or something? >> Cheers, >> Alexandre >> On 17 Mar 2010, at 09:23, Esteban Lorenzano wrote: >>> 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 (Adrian: I >>> really sorry for the delay... I know I promised this a lot of time >>> ago... but time is the tyrant :( ) >>> Cheers, >>> Esteban >>> _______________________________________________ >>> 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] MethodProperties question

by Mariano Martinez Peck

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

March 17, 2010

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

by StÃ©phane Ducasse

esteban excellent!!! Now how can we load code for Pharo1.0 which is different for Pharo1.1 and soon Pharo1.2.... you see what I mean. Ideally I would like to have the MetacelloRepository structured in a tree with versions 1.0/1.2.... so that in three years from now I can still load a version of something. The idea that we discuss with Dale is to be able to to a freeze of a configuration so that it copies all the dependent packages in a metacelloRepository. Stef > 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 (Adrian: I really sorry for the delay... I know I promised this a lot of time ago... but time is the tyrant :( ) > > Cheers, > Esteban > > > > _______________________________________________ > 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] packages :)

by StÃ©phane Ducasse

>> >> >> So I always need three information >> Class * method * extended|defined > > Not quite. > > At this moment, for any given class in a package, you can either have entries in the defined or in the extension dictionaries, but not in both in the same time. So, this is an indication that you can simply merge the two dictionaries. sure but you have them to filter after. > As soon as you add a method to a package, you know exactly if that method is defined or not by knowing whether the class is defined in that package. Yes this was the first implementation I did and it was boring to always check. Is the class defined or not. > Also, if you do have the methods in one dictionary, then you also won't have to care whether you moved the definition of a class between packages. Ummm I do not buy that. How? > Right now, if you move the definition of a class without touching the methods, you will have to ensure in the two packages that the methods that were defined are not extensions and the other way around. yes. > If you interpret the extension by looking at where the class is defined, then you do not lose anything. speed? Indeed I could merge all the methods into two dictionaries instead of four and always check the classes defined in the packages. but I will be doing includes: all the time. I can give a try. May be I will do another implementation to be able to measure. I will first remove the isExtension: > Yet another point is that I typically first want to know the methods of a class from a package. I do not want to know which is extended or which is not. So, I currently have to look it up in two dictionaries which is not necessarily optimal. you have the method methodForClass: for that, you get all the methods defined or extended for a class in a given package. > Or am I missing something?

March 17, 2010

Re: [Pharo-project] JPEGReadWriter and JPEGReadWriter2

by StÃ©phane Ducasse

PluginBasedJPEGReadWriter On Mar 17, 2010, at 2:11 PM, Mariano Martinez Peck wrote: > I read class comments and seem to be different, but I don't like the name at all. We should rename (or remove?) JPEGReadWriter2 to something better. > > we should merge them ? I have no idea...I just send a warning to you. > > 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] [ANN] Gofer Project Loader 1.0 (BETA)

by Henrik Johansen

On Mar 17, 2010, at 4:54 16PM, Alexandre Bergel wrote: >> Hi Alexandre, >> >> load: >> >> ...already loads latest stable version, but if the project hasn't any declared stable version, it will throw a "no stable version found" error, and you'll need to look for a version (using #availableVersionsOf:) >> of course, this can be improved... I will think on a way to do it. > > 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. > >> 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 :) Cheers, Henry

March 17, 2010

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

by Diogenes Moreira

Yessssssssssss.. Please 2010/3/17 Mariano Martinez Peck <marianopeck(a)gmail.com> > 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] [ANN] Gofer Project Loader 1.0 (BETA)

by Adrian Lienhard

> -1 to put it in Gofer. In my opinion, it is perfect as it is. > > +9999 to put it in PharoDev, but not in 1.0. We can put it when we start > building PharoDev 1.1 Makes sense Adrian

March 17, 2010

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

by Alexandre Bergel

Hi Esteban, It looks cool. I tried and I was seen apparent problems. I think it would be useful to add loadLastVersionOf: loadLastStableVersionOf: I am not aware of Metacello details, but where is there a distinction between loading and upgrading? You do not have removeProject: or something? Cheers, Alexandre On 17 Mar 2010, at 09:23, Esteban Lorenzano wrote: > 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 (Adrian: I > really sorry for the delay... I know I promised this a lot of time > ago... but time is the tyrant :( ) > > Cheers, > Esteban > > > > _______________________________________________ > 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] [ANN] Gofer Project Loader 1.0 (BETA)

by Mariano Martinez Peck

On Wed, Mar 17, 2010 at 3:30 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Hi Adrian, > > > On 2010-03-17 11:15:10 -0300, Adrian Lienhard <adi(a)netstyle.ch> said: > > Hi Esteban >> >> Looks cool! I haven't had time to test it out in depth yet, but here three >> questions: >> >> - does it keep memory of which projects are loaded? Is this what you refer >> to as "managed projects"? >> > > Yes, it keeps a list of "managed projects" (with itself as the first one) > so it can check for new versions, etc. For 1.1 would be cool to include, maybe, to implement the cleanUp method...regarding the latests integrations. There you can flush all managed projects. > > - would it make sense to integrate it into Gofer? >> > > I don't know... this is a "mixer" between Gofer and Metacello. If we > integrate it with Gofer core, suddenly we wil be creating a new dependence > package to add to core (Metacello)... of course, Metacello can be loaded "at > first project load" just like now "at first configuration loaded", but I > don't know if this is desirable... your choice more than mine :) > What will be cool is to include the gofer project loader into PharoDev > distributions. > > -1 to put it in Gofer. In my opinion, it is perfect as it is. +9999 to put it in PharoDev, but not in 1.0. We can put it when we start building PharoDev 1.1 > > > > Cheers, > Esteban > > > > _______________________________________________ > 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