February 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] shout for pharo 1.2: Please help.

by laurent laffont

Hi, I've remembered that ProfStef has a dependency on Shout. In version 1.6 (current stable) I have: spec for: #pharo do: [ spec project: 'Shout' with: '1.2.2'; can it be a problem ? If I remove it Metacello validator raises a critical warning. Laurent On Mon, Feb 28, 2011 at 8:07 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Yes but pharo was still loading the version 1.2.1 > So normally the latest configurationOfPharo and shout are fixed and > working. > Can you confirm that? > > Stef > On Feb 28, 2011, at 5:30 AM, Francisco Ortiz PeÃ±aloza wrote: > > > Hi Stef don't know if you already solve this, i created a 1.2.2 > > version of ConfigurationOfShout referencing some changes i made to > > shout to work with Editor changes. > > > > There're like five new versions since that and it's currently working > > with PharoCore 1.2 cause i tested a lot :) > > > > Cheers, > > Francisco > > > > > > > > On Sun, Feb 27, 2011 at 7:26 PM, StÃ©phane Ducasse > > <stephane.ducasse(a)inria.fr> wrote: > >> Ok > >> For me I just wanted to check if I can load shout. > >> Now it is just breaking on Dev Toolset>> > >> SHWorkspace open. > >> > >> I still do not understand how the correct version of shout was loaded > before. > >> Since Pharo was referencing 1.2.1 which was referencing jannik old > version > >> and the one with the fix of benjamin was not loaded. > >> > >> So I should adapt the baseline to load the correct test in 1.2.2 > >> The problem is that testing all the setup takes 35 min. > >> > >> Stef > >> > >> > >>> So Stef, I looked at ConfigurationOfPharo-StephaneDucasse.139 and I > noticed that you commented out some package specs for 1.2-beta2 ... you need > to be aware that commenting them out does not prevent those packages from > being loaded .... > >>> > >>> To make structural changes you need to remove the package spec from > 1.2-beta2 _and_ remove the package from 1.2-baseline. > >>> > >>> The specification for Shout Tests in 1.2-beta2 specifies the mcz file > to load. By commenting out the spec and leaving the spec in 1.2-baseline you > are telling Metacello to load the latest version of the Shout Tests > package.. > >>> > >>> Since 1.2-baseline is already shared by multiple versions, one way to > remove Shout Tests for version 1.2-beta2, is to create a 1.2-beta2-baseline > that does not include Shout Tests... > >>> > >>> You comment says that you don't know which version of the Shout Tests > to load, but by looking at 1.2-beta2-baseline, Shout Tests is referencing > the same project as Shout with a different load directive so it is correct > to use the save version as Shout. > >>> > >>> In a normal case I would recommend that you use the validator to look > at the configuration and fix those issues, but there _are_ a number of > validation issues with ConfigurationOfPharo already (which depending on what > other changes you have made might actually be contributing to the problem > ... There were also validation issues ConfigurationOfShout ... so you might > have hit a "perfect storm" of validation issues .. > >>> > >>> I have merged your changes into my working copy and I'll be doing a > test load shortly so perhaps I'll be able to observe some of the problems > first hand .. > >>> > >>> Dale > >>> > >>> On Feb 27, 2011, at 8:30 AM, StÃ©phane Ducasse wrote: > >>> > >>>> Ok > >>>> I do not understand how it loaded before because > >>>> I got a duplicate instance warning raised (even if the class > loaded was empty - I do not get it) > >>>> So I remove the empty package, fixing the version and the > baseline... > >>>> > >>>> Now I have the decompiler popping windows.... problem > >>>> Today this is tedious. > >>>> For a fix of 1 min I already spent 2 hours to try to load a > configuration. > >>>> > >>>> Stef > >>>> > >>>> > >>>>> Stef, > >>>>> > >>>>> I will try to take a look at your issue today along with testing out > the configuration fixes I have pending ... both Pharo and Shout had > configuration issues, but I can't say that your particular issue is related > ... yet. > >>>>> > >>>>> Dale > >>>>> > >>>>> On Feb 27, 2011, at 7:57 AM, StÃ©phane Ducasse wrote: > >>>>> > >>>>>> Hi guys > >>>>>> > >>>>>> I modified > >>>>>> > >>>>>> version 1.2.1 of ConfigurationOfShout to load my version > >>>>>> Shout-sd.101 (apparently lot of comments were removed between > Benjamin.100 and Benjamin.101 - strange) > >>>>>> > >>>>>> > >>>>>> In ConfigurationOfPharo there is > >>>>>> > >>>>>> project: 'Shout' with: '1.2.1'; > >>>>>> > >>>>>> > >>>>>> Now in ConfigurationOfShout there are > >>>>>> > >>>>>> version122: spec <version: '1.2.2' imports: #('1.1-baseline')> spec > for: #common do: [ spec blessing: #development. spec author: 'Francisco > Ortiz PeÃ±aloza'. spec description: 'Shout Changes for 1.2 using new > SmalltalkEditor'. ]. > >>>>>> > >>>>>> > >>>>>> version121: spec > >>>>>> <version: '1.2.1' imports: #('1.1-baseline')> > >>>>>> > >>>>>> spec for: #common do: [ > >>>>>> spec blessing: #development. > >>>>>> spec author: 'Stephane Ducasse'. > >>>>>> spec description: 'Shout for 1.2'. > >>>>>> ]. > >>>>>> > >>>>>> > >>>>>> When I load the latest stable of Pharo > >>>>>> > >>>>>> ((Smalltalk globals at: #ConfigurationOfPharo) project version: > #stable) load > >>>>>> > >>>>>> I get an error due to a duplicate (probably the instance variable of > pluggableShout.....). > >>>>>> Probably loading the wrong package. > >>>>>> > >>>>>> So I do not know what to do and lost my time. > >>>>>> > >>>>>> Stef > >>>>> > >>>>> > >>>> > >>>> > >>> > >>> > >> > >> > >> > > >

Feb. 28, 2011

Re: [Pharo-project] introducing RPackage :)

by StÃ©phane Ducasse

On Feb 28, 2011, at 2:08 AM, Carla F. Griggio wrote: > I'll try it with smallUML, it would be great to link diagrams to a package instead of a special class like it's done now :) But pay attention the package is an object and you will still need to put the spec of your diagram somewhere. And I still would love to have smallUML improved to the point we can use it to document all the pharo package. > > On Sat, Feb 26, 2011 at 6:07 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: > Hi, > > There is also a nighty build in hudson server. > > Cheers, > Jannik > > On Feb 26, 2011, at 21:48 , StÃ©phane Ducasse wrote: > > > > > On Feb 26, 2011, at 8:12 PM, Tudor Girba wrote: > > > >> Hi, > >> > >> We use RPackage in Moose, and it works fine. We only encountered a small problem raised when renaming a class, but Cyrille fixed that, too. I am quite confident in it. > >> > >> The way to load it is like this (different repo): > >> Gofer new > >> squeaksource: 'PharoTaskForces'; > >> package: 'ConfigurationOfRPackage'; > >> load. > >> (Smalltalk at: #ConfigurationOfRPackage) perform: #loadDefault. > >> > >> The translation of SystemChangeNotifier into Announcements happens in SystemAnnouncements package. > > > > thanks doru I will talk with cyrille monday. > > > >> > >> Just a note, until we can remove the SystemChangeNotifier, we have to first get Monticello work with RPackage and > > > > What do you mean by "we have to first get Monticello work with RPackage " It does not? > > > > I will have a look. > > > >> SystemAnnouncements. Afterwards, we should hook Announcements directly in the system, and yet afterwards remove the categories and get the tools work with RPackage. > >> > >> Cheers, > >> Doru > >> > >> > >> On 26 Feb 2011, at 18:59, StÃ©phane Ducasse wrote: > >> > >>> Hi guys > >>> > >>> I would like to give a try to introduce RPackage = a complete rewrite of PackageInfo. > >>> Moose people use it and I will sync with them to know. > >>> > >>> It would be great if some of you could load and play with the system > >>> > >>> > >>> Gofer new > >>> squeaksource: 'PharoInbox'; > >>> package: 'ConfigurationOfRPackage'; > >>> load. > >>> (Smalltalk at: #ConfigurationOfRPackage) perform: #loadDefault. > >>> > >>> Note that RPackage is based on announcement. So there is just one place that register to systemNotifier. > >>> So one of the following goal is to remove SystemChangeNotifier and replace it with announcement. > >>> > >>> Stef > >>> > >>> > >> > >> -- > >> www.tudorgirba.com > >> > >> "Every thing should have the right to be different." > >> > >> > >> > >> > > > > > > >

Feb. 28, 2011

Re: [Pharo-project] Metacello Configuration Pharo1.2 solo sprint ... status

by StÃ©phane Ducasse

thanks! On Feb 28, 2011, at 6:51 AM, Dale Henrichs wrote: > I've just finished copying the cleaned up configurations up to MetacelloRepository. > > All of the configurations that are referenced in ConfigurationOfPharo validate clean ... > > I loaded the config into a PHaroCore image, but had a number of failed tests, but I am running on a mac and I seem to remember that there were still some failing tests on the mac ... > > I'll check on the hudson results first thing tomorrow morning to double check .. > > Dale >

Feb. 28, 2011

Re: [Pharo-project] shout for pharo 1.2: Please help.

by StÃ©phane Ducasse

Yes but pharo was still loading the version 1.2.1 So normally the latest configurationOfPharo and shout are fixed and working. Can you confirm that? Stef On Feb 28, 2011, at 5:30 AM, Francisco Ortiz PeÃ±aloza wrote: > Hi Stef don't know if you already solve this, i created a 1.2.2 > version of ConfigurationOfShout referencing some changes i made to > shout to work with Editor changes. > > There're like five new versions since that and it's currently working > with PharoCore 1.2 cause i tested a lot :) > > Cheers, > Francisco > > > > On Sun, Feb 27, 2011 at 7:26 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Ok >> For me I just wanted to check if I can load shout. >> Now it is just breaking on Dev Toolset>> >> SHWorkspace open. >> >> I still do not understand how the correct version of shout was loaded before. >> Since Pharo was referencing 1.2.1 which was referencing jannik old version >> and the one with the fix of benjamin was not loaded. >> >> So I should adapt the baseline to load the correct test in 1.2.2 >> The problem is that testing all the setup takes 35 min. >> >> Stef >> >> >>> So Stef, I looked at ConfigurationOfPharo-StephaneDucasse.139 and I noticed that you commented out some package specs for 1.2-beta2 ... you need to be aware that commenting them out does not prevent those packages from being loaded .... >>> >>> To make structural changes you need to remove the package spec from 1.2-beta2 _and_ remove the package from 1.2-baseline. >>> >>> The specification for Shout Tests in 1.2-beta2 specifies the mcz file to load. By commenting out the spec and leaving the spec in 1.2-baseline you are telling Metacello to load the latest version of the Shout Tests package.. >>> >>> Since 1.2-baseline is already shared by multiple versions, one way to remove Shout Tests for version 1.2-beta2, is to create a 1.2-beta2-baseline that does not include Shout Tests... >>> >>> You comment says that you don't know which version of the Shout Tests to load, but by looking at 1.2-beta2-baseline, Shout Tests is referencing the same project as Shout with a different load directive so it is correct to use the save version as Shout. >>> >>> In a normal case I would recommend that you use the validator to look at the configuration and fix those issues, but there _are_ a number of validation issues with ConfigurationOfPharo already (which depending on what other changes you have made might actually be contributing to the problem ... There were also validation issues ConfigurationOfShout ... so you might have hit a "perfect storm" of validation issues .. >>> >>> I have merged your changes into my working copy and I'll be doing a test load shortly so perhaps I'll be able to observe some of the problems first hand .. >>> >>> Dale >>> >>> On Feb 27, 2011, at 8:30 AM, StÃ©phane Ducasse wrote: >>> >>>> Ok >>>> I do not understand how it loaded before because >>>> I got a duplicate instance warning raised (even if the class loaded was empty - I do not get it) >>>> So I remove the empty package, fixing the version and the baseline... >>>> >>>> Now I have the decompiler popping windows.... problem >>>> Today this is tedious. >>>> For a fix of 1 min I already spent 2 hours to try to load a configuration. >>>> >>>> Stef >>>> >>>> >>>>> Stef, >>>>> >>>>> I will try to take a look at your issue today along with testing out the configuration fixes I have pending ... both Pharo and Shout had configuration issues, but I can't say that your particular issue is related ... yet. >>>>> >>>>> Dale >>>>> >>>>> On Feb 27, 2011, at 7:57 AM, StÃ©phane Ducasse wrote: >>>>> >>>>>> Hi guys >>>>>> >>>>>> I modified >>>>>> >>>>>> version 1.2.1 of ConfigurationOfShout to load my version >>>>>> Shout-sd.101 (apparently lot of comments were removed between Benjamin.100 and Benjamin.101 - strange) >>>>>> >>>>>> >>>>>> In ConfigurationOfPharo there is >>>>>> >>>>>> project: 'Shout' with: '1.2.1'; >>>>>> >>>>>> >>>>>> Now in ConfigurationOfShout there are >>>>>> >>>>>> version122: spec <version: '1.2.2' imports: #('1.1-baseline')> spec for: #common do: [ spec blessing: #development. spec author: 'Francisco Ortiz PeÃ±aloza'. spec description: 'Shout Changes for 1.2 using new SmalltalkEditor'. ]. >>>>>> >>>>>> >>>>>> version121: spec >>>>>> <version: '1.2.1' imports: #('1.1-baseline')> >>>>>> >>>>>> spec for: #common do: [ >>>>>> spec blessing: #development. >>>>>> spec author: 'Stephane Ducasse'. >>>>>> spec description: 'Shout for 1.2'. >>>>>> ]. >>>>>> >>>>>> >>>>>> When I load the latest stable of Pharo >>>>>> >>>>>> ((Smalltalk globals at: #ConfigurationOfPharo) project version: #stable) load >>>>>> >>>>>> I get an error due to a duplicate (probably the instance variable of pluggableShout.....). >>>>>> Probably loading the wrong package. >>>>>> >>>>>> So I do not know what to do and lost my time. >>>>>> >>>>>> Stef >>>>> >>>>> >>>> >>>> >>> >>> >> >> >>

Feb. 28, 2011

Re: [Pharo-project] [update 1.2] #12339

by StÃ©phane Ducasse

How do you update? Because I took 12339 and loaded ConfigurationOfShout and it works I did the same with configurationOfPhaor and it works. > Hi, > > after updating to this version, Shout starts to fail sendind DNU > everywere. One of the things i detect was this update loads in my > image a Shout package signed markus.denker.1... > > Is there a way to see what're the changes on an update? > > Thanks, > Francisco > > On Sun, Feb 27, 2011 at 11:49 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> 12339 >> ----- >> >> Issue 3575: [Failing Tests] Obsolete classes after tests (workaround) >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> >

Feb. 28, 2011

Re: [Pharo-project] Azul Pauseless GC

by Andres Valloud

FWIW, the "pauseless" feature of the algorithm sounds very close (if not exactly) like VisualWorks' incremental GC, modulo the multithreading. On 2/26/11 9:46 , StÃ©phane Ducasse wrote: > Thanks damien for the link :) > > Begin forwarded message: > >> Nice explanation of the Azul Pauseless GC (easier than the paper :) >> http://www.infoq.com/articles/azul_gc_in_detail > > >

Feb. 28, 2011

Re: [Pharo-project] Metacello Configuration Pharo1.2 solo sprint ... status

by Dale Henrichs

I've just finished copying the cleaned up configurations up to MetacelloRepository. All of the configurations that are referenced in ConfigurationOfPharo validate clean ... I loaded the config into a PHaroCore image, but had a number of failed tests, but I am running on a mac and I seem to remember that there were still some failing tests on the mac ... I'll check on the hudson results first thing tomorrow morning to double check .. Dale On Feb 26, 2011, at 6:45 PM, Dale Henrichs wrote: > > On Feb 25, 2011, at 5:27 PM, Dale Henrichs wrote: >> Pharo1.2 is close and Metacello is one of the bad boys with the failing >> tests sooooo, I am going to do a solo sprint this weekend: >> >> 1. a quick release of Metacello with expectedFailures for the tests.... > > released 1.0-beta.28.3.1 with expected failures defined, last night... > >> 2. in build #57 of Pharo1.2 I noticed some odd things that I want to >> track down... > > tracked down the anomalies in build #157... as I suspected, the anomalies were due to configuration specification issues...the right things were loaded, but the configuration errors lead to misleading currentVersions for some of the configs... > >> 3. I expect that some of the #57 issues can be revealed with the >> validator, so I am thinking that I will run the validator over >> all of the configurations that are used in Pharo1.2 ... > > Yep 7 of the configurations referenced by ConfigurationOfPharo had issues that I've been able to clean up without doing anything too drastic to the configs ... I've still got to do some test loads to make sure that they load clean, etc... > >> 4. I'm not going to spend a lot of time reading/writing email ... > > ...GRUNT... > >> 5. While working on the above task, I will work on the >> MetacelloBrowser adding menu items > > Added ob sunit-type validation icons to the confiugrations and versions in the MetacelloBrowser ... when you click on the icon you get the validation results ... there is still more to polish in the MetacelloBrowser, I know that Alexandre is doing more work this evening and I've got a handful of things more to add that I think will be useful ... > > Dale

Feb. 28, 2011

Re: [Pharo-project] comments comments comments again

by Eliot Miranda

Hi StÃ©ph, why not implement a tool that takes a package, asks the user to identify the most important class comment, and the creates comments for all uncommented classes in the package that direct the user to the most important class comment? The generated comment could use the squeak code hyperlink support so the user just has to double click in the generated comment to get to the new comment. How about also including in the comment template a suggestion of what kind of entry-point documentation you'd like to see? 2Â¢ Eliot On Sun, Feb 27, 2011 at 7:18 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > why can we put comment in class comment? > For example I worked on fixing 1.2 and now I want to execute the configurationOfPharo and no magic invocation.... > JUST A FUCKING EMPTY class comment as usual. > > > So again I feel like an idiot and I'm trying in the dark. You have NOT A SINGLE REASON NOT TO PUT COMMENT! > One of these days I will hack the system to break the load when a class as no comment. > > So now after randomly trying.....I get a nice DNU. > Apparently my time is not worth anything.... > > So if you want to see if my fix works. Give a try I will not and if what I did break, may be I will have a look or may be not > because no time for that after. > > > And BTW do not put any comment, it feels much cooler that way. > > Stef > > >

Feb. 28, 2011

Re: [Pharo-project] shout for pharo 1.2: Please help.

by Francisco Ortiz PeÃ±aloza

Hi Stef don't know if you already solve this, i created a 1.2.2 version of ConfigurationOfShout referencing some changes i made to shout to work with Editor changes. There're like five new versions since that and it's currently working with PharoCore 1.2 cause i tested a lot :) Cheers, Francisco On Sun, Feb 27, 2011 at 7:26 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Ok > For me I just wanted to check if I can load shout. > Now it is just breaking on Dev Toolset>> > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â SHWorkspace open. > > I still do not understand how the correct version of shout was loaded before. > Since Pharo was referencing 1.2.1 which was referencing jannik old version > and the one with the fix of benjamin was not loaded. > > So I should adapt the baseline to load the correct test in 1.2.2 > The problem is that testing all the setup takes 35 min. > > Stef > > >> So Stef, I looked at Â ConfigurationOfPharo-StephaneDucasse.139 and I noticed that you commented out some package specs for 1.2-beta2 ... you need to be aware that commenting them out does not prevent those packages from being loaded .... >> >> To make structural changes you need to remove the package spec from 1.2-beta2 _and_ remove the package from 1.2-baseline. >> >> The specification for Shout Tests in Â 1.2-beta2 specifies the mcz file to load. By commenting out the spec and leaving the spec in 1.2-baseline you are telling Metacello to load the latest version of the Shout Tests package.. >> >> Since 1.2-baseline is already shared by multiple versions, one way to remove Shout Tests for version 1.2-beta2, is to create a 1.2-beta2-baseline that does not include Shout Tests... >> >> You comment says that you don't know which version of the Shout Tests to load, but by looking at 1.2-beta2-baseline, Shout Tests is referencing the same project as Shout with a different load directive so it is correct to use the save version as Shout. >> >> In a normal case I would recommend that you use the validator to look at the configuration and fix those issues, but there _are_ a number of validation issues with ConfigurationOfPharo already (which depending on what other changes you have made might actually be contributing to the problem ... There were also validation issues ConfigurationOfShout ... so you might have hit a "perfect storm" of validation issues .. >> >> I have merged your changes into my working copy and I'll be doing a test load shortly so perhaps I'll be able to observe some of the problems first hand .. >> >> Dale >> >> On Feb 27, 2011, at 8:30 AM, StÃ©phane Ducasse wrote: >> >>> Ok >>> I do not understand how it loaded before because >>> Â Â Â I got a duplicate instance warning raised (even if the class loaded was empty - I do not get it) >>> Â Â Â So I remove the empty package, fixing the version and the baseline... >>> >>> Now I have the decompiler popping windows.... problem >>> Today this is tedious. >>> For a fix of 1 min I already spent 2 hours to try to load a configuration. >>> >>> Stef >>> >>> >>>> Stef, >>>> >>>> I will try to take a look at your issue today along with testing out the configuration fixes I have pending ... both Pharo and Shout had configuration issues, but I can't say that your particular issue is related ... yet. >>>> >>>> Dale >>>> >>>> On Feb 27, 2011, at 7:57 AM, StÃ©phane Ducasse wrote: >>>> >>>>> Hi guys >>>>> >>>>> I modified >>>>> >>>>> version 1.2.1 of ConfigurationOfShout to load my version >>>>> Â Â Shout-sd.101 (apparently lot of comments were removed between Benjamin.100 and Benjamin.101 - strange) >>>>> >>>>> >>>>> In ConfigurationOfPharo there is >>>>> >>>>> Â Â project: 'Shout' with: '1.2.1'; >>>>> >>>>> >>>>> Now in ConfigurationOfShout there are >>>>> >>>>> version122: spec <version: '1.2.2' imports: #('1.1-baseline')> spec for: #common do: [ spec blessing: #development. spec author: 'Francisco Ortiz PeÃ±aloza'. spec description: 'Shout Changes for 1.2 using new SmalltalkEditor'. ]. >>>>> >>>>> >>>>> version121: spec >>>>> Â Â <version: '1.2.1' imports: #('1.1-baseline')> >>>>> >>>>> Â Â spec for: #common do: [ >>>>> Â Â Â Â Â Â spec blessing: #development. >>>>> Â Â Â Â Â Â spec author: 'Stephane Ducasse'. >>>>> Â Â Â Â Â Â spec description: 'Shout for 1.2'. >>>>> Â Â ]. >>>>> >>>>> >>>>> When I load the latest stable of Pharo >>>>> >>>>> ((Smalltalk globals at: #ConfigurationOfPharo) project version: #stable) load >>>>> >>>>> I get an error due to a duplicate (probably the instance variable of pluggableShout.....). >>>>> Probably loading the wrong package. >>>>> >>>>> So I do not know what to do and lost my time. >>>>> >>>>> Stef >>>> >>>> >>> >>> >> >> > > >

Feb. 28, 2011

Re: [Pharo-project] [update 1.2] #12339

by Francisco Ortiz PeÃ±aloza

Hi, after updating to this version, Shout starts to fail sendind DNU everywere. One of the things i detect was this update loads in my image a Shout package signed markus.denker.1... Is there a way to see what're the changes on an update? Thanks, Francisco On Sun, Feb 27, 2011 at 11:49 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 12339 > ----- > > Issue 3575: Â Â [Failing Tests] Obsolete classes after tests (workaround) > -- > Marcus Denker Â -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

Feb. 28, 2011