- Pharo-dev - lists.pharo.org

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

by Otto Behrens

> It broke the Pharo 1.2 build on Hudson since 2 days: Sorry about that > Error: Could not resolve: XML-Parser [XML-Parser-OttoBehrens.125] in /builds/workspace/Pharo 1.2/Pharo-1.2/p This tells me that it can't find the file in the repository, specified to be on gemsource, excerpt below. I am confident that I published the XMLParser package on gemsource, but since I don't see it there, I have doubts. I can try to get it published. Best would be if I can get access to the XMLSupport project on squeaksource. package: 'XML-Parser' with: [ spec repository: 'http://seaside.gemstone.com/ss/XMLSupport'; > See > https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/151/conso… Sorry, the stupid bluecoat server on this corporate network of my client blocks this site because of the certificate, so I can't see the console output. > - ConfigurationOfPharo uses project: 'XMLSupport' with: '1.1.6'. > - but 1.1.6 has package: 'XML-Tests-Parser' with: 'XML-Tests-Parser-JAAyer.6' I can't see how this influences the error message > - when I look at Otto's changes in ConfigurationOfXMLSupport > Â then 1.1.7 was marked as broken only for Gemstone and a new 1.1.8/1.1.9 > Â was introduced - so no changes for 1.1.6 version Yes! The later versions should not influence the 1.1.6 version.

Feb. 24, 2011

Re: [Pharo-project] Replacing the pharo logo

by Olivier Auverlot

oops ! I tryed with a clean image of Pharo and this is ok. I think that my image is corrupted with the many tests that i did with it. Thank you for your help. Best regards ;-) Olivier www.auverlot.fr > LogoImageMorph default: (ImageMorph withForm: (ImageReadWriter > formFromFileNamed: 'logo.png'))) > > should do it > Cheers > Alain > > > Le 24/02/2011 14:17, Olivier Auverlot a Ã©crit : >> Thank for your help. >> >> I tried this command in the workspace but I got an error. >> >> LogoImageMorph default: (ImageReadWriter formFromFileNamed: 'logo.png') >> >> Form(Object)>>doesNotUnderstand: #delete >> >> >> My picture is in the same directory that the Pharo image. >> >> Best regards >> Olivier ;-) >> >> www.auverlot.fr >> >> Le 24/02/11 13:48, Mariano Martinez Peck a Ã©crit : >>> >>> >>> On Thu, Feb 24, 2011 at 11:34 AM, Olivier Auverlot >>> <olivier.auverlot(a)gmail.com <mailto:olivier.auverlot@gmail.com>> wrote: >>> >>> Hi, >>> >>> How to replacing the pharo logo with a custom picture ? >>> >>> In the collaboractive book, I found an article about "Putting a >>> background picture" but it changes the background without modify >>> the logo. >>> >>> >>> similar, but use LogoImageMorph default: yourImage >>> >>> Best regards >>> Olivier ;-) >>> >>> www.auverlot.fr <http://www.auverlot.fr> >>> >>> >> > >

Feb. 24, 2011

Re: [Pharo-project] Replacing the pharo logo

by Olivier Auverlot

Hi Alain, Sorry. I got the same error that in my previous mail :-( > LogoImageMorph default: (ImageMorph withForm: (ImageReadWriter > formFromFileNamed: 'logo.png'))) > > should do it > Cheers > Alain > > > Le 24/02/2011 14:17, Olivier Auverlot a Ã©crit : >> Thank for your help. >> >> I tried this command in the workspace but I got an error. >> >> LogoImageMorph default: (ImageReadWriter formFromFileNamed: 'logo.png') >> >> Form(Object)>>doesNotUnderstand: #delete >> >> >> My picture is in the same directory that the Pharo image. >> >> Best regards >> Olivier ;-) >> >> www.auverlot.fr >> >> Le 24/02/11 13:48, Mariano Martinez Peck a Ã©crit : >>> >>> >>> On Thu, Feb 24, 2011 at 11:34 AM, Olivier Auverlot >>> <olivier.auverlot(a)gmail.com <mailto:olivier.auverlot@gmail.com>> wrote: >>> >>> Hi, >>> >>> How to replacing the pharo logo with a custom picture ? >>> >>> In the collaboractive book, I found an article about "Putting a >>> background picture" but it changes the background without modify >>> the logo. >>> >>> >>> similar, but use LogoImageMorph default: yourImage >>> >>> Best regards >>> Olivier ;-) >>> >>> www.auverlot.fr <http://www.auverlot.fr> >>> >>> >> > >

Feb. 24, 2011

[Pharo-project] Issue 3750 in pharo: The desktop logo should be changeable from the SettingBrowser

by pharo＠googlecode.com

Status: Accepted Owner: aplan...(a)gmail.com New issue 3750 by aplan...(a)gmail.com: The desktop logo should be changeable from the SettingBrowser http://code.google.com/p/pharo/issues/detail?id=3750 very simple to do. I will add it soon

Feb. 24, 2011

Re: [Pharo-project] Replacing the pharo logo

by Alain Plantec

Le 24/02/2011 16:26, Mariano Martinez Peck a Ã©crit : > alain, maybe this is another good idea for a setting ? > yes! http://code.google.com/p/pharo/issues/detail?id=3750 Alain

Feb. 24, 2011

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

by Torsten Bergmann

Whatever has changed from ConfigurationOfXMLSupport-DaleHenrichs.46 up to ... ConfigurationOfXMLSupport-OttoBehrens.56 It broke the Pharo 1.2 build on Hudson since 2 days: Error: Could not resolve: XML-Parser [XML-Parser-OttoBehrens.125] in /builds/workspace/Pharo 1.2/Pharo-1.2/p See https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/151/conso… - ConfigurationOfPharo uses project: 'XMLSupport' with: '1.1.6'. - but 1.1.6 has package: 'XML-Tests-Parser' with: 'XML-Tests-Parser-JAAyer.6' - when I look at Otto's changes in ConfigurationOfXMLSupport then 1.1.7 was marked as broken only for Gemstone and a new 1.1.8/1.1.9 was introduced - so no changes for 1.1.6 version Any comments? Thx T. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

Feb. 24, 2011

Re: [Pharo-project] Replacing the pharo logo

by Mariano Martinez Peck

alain, maybe this is another good idea for a setting ? On Thu, Feb 24, 2011 at 4:17 PM, Alain Plantec <alain.plantec(a)yahoo.com>wrote: > LogoImageMorph default: (ImageMorph withForm: (ImageReadWriter > formFromFileNamed: 'logo.png'))) > > should do it > Cheers > Alain > > > Le 24/02/2011 14:17, Olivier Auverlot a Ã©crit : > >> Thank for your help. >> >> I tried this command in the workspace but I got an error. >> >> LogoImageMorph default: (ImageReadWriter formFromFileNamed: 'logo.png') >> >> Form(Object)>>doesNotUnderstand: #delete >> >> >> My picture is in the same directory that the Pharo image. >> >> Best regards >> Olivier ;-) >> >> www.auverlot.fr >> >> Le 24/02/11 13:48, Mariano Martinez Peck a Ã©crit : >> >>> >>> >>> On Thu, Feb 24, 2011 at 11:34 AM, Olivier Auverlot < >>> olivier.auverlot(a)gmail.com <mailto:olivier.auverlot@gmail.com>> wrote: >>> >>> Hi, >>> >>> How to replacing the pharo logo with a custom picture ? >>> >>> In the collaboractive book, I found an article about "Putting a >>> background picture" but it changes the background without modify >>> the logo. >>> >>> >>> similar, but use LogoImageMorph default: yourImage >>> >>> Best regards >>> Olivier ;-) >>> >>> www.auverlot.fr <http://www.auverlot.fr> >>> >>> >>> >> > >

Feb. 24, 2011

Re: [Pharo-project] Replacing the pharo logo

by Alain Plantec

LogoImageMorph default: (ImageMorph withForm: (ImageReadWriter formFromFileNamed: 'logo.png'))) should do it Cheers Alain Le 24/02/2011 14:17, Olivier Auverlot a Ã©crit : > Thank for your help. > > I tried this command in the workspace but I got an error. > > LogoImageMorph default: (ImageReadWriter formFromFileNamed: 'logo.png') > > Form(Object)>>doesNotUnderstand: #delete > > > My picture is in the same directory that the Pharo image. > > Best regards > Olivier ;-) > > www.auverlot.fr > > Le 24/02/11 13:48, Mariano Martinez Peck a Ã©crit : >> >> >> On Thu, Feb 24, 2011 at 11:34 AM, Olivier Auverlot >> <olivier.auverlot(a)gmail.com <mailto:olivier.auverlot@gmail.com>> wrote: >> >> Hi, >> >> How to replacing the pharo logo with a custom picture ? >> >> In the collaboractive book, I found an article about "Putting a >> background picture" but it changes the background without modify >> the logo. >> >> >> similar, but use LogoImageMorph default: yourImage >> >> Best regards >> Olivier ;-) >> >> www.auverlot.fr <http://www.auverlot.fr> >> >> >

Feb. 24, 2011

Re: [Pharo-project] [Metacello] Metacello tests failing in 1.2

by laurent laffont

On Thu, Feb 24, 2011 at 3:40 PM, Dale Henrichs <dhenrich(a)vmware.com> wrote: > Unless I find a real bug (I haven't run into one yet) the only changes I'm > making specifically for Pharo 1.2 with the new Gofer is to change the tests > so that they pass. There are no behavior changes needed, just change the > tests to use the "correct" branching scheme. > OK. Then I agree for the #expectedFailures solution. Laurent. > > Dale > > On Feb 24, 2011, at 6:28 AM, laurent laffont wrote: > > On Thu, Feb 24, 2011 at 3:15 PM, Dale Henrichs <dhenrich(a)vmware.com > <mailto:dhenrich@vmware.com>> wrote: > I haven't released my changes yet ... once I'm satisfied with the the > behavior on PharoCore1.2 (that's where I'm doing development) I now have to > get the new version of Gofer ported to Squeak and GemStone before I can make > the full release ... otherwise the tests will be failing on Squeak/GemStone > ... > > If the goal is to make the tests green on Pharo1.2, you might just add > #expectedFailures as non-metacello extension methods to the troublesome > tests ... I think that this is the exact use case that #expectedFailures is > aimed at ... the tests will be green for Pharo1.2 and I'll be able to take > the necessary time to propogate the necessary changes... > > Well, I prefer to not have tests green in this case because Pharo 1.2 > cannot be released without the fixed version of Metacello, is it ? > > Laurent. > > > Dale > On Feb 24, 2011, at 5:50 AM, laurent laffont wrote: > > On Thu, Feb 24, 2011 at 2:31 PM, Dale Henrichs <dhenrich(a)vmware.com > <mailto:dhenrich@vmware.com><mailto:dhenrich@vmware.com<mailto: > dhenrich(a)vmware.com>>> wrote: > Laurent, > > I've actually made a pass and cleaned up the tests ... you can compare with > my work:)... I need to write some more tests to make sure that Metacello is > still behaving correctly, I think I've added enough coverage, but I need to > look a little closer ... > > My guess is that you didn't reset the resource ... the resource structure > is cached, so when you make changes to the code that is used to create the > resource, you need to reset it as well... > > Yes that was that ! Still 9 errors but as you've already done it ..... > your changes has been integrated in PharoCore 1.2 ? > > Laurent. > > > > > Dale > > On Feb 24, 2011, at 12:10 AM, laurent laffont wrote: > > On Thu, Feb 17, 2011 at 12:33 AM, Dale Henrichs <dhenrich(a)vmware.com > <mailto:dhenrich@vmware.com><mailto:dhenrich@vmware.com<mailto: > dhenrich(a)vmware.com>><mailto:dhenrich@vmware.com<mailto: > dhenrich(a)vmware.com><mailto:dhenrich@vmware.com<mailto:dhenrich@vmware.com>>>> > wrote: > On 02/15/2011 05:46 PM, Guillermo Polito wrote: > Hi Dale! > > There are 13 failing tests on the 1.2 dev build since a week ago ( > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/141/testReport/ > ). Do we have the right version? Do you have any clue so I don't dive > in the code blindly? :) > > Cheers, > Guille > > Ahhhh, It looks the Gofer changes for Issue 3660 have been integrated, > which means that the sorting order for mcz files has been changed, which > means that the Metacello tests that are sensitive (or validating) the sort > order have broken ... > > It will be at least a couple of days before I can get these issues fixed I > have to propogate the gofer fixes to GemStone and Squeak... the normal > operation of Metacello shouldn't be affected by these failing tests ... the > test cases involved include examples of mcz files with "incorrect" branch > naming scheme... > > I've created Metacello Issue 108: "Need to update Metacello (tests and > Gofer config) to integrate changes from Pharo Issue 3660"[1] to track > progress. > > [1] http://code.google.com/p/metacello/issues/detail?id=108 > > > > I've tried to resolve this past two days (yep, not so easy for a first dive > into Metacello :). If I understand: > 'GoferBar-lr.branch.1' should be 'GoferBar.branch-lr.1' > > so I've changed this for all packages/branches everywhere (in > MetacelloMonticelloResource, MetacelloConfigurationResource, GoferResource > and tests). > > Now a lot of tests are red because in > MetacelloFetchingMCSpecLoader>>retryingResolvePackageSpecReferences: it > cannot find GoferBar-lr.branch.2 > Indeed in MetacelloTestConfigurationOfFoo generated by the tests there's > package: 'GoferBar' with: 'GoferBar-lr.branch.2'; > > This driving me mad: I cannot find how MetacelloTestConfigurationOfFoo is > generated and when a spec with 'GoferBar-lr.branch.2' is created instead of > 'GoferBar.branch-lr.2'. > > > Any hint ? > > Cheers, > > Laurent > > > Dale > > > > > > > > > >

Feb. 24, 2011

Re: [Pharo-project] [Metacello] Metacello tests failing in 1.2

by Dale Henrichs

Unless I find a real bug (I haven't run into one yet) the only changes I'm making specifically for Pharo 1.2 with the new Gofer is to change the tests so that they pass. There are no behavior changes needed, just change the tests to use the "correct" branching scheme. Dale On Feb 24, 2011, at 6:28 AM, laurent laffont wrote: On Thu, Feb 24, 2011 at 3:15 PM, Dale Henrichs <dhenrich(a)vmware.com<mailto:dhenrich@vmware.com>> wrote: I haven't released my changes yet ... once I'm satisfied with the the behavior on PharoCore1.2 (that's where I'm doing development) I now have to get the new version of Gofer ported to Squeak and GemStone before I can make the full release ... otherwise the tests will be failing on Squeak/GemStone ... If the goal is to make the tests green on Pharo1.2, you might just add #expectedFailures as non-metacello extension methods to the troublesome tests ... I think that this is the exact use case that #expectedFailures is aimed at ... the tests will be green for Pharo1.2 and I'll be able to take the necessary time to propogate the necessary changes... Well, I prefer to not have tests green in this case because Pharo 1.2 cannot be released without the fixed version of Metacello, is it ? Laurent. Dale On Feb 24, 2011, at 5:50 AM, laurent laffont wrote: On Thu, Feb 24, 2011 at 2:31 PM, Dale Henrichs <dhenrich(a)vmware.com<mailto:dhenrich@vmware.com><mailto:dhenrich@vmware.com<mailto:dhenrich@vmware.com>>> wrote: Laurent, I've actually made a pass and cleaned up the tests ... you can compare with my work:)... I need to write some more tests to make sure that Metacello is still behaving correctly, I think I've added enough coverage, but I need to look a little closer ... My guess is that you didn't reset the resource ... the resource structure is cached, so when you make changes to the code that is used to create the resource, you need to reset it as well... Yes that was that ! Still 9 errors but as you've already done it ..... your changes has been integrated in PharoCore 1.2 ? Laurent. Dale On Feb 24, 2011, at 12:10 AM, laurent laffont wrote: On Thu, Feb 17, 2011 at 12:33 AM, Dale Henrichs <dhenrich(a)vmware.com<mailto:dhenrich@vmware.com><mailto:dhenrich@vmware.com<mailto:dhenrich@vmware.com>><mailto:dhenrich@vmware.com<mailto:dhenrich@vmware.com><mailto:dhenrich@vmware.com<mailto:dhenrich@vmware.com>>>> wrote: On 02/15/2011 05:46 PM, Guillermo Polito wrote: Hi Dale! There are 13 failing tests on the 1.2 dev build since a week ago ( https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/141/testReport/ ). Do we have the right version? Do you have any clue so I don't dive in the code blindly? :) Cheers, Guille Ahhhh, It looks the Gofer changes for Issue 3660 have been integrated, which means that the sorting order for mcz files has been changed, which means that the Metacello tests that are sensitive (or validating) the sort order have broken ... It will be at least a couple of days before I can get these issues fixed I have to propogate the gofer fixes to GemStone and Squeak... the normal operation of Metacello shouldn't be affected by these failing tests ... the test cases involved include examples of mcz files with "incorrect" branch naming scheme... I've created Metacello Issue 108: "Need to update Metacello (tests and Gofer config) to integrate changes from Pharo Issue 3660"[1] to track progress. [1] http://code.google.com/p/metacello/issues/detail?id=108 I've tried to resolve this past two days (yep, not so easy for a first dive into Metacello :). If I understand: 'GoferBar-lr.branch.1' should be 'GoferBar.branch-lr.1' so I've changed this for all packages/branches everywhere (in MetacelloMonticelloResource, MetacelloConfigurationResource, GoferResource and tests). Now a lot of tests are red because in MetacelloFetchingMCSpecLoader>>retryingResolvePackageSpecReferences: it cannot find GoferBar-lr.branch.2 Indeed in MetacelloTestConfigurationOfFoo generated by the tests there's package: 'GoferBar' with: 'GoferBar-lr.branch.2'; This driving me mad: I cannot find how MetacelloTestConfigurationOfFoo is generated and when a spec with 'GoferBar-lr.branch.2' is created instead of 'GoferBar.branch-lr.2'. Any hint ? Cheers, Laurent Dale

Feb. 24, 2011