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

Re: [Pharo-project] BalloonCanvas>>drawPolygon

by Hilaire Fernandes

I turn DrGeo canvas to use Balloon to be at today standard regarding anti aliasing. Rendering polygon was the only issue I met with Balloon, even if its rendering is not exempt of unwished artifacts. No doubt Athens will be better but it adds the task to get Cairo on iOS and Android VM. Hilaire Le 24/02/2013 21:14, stephane ducasse a Ã©crit : > this is not an issue that we were aware of. At least I did not. > > On Feb 24, 2013, at 8:06 PM, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > >> Hello, >> >> When I use this method I get a beautiful red rectangle. >> And I can read http://bugs.squeak.org/view.php?id=7598 >> >> Do someone confirm the issue? >> >> Thanks >> >> Hilaire >> >> > > >

Feb. 25, 2013

[Pharo-project] new build slaves

by Camillo Bruni

- fedora - debian - windows xp now onto changing the VM-tests to run on all these platforms :)

Feb. 25, 2013

[Pharo-project] windows setup

by Camillo Bruni

I moved the windows setup from our internal wiki to the google code wiki https://code.google.com/p/pharo/wiki/SetupWindowsBuild

Feb. 25, 2013

Re: [Pharo-project] pharo-contribution triggering for new Pharo versions

by Camillo Bruni

On 2013-02-25, at 15:06, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 25, 2013, at 3:01 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > >> Hi, >> >> how to setup the jobs on pharo-contribution to be executed with every >> new Pharo version? I tried simply to setup URL trigger on >> http://pharo.gforge.inria.fr/ci/image/20/ but it was not started for >> new versions. > > For Opal, I set a content trigger on > > https://ci.inria.fr/pharo/job/Pharo-2.0/lastSuccessfulBuild/buildTimestamp I added a placeholder job https://ci.inria.fr/pharo-contribution/job/Pharo-2.0-Update-Trigger/ so you can just let it depend on that.

Feb. 25, 2013

Re: [Pharo-project] pharo-contribution triggering for new Pharo versions

by Marcus Denker

On Feb 25, 2013, at 3:01 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > how to setup the jobs on pharo-contribution to be executed with every > new Pharo version? I tried simply to setup URL trigger on > http://pharo.gforge.inria.fr/ci/image/20/ but it was not started for > new versions. For Opal, I set a content trigger on https://ci.inria.fr/pharo/job/Pharo-2.0/lastSuccessfulBuild/buildTimestamp > BTW, the job PharoKernel2.0-ReloadByMonticello that loads everyting > back to shrinked kernel is green again. > Very good! Marcus

Feb. 25, 2013

[Pharo-project] pharo-contribution triggering for new Pharo versions

by Pavel Krivanek

Hi, how to setup the jobs on pharo-contribution to be executed with every new Pharo version? I tried simply to setup URL trigger on http://pharo.gforge.inria.fr/ci/image/20/ but it was not started for new versions. BTW, the job PharoKernel2.0-ReloadByMonticello that loads everyting back to shrinked kernel is green again. -- Pavel

Feb. 25, 2013

Re: [Pharo-project] Refactor: rename class give Spec bug.

by Camillo Bruni

yep, the autocompletion keeps a history of used symbols, but doesn't properly free them :/ On 2013-02-25, at 14:52, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Interestingly, the autocomplete proposes it to me but a browse doesn't > work (in 20568). > > Like in WidgetBuilt browse gives nothing... > > Updating to 20568 doesn't solve the issue. Weird! > > Phil > > > 2013/2/25 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: >> Does the class WidgetBuilt exists in your system ? >> If not, maybe you should update your pharo version :) >> >> (This class exists in Pharo 20568) >> >> Ben >> >> On Feb 24, 2013, at 6:02 PM, phil(a)highoctane.be wrote: >> >> I was trying to get the Manuia Memory Monitor to work in Pharo 2.0 >> >> Got it working, nothing special: just say Smalltalk vm parameterAt: >> xxx instead of the SmalltalkImage current vmParameterAt: xxx >> >> Some Cmd-. needed but worked. >> >> Then, I wanted to have a look at how it worked. >> >> I noticed a class named: MMMemoryUsageIndicadorMorph and wanted to >> rename it to MMMemoryUsageIndicatorMorph. >> >> But I got a MNU: receiver of "model:widget:" is nil. >> >> Quite annoying. Screenshot in attach. >> >> Phil >> <PharoScreenshot.png> >> >> >

Feb. 25, 2013

Re: [Pharo-project] Refactor: rename class give Spec bug.

by phil＠highoctane.be

Interestingly, the autocomplete proposes it to me but a browse doesn't work (in 20568). Like in WidgetBuilt browse gives nothing... Updating to 20568 doesn't solve the issue. Weird! Phil 2013/2/25 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: > Does the class WidgetBuilt exists in your system ? > If not, maybe you should update your pharo version :) > > (This class exists in Pharo 20568) > > Ben > > On Feb 24, 2013, at 6:02 PM, phil(a)highoctane.be wrote: > > I was trying to get the Manuia Memory Monitor to work in Pharo 2.0 > > Got it working, nothing special: just say Smalltalk vm parameterAt: > xxx instead of the SmalltalkImage current vmParameterAt: xxx > > Some Cmd-. needed but worked. > > Then, I wanted to have a look at how it worked. > > I noticed a class named: MMMemoryUsageIndicadorMorph and wanted to > rename it to MMMemoryUsageIndicatorMorph. > > But I got a MNU: receiver of "model:widget:" is nil. > > Quite annoying. Screenshot in attach. > > Phil > <PharoScreenshot.png> > >

Feb. 25, 2013

Re: [Pharo-project] [update 2.0] #20569

by Camillo Bruni

On 2013-02-25, at 14:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 25, 2013, at 2:18 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > >> Why doesn't it work in CogVM? > > because we become: methods when installing a new trailer and cog does not support > become: on active methods. > >> Is condenseChanges ok now too? >> > I personally think we should not care. In 3.0 we really need get rid of this overly horrible > .sources and .changes monster for something trivially simplistic. > > We saved *a lot* on our Moore's Bank account the last yearsâ¦ at some point it is time > to invest that. Keep in mind that available RAM will double again until we release 3.0â¦ I am always impressed when I think about that :D... and even more when I see how little memory we actually use :P

Feb. 25, 2013

Re: [Pharo-project] [update 2.0] #20569

by Marcus Denker

On Feb 25, 2013, at 2:18 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Why doesn't it work in CogVM? because we become: methods when installing a new trailer and cog does not support become: on active methods. > Is condenseChanges ok now too? > I personally think we should not care. In 3.0 we really need get rid of this overly horrible .sources and .changes monster for something trivially simplistic. We saved *a lot* on our Moore's Bank account the last yearsâ¦ at some point it is time to invest that. Keep in mind that available RAM will double again until we release 3.0â¦ Marcus

Feb. 25, 2013