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

Re: [Pharo-project] Issue 3707 in pharo: Syntax highlighting looks strange

by pharo＠googlecode.com

Comment #5 on issue 3707 by marcus.d...(a)gmail.com: Syntax highlighting looks strange http://code.google.com/p/pharo/issues/detail?id=3707 Why don't we just change it back to how it used to be? We are *frozen* and want to release 1.2 ASAP (that is, 2 month ago). Yet, someone changed compeltely everything for how syntax is colored. In a very ad-hoc way. it's not just the bold. The colors are *random*. Selectors are colored the same as arguments, for example. We should just revert and do experiments in 1.3.

Feb. 25, 2011

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

by laurent laffont

On Fri, Feb 25, 2011 at 2:10 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Markus wrote: > >The XML package breaks the build? So let's remove it completely. Let's > ship >1.2, but without all the packages that are problematic. > > It's not that the package is problematic - the Configs are problematic > > Laurent wrote: > >For XML I can fix this tonight if Otto don't want / can do it. > > Yes, the problematic 1.1.8 version of XMLSupport has to be fixed. > But it is not yet used by Pharo ... so this is not the reason: > > What strikes me is that ConfigurationOfPharo STILL references > the working 1.1.6 version BUT the corrupt 1.1.8 version is > loaded instead. > May be another ConfigurationOfXXXX reference XMLSupport ? Laurent > THIS is the reason why Hudson is read! > > If you look at ConfigurationOfPharo then it hasnt changed > since 18 February 2011 (ConfigurationOfPharo-GuillermoPolito.134) > and if you load "ConfigurationOfXMLSupport-DaleHenrichs.46" > from 9 February 2011 and check what Otto Behrens changed > then you will notice that he did'nt touch the 1.1.6 version > of ConfigurationOfXMLSupport. > > He just added a baseline/version 1.1.8 and 1.1.9. > > So the "old" version 1.1.6 which is used by ConfigurationOfPharo > was not touched either. > > To me this looks like a Metacello resolving remote project > versions problem? (that's why I CC:ed Dale) > > > >But I agree that it seems few people care about 1.2. Sad, I like it far > >better than 1.1.1. > > Yes, but I think we opened 1.3 too early. I think thats > why community does not concentrate on Pharo dev 1.2 too much > and continues to work on 1.3 core instead. > > Thats good for moving Pharo forward - but not for outside > visibility. How should others deliver software on top of Pharo > if Pharo isnt delivered itself? > > >I personally thing if we ever want to release 1.2, we need to start to be > >more radical. > > Yes - but not by throwing out broken packages. What if Hudson > is broken by a problem in clas Object. Would you throw out Kernel? > > Instead I would propose for the harvesters/integrators to stop > integrating stuff for 1.3 until Pharo 1.2 is out of the door... > > Bye > T. > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > >

Feb. 25, 2011

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

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage Importance-High New issue 3758 by marcus.d...(a)gmail.com: Metacello has 12 failing tests in 1.2 http://code.google.com/p/pharo/issues/detail?id=3758 >>> Metacello.TestsMC.MetacelloCurrentVersionTest.testFoo40Loaded1Package1LaterPackage >>> >>> 3.296 22 >>> Metacello.TestsMC.MetacelloGoferBasedAtomicLoaderTest.testBaselineFetch >>> 0.06 22 >>> Metacello.TestsMC.MetacelloGoferBasedAtomicLoaderTest.testBaselineLoad >>> 0.769 22 >>> Metacello.TestsMC.MetacelloGoferBasedAtomicLoaderTest.testIssue49PartialLoadC >>> >>> 1.539 22 >>> Metacello.TestsMC.MetacelloGoferBasedAtomicLoaderTest.testIssue49PartialLoadG >>> >>> 1.726 22 >>> Metacello.TestsMC.MetacelloGoferBasedLoaderTest.testIssue49PartialLoadC >>> 1.529 22 >>> Metacello.TestsMC.MetacelloGoferBasedLoaderTest.testBaselineFetch >>> 0.056 22 >>> Metacello.TestsMC.MetacelloGoferBasedLoaderTest.testBaselineLoad 0.831 >>> 22 >>> Metacello.TestsMC.MetacelloGoferBasedLoaderTest.testIssue49PartialLoadG >>> 1.787 22 >>> Metacello.TestsMC.MetacelloGoferFunctionalTest.testComparison 0.0070 22 >>> Metacello.TestsMC.MetacelloGoferFunctionalTest.testPackageResolution >>> 0.012 22 >>> Metacello.TestsMC.MetacelloMCCachingLoaderTestCase.testBaselineLoad >>> 0.957 22 >>> Metacello.TestsMC.MetacelloMCSpecLoaderTest.testLatestPackage What do we do?

Feb. 25, 2011

Re: [Pharo-project] Issue 3757 in pharo: 1.2 build is broken due to XML package

by pharo＠googlecode.com

Comment #1 on issue 3757 by marcus.d...(a)gmail.com: 1.2 build is broken due to XML package http://code.google.com/p/pharo/issues/detail?id=3757 We should remove the XML package

Feb. 25, 2011

Re: [Pharo-project] Issue 3581 in pharo: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

by pharo＠googlecode.com

Comment #4 on issue 3581 by marcus.d...(a)gmail.com: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3581 We should remove this package from 1.2

Feb. 25, 2011

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

by Torsten Bergmann

Markus wrote: >The XML package breaks the build? So let's remove it completely. Let's ship >1.2, but without all the packages that are problematic. It's not that the package is problematic - the Configs are problematic Laurent wrote: >For XML I can fix this tonight if Otto don't want / can do it. Yes, the problematic 1.1.8 version of XMLSupport has to be fixed. But it is not yet used by Pharo ... so this is not the reason: What strikes me is that ConfigurationOfPharo STILL references the working 1.1.6 version BUT the corrupt 1.1.8 version is loaded instead. THIS is the reason why Hudson is read! If you look at ConfigurationOfPharo then it hasnt changed since 18 February 2011 (ConfigurationOfPharo-GuillermoPolito.134) and if you load "ConfigurationOfXMLSupport-DaleHenrichs.46" from 9 February 2011 and check what Otto Behrens changed then you will notice that he did'nt touch the 1.1.6 version of ConfigurationOfXMLSupport. He just added a baseline/version 1.1.8 and 1.1.9. So the "old" version 1.1.6 which is used by ConfigurationOfPharo was not touched either. To me this looks like a Metacello resolving remote project versions problem? (that's why I CC:ed Dale) >But I agree that it seems few people care about 1.2. Sad, I like it far >better than 1.1.1. Yes, but I think we opened 1.3 too early. I think thats why community does not concentrate on Pharo dev 1.2 too much and continues to work on 1.3 core instead. Thats good for moving Pharo forward - but not for outside visibility. How should others deliver software on top of Pharo if Pharo isnt delivered itself? >I personally thing if we ever want to release 1.2, we need to start to be >more radical. Yes - but not by throwing out broken packages. What if Hudson is broken by a problem in clas Object. Would you throw out Kernel? Instead I would propose for the harvesters/integrators to stop integrating stuff for 1.3 until Pharo 1.2 is out of the door... Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

Feb. 25, 2011

Re: [Pharo-project] Issue 3652 in pharo: [Failing Test] MocketryTests.Actions.MockActionAcceptanceTests.testWillProcessBlocking

by pharo＠googlecode.com

Comment #4 on issue 3652 by marcus.d...(a)gmail.com: [Failing Test] MocketryTests.Actions.MockActionAcceptanceTests.testWillProcessBlocking http://code.google.com/p/pharo/issues/detail?id=3652 We should remove this package from 1.2

Feb. 25, 2011

[Pharo-project] Issue 3757 in pharo: 1.2 build is broken due to XML package

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage Importance-High New issue 3757 by marcus.d...(a)gmail.com: 1.2 build is broken due to XML package http://code.google.com/p/pharo/issues/detail?id=3757 1.2 build is broken due to XML package

Feb. 25, 2011

Re: [Pharo-project] Issue 3731 in pharo: default browser size bigger

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3731 by marcus.d...(a)gmail.com: default browser size bigger http://code.google.com/p/pharo/issues/detail?id=3731 The core browser size looks good to me

Feb. 25, 2011

Re: [Pharo-project] Issue 3579 in pharo: "declare temp" adds the variable twice

by pharo＠googlecode.com

Updates: Status: Closed Comment #14 on issue 3579 by marcus.d...(a)gmail.com: "declare temp" adds the variable twice http://code.google.com/p/pharo/issues/detail?id=3579 verified in #149

Feb. 25, 2011