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

[Pharo-project] Fwd: [Metacello] Metacello 1.0-beta.28.3.1 released

by Dale Henrichs

Begin forwarded message: From: Dale Henrichs <dhenrich(a)vmware.com<mailto:dhenrich@vmware.com>> Date: February 25, 2011 9:12:04 PM PST To: Metacello <metacello(a)googlegroups.com<mailto:metacello@googlegroups.com>> Subject: [Metacello] Metacello 1.0-beta.28.3.1 released Reply-To: "metacello(a)googlegroups.com<mailto:metacello@googlegroups.com>" <metacello(a)googlegroups.com<mailto:metacello@googlegroups.com>> Targeted at Pharo1.2 - fix Issue 3758: Metacello has 12 failing tests in 1.2 http://code.google.com/p/pharo/issues/detail?id=3758 - well ... add expectedFails for the tests are failing due to the fix for Pharo Issue 3660 Dale

Feb. 26, 2011

[Pharo-project] Hudson build script for Pharo-1.2 image

by Dale Henrichs

Marcus, When you get a chance could you give me a pointer to the build script that you use to build the Pharo-1.2 image? Thanks, Dale

Feb. 26, 2011

[Pharo-project] [ANN] More on Keymappings

by Guillermo Polito

What do we have now? - Can provide settings for a set of morphs - Can provide settings for a TextEditors (Smalltalk editor and related) - Settings integration I added some methods to the Settings Tree Builder in order to avoid references from the users code. - I ran Slint over it and cleaned it a lot more :). ( And learnt that Slint is there :P ) More info in here: http://guilleel3.blogspot.com/ Guille

Feb. 26, 2011

Re: [Pharo-project] Metacello Configuration Pharo1.2 solo sprint Portland, Oregon ... Saturday and Sunday

by Miguel CobÃ¡

Thanks Dale El vie, 25-02-2011 a las 17:27 -0800, Dale Henrichs escribiÃ³: > Okay, okay.... I've been trying to keep a half dozen balls in the air > for the last few weeks and what that means is that I don't give enough > attention to any of them ... > > 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 > that are failing in Pharo1.2. I have already fixed the tests > (only test changes are needed), but I now need to port the Gofer > changes to Squeak and GemStone which is a bigger job. A quick > surgical set of expectedFailures is the best thing to do here. > 2. in build #57 of Pharo1.2 I noticed some odd things that I want to > track down... > 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 and go about > identify and/or fixing the meaningful issues that I find. My main > goal will be to repair things that are broken, so I will be > reluctant to make semantic changes without checking with the > maintainers, but if the problem is really gruesome I will fix it > and apologize later:) > 4. I'm not going to spend a lot of time reading/writing email ... > this will be a sprint not a coffee klatch. With that said, if you > have a Metacello config issue that is related to Pharo1.2 drop me > an email with your question/thought but don't be offended if > I don't respond at all or just GRUNT in reply ... I may even take > action without letting you know... > 5. While working on the above task, I will work on the > MetacelloBrowser adding menu items for the operations that I > performso it will then be easier for other folks to perform the > same types of jobs in the future. I may do something funky like > hide the menu items behind a boolean so as not to pollute the > menu items with a whole bunch of advanced type operations (that > will be named poorly:)... > > I realize that I may be closing the barn door after the horse is gone - > build 57 is yellow afterall - but cleaning up validation issues is long > overdue. > > I don't plan on fixing Metacello bugs unless I find something that just > begs to be fixed ... the sprint is mainly about running the validator > and cleaning up the real nasty bits and track down the Metacello > anomalies in #57... > > Dale > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Feb. 26, 2011

Re: [Pharo-project] Metacello Configuration Pharo1.2 solo sprint Portland, Oregon ... Saturday and Sunday

by Dale Henrichs

Alexandre, Great ... I'm getting an early start on the sprint tonight, so I might have checked in some new commands by the time you get to it ... I like the OB-style commands that will be very convenient... Dale On Feb 25, 2011, at 6:30 PM, Alexandre Bergel wrote: > > Hi Dale! > > FYI, I plan to work on MetacelloBrowser tomorrow evening. Accommodating the issue with automatic addition of repositories and a better management of the comment. And if I find some time, I will implement the OB-like command discovery. Much better than fiddling with the #fillMenu: method. > > I will let you know about my progresses. > > Cheers, > Alexandre > > > Le 25 fÃ©vr. 2011 Ã 22:27, Dale Henrichs <dhenrich(a)vmware.com> a Ã©crit : > >> Okay, okay.... I've been trying to keep a half dozen balls in the air for the last few weeks and what that means is that I don't give enough attention to any of them ... >> >> 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 >> that are failing in Pharo1.2. I have already fixed the tests >> (only test changes are needed), but I now need to port the Gofer >> changes to Squeak and GemStone which is a bigger job. A quick >> surgical set of expectedFailures is the best thing to do here. >> 2. in build #57 of Pharo1.2 I noticed some odd things that I want to >> track down... >> 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 and go about >> identify and/or fixing the meaningful issues that I find. My main >> goal will be to repair things that are broken, so I will be >> reluctant to make semantic changes without checking with the >> maintainers, but if the problem is really gruesome I will fix it >> and apologize later:) >> 4. I'm not going to spend a lot of time reading/writing email ... >> this will be a sprint not a coffee klatch. With that said, if you >> have a Metacello config issue that is related to Pharo1.2 drop me >> an email with your question/thought but don't be offended if >> I don't respond at all or just GRUNT in reply ... I may even take >> action without letting you know... >> 5. While working on the above task, I will work on the >> MetacelloBrowser adding menu items for the operations that I >> performso it will then be easier for other folks to perform the >> same types of jobs in the future. I may do something funky like >> hide the menu items behind a boolean so as not to pollute the >> menu items with a whole bunch of advanced type operations (that >> will be named poorly:)... >> >> I realize that I may be closing the barn door after the horse is gone - build 57 is yellow afterall - but cleaning up validation issues is long overdue. >> >> I don't plan on fixing Metacello bugs unless I find something that just begs to be fixed ... the sprint is mainly about running the validator and cleaning up the real nasty bits and track down the Metacello anomalies in #57... >> >> Dale >> >

Feb. 26, 2011

Re: [Pharo-project] Metacello Configuration Pharo1.2 solo sprint Portland, Oregon ... Saturday and Sunday

by Alexandre Bergel

Hi Dale! FYI, I plan to work on MetacelloBrowser tomorrow evening. Accommodating the issue with automatic addition of repositories and a better management of the comment. And if I find some time, I will implement the OB-like command discovery. Much better than fiddling with the #fillMenu: method. I will let you know about my progresses. Cheers, Alexandre Le 25 fÃ©vr. 2011 Ã 22:27, Dale Henrichs <dhenrich(a)vmware.com> a Ã©crit : > Okay, okay.... I've been trying to keep a half dozen balls in the air for the last few weeks and what that means is that I don't give enough attention to any of them ... > > 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 > that are failing in Pharo1.2. I have already fixed the tests > (only test changes are needed), but I now need to port the Gofer > changes to Squeak and GemStone which is a bigger job. A quick > surgical set of expectedFailures is the best thing to do here. > 2. in build #57 of Pharo1.2 I noticed some odd things that I want to > track down... > 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 and go about > identify and/or fixing the meaningful issues that I find. My main > goal will be to repair things that are broken, so I will be > reluctant to make semantic changes without checking with the > maintainers, but if the problem is really gruesome I will fix it > and apologize later:) > 4. I'm not going to spend a lot of time reading/writing email ... > this will be a sprint not a coffee klatch. With that said, if you > have a Metacello config issue that is related to Pharo1.2 drop me > an email with your question/thought but don't be offended if > I don't respond at all or just GRUNT in reply ... I may even take > action without letting you know... > 5. While working on the above task, I will work on the > MetacelloBrowser adding menu items for the operations that I > performso it will then be easier for other folks to perform the > same types of jobs in the future. I may do something funky like > hide the menu items behind a boolean so as not to pollute the > menu items with a whole bunch of advanced type operations (that > will be named poorly:)... > > I realize that I may be closing the barn door after the horse is gone - build 57 is yellow afterall - but cleaning up validation issues is long overdue. > > I don't plan on fixing Metacello bugs unless I find something that just begs to be fixed ... the sprint is mainly about running the validator and cleaning up the real nasty bits and track down the Metacello anomalies in #57... > > Dale >

Feb. 26, 2011

[Pharo-project] Metacello Configuration Pharo1.2 solo sprint Portland, Oregon ... Saturday and Sunday

by Dale Henrichs

Okay, okay.... I've been trying to keep a half dozen balls in the air for the last few weeks and what that means is that I don't give enough attention to any of them ... 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 that are failing in Pharo1.2. I have already fixed the tests (only test changes are needed), but I now need to port the Gofer changes to Squeak and GemStone which is a bigger job. A quick surgical set of expectedFailures is the best thing to do here. 2. in build #57 of Pharo1.2 I noticed some odd things that I want to track down... 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 and go about identify and/or fixing the meaningful issues that I find. My main goal will be to repair things that are broken, so I will be reluctant to make semantic changes without checking with the maintainers, but if the problem is really gruesome I will fix it and apologize later:) 4. I'm not going to spend a lot of time reading/writing email ... this will be a sprint not a coffee klatch. With that said, if you have a Metacello config issue that is related to Pharo1.2 drop me an email with your question/thought but don't be offended if I don't respond at all or just GRUNT in reply ... I may even take action without letting you know... 5. While working on the above task, I will work on the MetacelloBrowser adding menu items for the operations that I performso it will then be easier for other folks to perform the same types of jobs in the future. I may do something funky like hide the menu items behind a boolean so as not to pollute the menu items with a whole bunch of advanced type operations (that will be named poorly:)... I realize that I may be closing the barn door after the horse is gone - build 57 is yellow afterall - but cleaning up validation issues is long overdue. I don't plan on fixing Metacello bugs unless I find something that just begs to be fixed ... the sprint is mainly about running the validator and cleaning up the real nasty bits and track down the Metacello anomalies in #57... Dale

Feb. 26, 2011

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

by Dale Henrichs

I've downloaded a Pharo1.2 image from Hudson to see what's happening and I notice that there are a number of validation issues with the ConfigurationOfPharo ... so I think that the XMLSupport issues have been addressed ... this build is yello and the earlier build was red ... Is that right? Or are there other things that I don't know about? Dale On 02/25/2011 04:11 AM, Torsten Bergmann wrote: > Still I do not understand: > > Evaluate this in an updated Pharo core 1.2: > > ------------------------------------------------------------------------ > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfXMLSupport'; > load. > > (Smalltalk at: #ConfigurationOfXMLSupport) project latestVersion > ------------------------------------------------------------------------ > > returns 1.1.8 [ConfigurationOfXMLSupport] > > This is now broken by Otto. OK, he broke it, he has to repair it;) > > But independent from that, the method in: > > ConfigurationOfPharo>>version12beta2: > > includes the following: > > project: 'XMLSupport' with: '1.1.6'. > > So I would have expected that for Pharo "1.2-beta2" the 1.1.6 (and not the > 1.1.8) of XMLSupport gets loaded and Hudson should have been green. > > Why does Metacello load the 1.1.8 when a previous project version (1.1.6) > is referenced? > > Dale, any comments?

Feb. 26, 2011

Re: [Pharo-project] Issue 3758 in pharo: Metacello has 12 failing tests in 1.2

by pharo＠googlecode.com

Comment #1 on issue 3758 by da...(a)teleport.com: Metacello has 12 failing tests in 1.2 http://code.google.com/p/pharo/issues/detail?id=3758 keep an eye on http://code.google.com/p/metacello/issues/detail?id=108 for status ... at the moment, I have fixed the tests for Pharo1.2, but I now need to port the Gofer changes to GemStone and Squeak before making a new release. I suggest that you set expectedFailures for those tests, since only the tests are affected by the Gofer changes ...

Feb. 26, 2011

Re: [Pharo-project] we cannot add attachment anymore on the bug tracker

by David T. Lewis

On Sat, Feb 26, 2011 at 12:40:33AM +0100, Igor Stasenko wrote: > On 26 February 2011 00:17, Lukas Renggli <renggli(a)gmail.com> wrote: > > On 26 February 2011 00:16, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 25 February 2011 23:53, Lukas Renggli <renggli(a)gmail.com> wrote: > >>> Thanks for letting me know. Getting the quota increased is pretty easy > >>> (kudos Nathaniel), if you ask the right people ;-) > >> > >> i don't know such people personally. > > > > Yes, I don't know you either. > > > that was rude. > I do not think it was meant to be rude. I am guessing that this was just a way to say thank you to Nathanael SchÃ¤rli, an esteemed Squeak (Pharo) alumnus who IIRC is now working for Google. For myself, I don't know any of the Squeak/Pharo folks personally, so I don't think there is anything wrong with that :) Dave

Feb. 26, 2011