January 2014 - Pharo-dev - lists.pharo.org

XMLParser Problem with SVG

by J.F. Rick

I am trying to use SVG with Athens; however, the XMLParser for Pharo 3.0 cannot read normal SVG files that it used to. So, the demo of "ASVGMorph fromFile: 'lion.svg'" fails in the XMLParser (i.e., before ASVGMorph really does anything to it). It seems to download the DTD file from the Internet and then cannot properly parse it. Here is my setup: Up-to-date Pharo 3.0. Added XMLParser from the Configuration Browser. Example file can be found here: http://www.thetangentbundle.net/w/images/f/ff/lion.svg The following brings up an error: XMLDOMParser parseFileNamed: 'lion.svg' Cheers, Jeff -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Jan. 5, 2014

Re: [Pharo-dev] FogBugz (Case [Issue]12566) Kernel - Added Behavior>>#dependentClasses

by Alexandre Bergel

Hi! I have proposed a method Behavior>>dependentClasses, but apparently the Monkey is not really happy about it. I doubt the error in the generated report stems from this change. https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/6734//artifact/vali… No idea how to proceed from there. Cheers, Alexandre On Jan 5, 2014, at 6:42 AM, Pharo Issue Tracker <do-not-reply(a)pharo.fogbugz.com> wrote: > > Ulysse The Galactic Monkey From Outer Spaceedited Case 12566: Added Behavior>>#dependentClasses: > > Bug in Kernel: 1. Pharo Image > > Issue Validation Failed: https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/6734//artifact/vali… > Errors: 1 | Warnings: 1 | > > Status changed: > Resolved (Monkey is checking) Work Needed (Failing Test) > > Priority: 5 â Fix If Time Status: Work Needed (Failing Test) > Assigned to: Alexandre Bergel Milestone: Pharo3.0 > > > Go to Case > > Don't want FogBugz notifications anymore? Update your preferences. > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 5, 2014

Re: [Pharo-dev] what happened with RectangleMorph?

by Tudor Girba

Hi, On Sun, Jan 5, 2014 at 12:44 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > anyway, I added a 3.2 version, so I can reference it in my projects > Thanks. > (is *really* not good to reference to a baseline of an external project in > your ownâ¦ that just leads to a lot of pain :) > Not true. Moose is developed on the latest of Pharo, latest of Magritte, latest of PetitParser etc. For custom analysis purposes, my code runs on the latest of Moose. And it works. In fact, with this setup we can spot problems sooner than in any other environment exactly because. And, contrary to the expectations, we can react to these problems faster and cheaper, too. I will say it again: in our environment, in most cases it is better to stay on top of the latest baseline, than stuck on some previous version. The incremental choice of going from hardcoded version to hardcoded version does not scale for our tools. It can work for Pharo because it is at the bottom of the chain. but as you go up, the problem explodes exponentially. Doru > Esteban > > > On 05 Jan 2014, at 12:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > grrrr > > one of this days we should write the âmetacello compendiumâ, and create > agreements in ways to do things :P > > > > On 05 Jan 2014, at 12:41, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > I added a development version to point to the baseline :) > > Cheers, > Doru > > > On Sun, Jan 5, 2014 at 12:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > >> and you added a baseline 3.2 but not a version (not cool, doru, not cool >> :) >> >> On 05 Jan 2014, at 12:07, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> MAElementRow was still depending on RectangleMorph. >> But it was more a problem of the #stable release: it was not updated. >> >> Esteban >> >> On 05 Jan 2014, at 11:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi Esteban, >> >> I fixed this issue in Magritte-Morph a long time ago when we ported Moose >> to Pharo 3.0. What exactly is the issue? >> >> Cheers, >> Doru >> >> >> >> >> On Sun, Jan 5, 2014 at 11:34 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: >> >>> >>> On 05 Jan 2014, at 11:33, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> > >>> > On 05 Jan 2014, at 11:30, Esteban Lorenzano <estebanlm(a)gmail.com> >>> wrote: >>> > >>> >> â¦ is not there anymore. >>> >> And Magritte-Morph requires it :( >>> >> >>> >> my guess: I was another victim of Stef compulsion of giving us a >>> better and cleaning system :) >>> >> >>> > >>> > The thing was that it had no state nor behaviour different to Morphâ¦ >>> everywhere where it was used >>> > (and especially subclassed), one could just put Morph. One concept >>> lessâ¦ >>> >>> coolâ¦ :) >>> >>> > >>> >> But it should be replaced by what? >>> >> >>> > Morph >>> > >>> > Marcus >>> > >>> > >>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 5, 2014

Re: [Pharo-dev] issue 12506 Vm crashes vm when testing updates [A-L]

by Marcus Denker

On 05 Jan 2014, at 12:37, Nicolai Hess <nicolaihess(a)web.de> wrote: > But what of these changes were responsible for that you have to > have the sources file in your vm directory? (and only in 30664 and 30665!) > Or maybe because I did do a âSmalltalk cleanUpâ before uploading the recompiled image? > What are the exact steps for recompiling the image, you did? (just OpalCompiler recompileAll) > > > > 2014/1/5 Marcus Denker <marcus.denker(a)inria.fr> > > On 05 Jan 2014, at 12:08, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> My observations for issue 12506 >> >> - I can reproduce it on linux >> - segfault happens in primtiveNextInstance >> - tests A-L worked in 30663 >> - tests A-L segfault since 30664 >> - doesn't segfaults anymore if you open the image, change some code, save and close the image >> - it segfaults if you just run a subset of the A-L tests >> (pharo --nodisplay Pharo.image test --junit-xml-output 'FileSystem-Tests-Core' 'FreeTypeTests' 'FileSystem-Tests-Disk' 'FuelTests' 'FileSystem-Tests-Memory' 'KernelTests') >> - this "fail"-subset is different for the different images (30664, 30665, ...) >> - it does not segfault if you omit the junit-xml-output option >> > > -> Opal Regression Tests do run all tests (after recompiling) â> no problem ever > -> Monkey runs all tests for all âFix review neededâ â> no problem > >> And someone knows what happened with the image between version >> 30663 and 30666, because only >> 30664 and 30665 need the PharoV20.sources in the same directory as the VM, >> for all other versions it suffices if the sources are where the image file is. >> (Same as in http://forum.world.st/pharo-3-0-image-td4732890.html) >> > > These are the changes: > > 30663: > full diff: https://github.com/pharo-project/pharo-core/commit/c6adb033b0a42acbfe451955… > > > 12510 NautilusHistory entry for class methods loads instance methods > https://pharo.fogbugz.com/f/cases/12510 > > 12502 FileList MNU FileSystemPermission>><= > https://pharo.fogbugz.com/f/cases/12502 > > 12429 MessageBrowser loses changes > https://pharo.fogbugz.com/f/cases/12429 > > 12451 Error on Browse Full in Nautilus from class in group view > https://pharo.fogbugz.com/f/cases/12451 > > 30664 > full diff: https://github.com/pharo-project/pharo-core/commit/b84651feddc39d4336329e22… > > > 12517 SystemNavigation methodHierarchyBrowserForClass:selector: discards package information > https://pharo.fogbugz.com/f/cases/12517 > > 12476 Undeclared > https://pharo.fogbugz.com/f/cases/12476 > (remove Athens Tutorial as it introduces an Undeclared and was not in the image before) > > (in addition, I downloaded the image, recompiled and uploaded a new seed image as latest.zip). > > > 30665 > full diff: https://mail.google.com/mail/u/0/#search/30665/1435265c4bcdb3c2 > > - do not call #cleanUpForRelease on update > > (to check if this was the reason for the crash, it was not) > > >

Jan. 5, 2014

Re: [Pharo-dev] what happened with RectangleMorph?

by Esteban Lorenzano

anyway, I added a 3.2 version, so I can reference it in my projects (is *really* not good to reference to a baseline of an external project in your ownâ¦ that just leads to a lot of pain :) Esteban On 05 Jan 2014, at 12:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > grrrr > > one of this days we should write the âmetacello compendiumâ, and create agreements in ways to do things :P > > > > On 05 Jan 2014, at 12:41, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> I added a development version to point to the baseline :) >> >> Cheers, >> Doru >> >> >> On Sun, Jan 5, 2014 at 12:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> and you added a baseline 3.2 but not a version (not cool, doru, not cool :) >> >> On 05 Jan 2014, at 12:07, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> MAElementRow was still depending on RectangleMorph. >>> But it was more a problem of the #stable release: it was not updated. >>> >>> Esteban >>> >>> On 05 Jan 2014, at 11:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>>> Hi Esteban, >>>> >>>> I fixed this issue in Magritte-Morph a long time ago when we ported Moose to Pharo 3.0. What exactly is the issue? >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> >>>> >>>> On Sun, Jan 5, 2014 at 11:34 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> On 05 Jan 2014, at 11:33, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>>> >>>> > >>>> > On 05 Jan 2014, at 11:30, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> > >>>> >> â¦ is not there anymore. >>>> >> And Magritte-Morph requires it :( >>>> >> >>>> >> my guess: I was another victim of Stef compulsion of giving us a better and cleaning system :) >>>> >> >>>> > >>>> > The thing was that it had no state nor behaviour different to Morphâ¦ everywhere where it was used >>>> > (and especially subclassed), one could just put Morph. One concept lessâ¦ >>>> >>>> coolâ¦ :) >>>> >>>> > >>>> >> But it should be replaced by what? >>>> >> >>>> > Morph >>>> > >>>> > Marcus >>>> > >>>> > >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every thing has its own flow" >>> >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >

Jan. 5, 2014

Re: [Pharo-dev] what happened with RectangleMorph?

by Esteban Lorenzano

grrrr one of this days we should write the âmetacello compendiumâ, and create agreements in ways to do things :P On 05 Jan 2014, at 12:41, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I added a development version to point to the baseline :) > > Cheers, > Doru > > > On Sun, Jan 5, 2014 at 12:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > and you added a baseline 3.2 but not a version (not cool, doru, not cool :) > > On 05 Jan 2014, at 12:07, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> MAElementRow was still depending on RectangleMorph. >> But it was more a problem of the #stable release: it was not updated. >> >> Esteban >> >> On 05 Jan 2014, at 11:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> Hi Esteban, >>> >>> I fixed this issue in Magritte-Morph a long time ago when we ported Moose to Pharo 3.0. What exactly is the issue? >>> >>> Cheers, >>> Doru >>> >>> >>> >>> >>> On Sun, Jan 5, 2014 at 11:34 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> On 05 Jan 2014, at 11:33, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> > >>> > On 05 Jan 2014, at 11:30, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> > >>> >> â¦ is not there anymore. >>> >> And Magritte-Morph requires it :( >>> >> >>> >> my guess: I was another victim of Stef compulsion of giving us a better and cleaning system :) >>> >> >>> > >>> > The thing was that it had no state nor behaviour different to Morphâ¦ everywhere where it was used >>> > (and especially subclassed), one could just put Morph. One concept lessâ¦ >>> >>> coolâ¦ :) >>> >>> > >>> >> But it should be replaced by what? >>> >> >>> > Morph >>> > >>> > Marcus >>> > >>> > >>> >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >> > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Jan. 5, 2014

Re: [Pharo-dev] what happened with RectangleMorph?

by Tudor Girba

I added a development version to point to the baseline :) Cheers, Doru On Sun, Jan 5, 2014 at 12:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > and you added a baseline 3.2 but not a version (not cool, doru, not cool :) > > On 05 Jan 2014, at 12:07, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > MAElementRow was still depending on RectangleMorph. > But it was more a problem of the #stable release: it was not updated. > > Esteban > > On 05 Jan 2014, at 11:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi Esteban, > > I fixed this issue in Magritte-Morph a long time ago when we ported Moose > to Pharo 3.0. What exactly is the issue? > > Cheers, > Doru > > > > > On Sun, Jan 5, 2014 at 11:34 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > >> >> On 05 Jan 2014, at 11:33, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> > >> > On 05 Jan 2014, at 11:30, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> > >> >> â¦ is not there anymore. >> >> And Magritte-Morph requires it :( >> >> >> >> my guess: I was another victim of Stef compulsion of giving us a >> better and cleaning system :) >> >> >> > >> > The thing was that it had no state nor behaviour different to Morphâ¦ >> everywhere where it was used >> > (and especially subclassed), one could just put Morph. One concept lessâ¦ >> >> coolâ¦ :) >> >> > >> >> But it should be replaced by what? >> >> >> > Morph >> > >> > Marcus >> > >> > >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 5, 2014

Re: [Pharo-dev] issue 12506 Vm crashes vm when testing updates [A-L]

by Nicolai Hess

But what of these changes were responsible for that you have to have the sources file in your vm directory? (and only in 30664 and 30665!) What are the exact steps for recompiling the image, you did? (just OpalCompiler recompileAll) 2014/1/5 Marcus Denker <marcus.denker(a)inria.fr> > > On 05 Jan 2014, at 12:08, Nicolai Hess <nicolaihess(a)web.de> wrote: > > My observations for issue 12506 > > - I can reproduce it on linux > - segfault happens in primtiveNextInstance > - tests A-L worked in 30663 > - tests A-L segfault since 30664 > - doesn't segfaults anymore if you open the image, change some code, save > and close the image > - it segfaults if you just run a subset of the A-L tests > (pharo --nodisplay Pharo.image test --junit-xml-output > 'FileSystem-Tests-Core' 'FreeTypeTests' 'FileSystem-Tests-Disk' 'FuelTests' > 'FileSystem-Tests-Memory' 'KernelTests') > - this "fail"-subset is different for the different images (30664, 30665, > ...) > - it does not segfault if you omit the junit-xml-output option > > > -> Opal Regression Tests do run all tests (after recompiling) â> no > problem ever > -> Monkey runs all tests for all âFix review neededâ â> no problem > > And someone knows what happened with the image between version > 30663 and 30666, because only > 30664 and 30665 need the PharoV20.sources in the same directory as the VM, > for all other versions it suffices if the sources are where the image file > is. > (Same as in http://forum.world.st/pharo-3-0-image-td4732890.html) > > > These are the changes: > > 30663: > full diff: > https://github.com/pharo-project/pharo-core/commit/c6adb033b0a42acbfe451955… > > 12510 NautilusHistory entry for class methods loads instance methods > https://pharo.fogbugz.com/f/cases/12510 > > 12502 FileList MNU FileSystemPermission>><= > https://pharo.fogbugz.com/f/cases/12502 > > 12429 MessageBrowser loses changes > https://pharo.fogbugz.com/f/cases/12429 > > 12451 Error on Browse Full in Nautilus from class in group view > https://pharo.fogbugz.com/f/cases/12451 > 30664 > full diff: > https://github.com/pharo-project/pharo-core/commit/b84651feddc39d4336329e22… > > 12517 SystemNavigation methodHierarchyBrowserForClass:selector: discards > package information > https://pharo.fogbugz.com/f/cases/12517 > > 12476 Undeclared > https://pharo.fogbugz.com/f/cases/12476 > (remove Athens Tutorial as it introduces an Undeclared and was not in > the image before) > > (in addition, I downloaded the image, recompiled and uploaded a new seed > image as latest.zip). > > > 30665 > full diff: > https://mail.google.com/mail/u/0/#search/30665/1435265c4bcdb3c2 > > - do not call #cleanUpForRelease on update > > (to check if this was the reason for the crash, it was not) > > >

Jan. 5, 2014

Re: [Pharo-dev] issue 12506 Vm crashes vm when testing updates [A-L]

by Marcus Denker

On 05 Jan 2014, at 12:08, Nicolai Hess <nicolaihess(a)web.de> wrote: > My observations for issue 12506 > > - I can reproduce it on linux > - segfault happens in primtiveNextInstance > - tests A-L worked in 30663 > - tests A-L segfault since 30664 > - doesn't segfaults anymore if you open the image, change some code, save and close the image > - it segfaults if you just run a subset of the A-L tests > (pharo --nodisplay Pharo.image test --junit-xml-output 'FileSystem-Tests-Core' 'FreeTypeTests' 'FileSystem-Tests-Disk' 'FuelTests' 'FileSystem-Tests-Memory' 'KernelTests') > - this "fail"-subset is different for the different images (30664, 30665, ...) > - it does not segfault if you omit the junit-xml-output option > -> Opal Regression Tests do run all tests (after recompiling) â> no problem ever -> Monkey runs all tests for all âFix review neededâ â> no problem > And someone knows what happened with the image between version > 30663 and 30666, because only > 30664 and 30665 need the PharoV20.sources in the same directory as the VM, > for all other versions it suffices if the sources are where the image file is. > (Same as in http://forum.world.st/pharo-3-0-image-td4732890.html) > These are the changes: 30663: full diff: https://github.com/pharo-project/pharo-core/commit/c6adb033b0a42acbfe451955… 12510 NautilusHistory entry for class methods loads instance methods https://pharo.fogbugz.com/f/cases/12510 12502 FileList MNU FileSystemPermission>><= https://pharo.fogbugz.com/f/cases/12502 12429 MessageBrowser loses changes https://pharo.fogbugz.com/f/cases/12429 12451 Error on Browse Full in Nautilus from class in group view https://pharo.fogbugz.com/f/cases/12451 30664 full diff: https://github.com/pharo-project/pharo-core/commit/b84651feddc39d4336329e22… 12517 SystemNavigation methodHierarchyBrowserForClass:selector: discards package information https://pharo.fogbugz.com/f/cases/12517 12476 Undeclared https://pharo.fogbugz.com/f/cases/12476 (remove Athens Tutorial as it introduces an Undeclared and was not in the image before) (in addition, I downloaded the image, recompiled and uploaded a new seed image as latest.zip). 30665 full diff: https://mail.google.com/mail/u/0/#search/30665/1435265c4bcdb3c2 - do not call #cleanUpForRelease on update (to check if this was the reason for the crash, it was not)

Jan. 5, 2014

Re: [Pharo-dev] what happened with RectangleMorph?

by Esteban Lorenzano

and you added a baseline 3.2 but not a version (not cool, doru, not cool :) On 05 Jan 2014, at 12:07, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > MAElementRow was still depending on RectangleMorph. > But it was more a problem of the #stable release: it was not updated. > > Esteban > > On 05 Jan 2014, at 11:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi Esteban, >> >> I fixed this issue in Magritte-Morph a long time ago when we ported Moose to Pharo 3.0. What exactly is the issue? >> >> Cheers, >> Doru >> >> >> >> >> On Sun, Jan 5, 2014 at 11:34 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> On 05 Jan 2014, at 11:33, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> > >> > On 05 Jan 2014, at 11:30, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> > >> >> â¦ is not there anymore. >> >> And Magritte-Morph requires it :( >> >> >> >> my guess: I was another victim of Stef compulsion of giving us a better and cleaning system :) >> >> >> > >> > The thing was that it had no state nor behaviour different to Morphâ¦ everywhere where it was used >> > (and especially subclassed), one could just put Morph. One concept lessâ¦ >> >> coolâ¦ :) >> >> > >> >> But it should be replaced by what? >> >> >> > Morph >> > >> > Marcus >> > >> > >> >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >

Jan. 5, 2014