- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] Gofer Project Loader 1.0 (BETA)
by Dale Henrichs March 17, 2010

March 17, 2010

Alexandre, load involves loading a project into an image in which the project does not exist. upgrade involves loading a project into an image in which the project already is loaded. Loading is straightforward ... it is what we do all of the time. Add a bunch of classes and methods, then run the #initialize methods for the new classes. Upgrading is interesting because besides adding/removing classes and methods, you have to worry about completely unloading packages that are no longer part of the project. You also have to worry about the fact that new classes will get there #initialize methods, but preexisitng classes will not ... which can lead to interesting results. This may lead to pre/post upgrade doits... Remove is interesting because you have to also consider removing any projects that are dependent upon the project being removed. Once Metacello 1.0 is released I start working on adding upgrade and remove to Metacello. Dale ----- "Alexandre Bergel" <alexandre(a)bergel.eu> wrote: | 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 | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | | | | | | | _______________________________________________ | 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] Removal of requires calculation code
by Adrian Lienhard March 17, 2010

March 17, 2010

I finally managed to finish this task, which I started at last week's sprint. This change removes the required/provided selectors computation code that was in the Traits package for historical reasons. This removes 17 classes with about 240 methods from PharoCore. I re-packaged the removed code and put it on SqueakSource: http://www.squeaksource.com/Requires.html Info for integrators: Preamble: ------------ SystemChangeNotifier uniqueInstance noMoreNotificationsFor: RequiredSelectors current. SystemChangeNotifier uniqueInstance noMoreNotificationsFor: ProvidedSelectors current SystemChangeNotifier uniqueInstance noMoreNotificationsFor: LocalSends current. Changes (in inbox): ------------ Name: Kernel-AdrianLienhard.622 Author: AdrianLienhard Time: 17 March 2010, 8:57:59 pm UUID: b3776db1-b0c0-4e01-808b-0090fc7a42dc Ancestors: Kernel-StephaneDucasse.621, Kernel-AdrianLienhard.615 Name: Traits-AdrianLienhard.363 Author: AdrianLienhard Time: 17 March 2010, 9:06:32 pm UUID: 6d4af177-0e6f-4db1-bf30-1fd62c10c298 Ancestors: Traits-StephaneDucasse.362, Traits-AdrianLienhard.359 Name: ScriptLoader11-AdrianLienhard.305 Author: AdrianLienhard Time: 17 March 2010, 9:00:43 pm UUID: 0eae5794-e74e-4d4d-a6e0-8e3a8b641af0 Ancestors: ScriptLoader11-StephaneDucasse.304, ScriptLoader11-AdrianLienhard.290 Name: Tests-AdrianLienhard.136 Author: AdrianLienhard Time: 17 March 2010, 9:05:49 pm UUID: 7dd01882-2b6e-4dce-8139-caf9cc96caf4 Ancestors: Tests-StephaneDucasse.135, Tests-AdrianLienhard.125 To track this change: http://code.google.com/p/pharo/issues/detail?id=2160 Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

3 2

[Pharo-project] [ANN] Gofer Project Loader 1.0 (BETA)
by Esteban Lorenzano March 17, 2010

March 17, 2010

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

9 15

Re: [Pharo-project] [ANN] Gofer Project Loader 1.0 (BETA)
by Dale Henrichs March 17, 2010

March 17, 2010

----- "Alexandre Bergel" <alexandre(a)bergel.eu> wrote: | > load involves loading a project into an image in which the project | > does not exist. | > upgrade involves loading a project into an image in which the | > project already is loaded. | > | > Loading is straightforward ... it is what we do all of the time. Add | > a bunch of classes and methods, then run the #initialize methods for | > the new classes. | > | > Upgrading is interesting because besides adding/removing classes and | > methods, you have to worry about completely unloading packages that | > are no longer part of the project. You also have to worry about the | > fact that new classes will get there #initialize methods, but | > preexisitng classes will not ... which can lead to interesting | > results. This may lead to pre/post upgrade doits... | | I easily understand the difference. I was just wondering whether load: | cannot do an update: if the package is present already. Maybe as I | user I should not take care whether a package is already present | before loading it. Just a thought. That is probably a good idea ... the less someone has to think before running a script the better, as long as the 'right thing is done'.

1 0

[Pharo-project] May be there is a problem with ChangeSet
by StÃ©phane Ducasse March 17, 2010

March 17, 2010

Apparently I have methods that are cut.... and I cannot load the file back.... I cannot save with MC either. :( Stef

1 1

[Pharo-project] Fix 1973: PluggableTreeMorph class#on:list:selected:changeSelected: inconsistency
by laurent laffont March 17, 2010

March 17, 2010

in PharoInbox. http://code.google.com/p/pharo/issues/detail?id=1973 Laurent Laffont

1 0

[Pharo-project] Code Freeze 1.1?
by Marcus Denker March 17, 2010

March 17, 2010

Hi, Now with 1.0 done, I think we should think about freezing 1.1. The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other thing is that 1.1 did change quite some things that have impact on external code (Preferences, as an example). So I think we should -> start slowing down on 1.1 (Stef suggested that already) -> start polishing (tests...) -> start to look at the Dev image. -> Official code freeze end of March. -> Release if possible end of April (this of course depends on the state of things). Any reasons against? Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

8 19

[Pharo-project] eCompletion works on Pharo 1.1
by Lukas Renggli March 17, 2010

March 17, 2010

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

2 1

[Pharo-project] [update 1.1] #11277
by stephane ducasse March 17, 2010

March 17, 2010

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

1 0

[Pharo-project] Pharo 1.1 deprecation fixes for Refactoring Engine
by Lukas Renggli March 17, 2010

March 17, 2010

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

2 1