November 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] monticello not tracking recategorization

by Dale Henrichs

Cami, In the old days, the following event was registered: aSystemChangeNotifier notify: self ofSystemChangesOfItem: #method change: #Recategorized using: #methodMoved: in MCPackageManager class>>reregisterForNotificationsWith: So either that event is not being generated by the code or .... HTH, Dale ----- Original Message ----- | From: "Camillo Bruni" <camillobruni(a)gmail.com> | To: "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr> | Sent: Wednesday, November 28, 2012 11:06:12 AM | Subject: [Pharo-project] monticello not tracking recategorization | | currently monticello does not track method recategorization! | | anybody has a direct hint where to look at? | | in the mean time I start a binary search on the images to figure out | when we introduced the bug... |

Nov. 28, 2012

Re: [Pharo-project] a probably stupid question on canvas

by Igor Stasenko

On 28 November 2012 19:45, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > So reply to my question? > Should we merge alpha and color? > ifTrue: I will do it. > you mean ColorMappingCanvas and AlphaBlendingCanvas? i'd rather just remove them. IMO it doesn't worth time & effort. Especially in light of our dream to migrate on Athens :) yes, actually you can merge them and just give mapping as a block: mapingCanvas := otherCanvas asColorMappingCanvas: [:color | color darker ]. and so, you can get rid of all subclasses of ColorMappingCanvas alltogether. But besides of that, i don't particularily like how this is implemented: in order to do such mapping, it wraps the whole canvas protocol... I you would ask such lazy guy, like me, how to implement such functionality properly, i will find a lot of excuses why you should not do it like ColorMappingCanvas does. -- Best regards, Igor Stasenko.

Nov. 28, 2012

Re: [Pharo-project] Getting started with Athens

by Vanessa PeÃ±a Araya

On 11/28/2012 05:11 PM, Igor Stasenko wrote: > On 28 November 2012 20:01, Vanessa PeÃ±a Araya <van.c.pena(a)gmail.com> wrote: >> Stef >> >> I was trying Athens on Pharo 2.0 today (I really like Pharo 2.0!! <3), but I >> had a couple of problems with the examples. I was going to post it later but >> I'll add them here: >> >> - exampleDrawText >> With AthensCairoSurface StrikeFont does not understand glyphRendererOn: >> > and it shoudn't. > Make sure you enabled freetype library in settings. > > (LogicalFont familyName: 'Arial' pointSize: 20) realFont. > > should answer a freetype font, not strike font instance. I didn't know that, thanks. Works perfect now :) > >> With AthensBallonSurface does not understand Clear: >> >> If it helps, others examples like example8, exampleDrawForm and >> exampleDrawForm2 don't work for me with AthensBallonSurface. And >> exampleStrokeRect with AthensCairoSurface only shows a black rectangle. >> > Sorry, i did not tested balloon surface for a while. That's trivial to > fix though. > > The problem with balloon that many features may not work there properly, > because balloon capabilities is very limiting. > Balloon backend will stay there as a 'last resort', when nothing else works. > > .. but perhaps i should do a pass on it, to prevent to much bitrotting. Maybe a comment? I think that's hard to know when I was starting with Athens, a comment might help choosing the right surface. Thanks for the help. > >> I'm particularly interesting in the one with rendering text. >> > just make sure you don't use strike fonts. freetype should work fine with > balloon backend. > >> Thanks, >> Vanessa. >>

Nov. 28, 2012

Re: [Pharo-project] Getting started with Athens

by Igor Stasenko

On 28 November 2012 20:01, Vanessa PeÃ±a Araya <van.c.pena(a)gmail.com> wrote: > Stef > > I was trying Athens on Pharo 2.0 today (I really like Pharo 2.0!! <3), but I > had a couple of problems with the examples. I was going to post it later but > I'll add them here: > > - exampleDrawText > With AthensCairoSurface StrikeFont does not understand glyphRendererOn: > and it shoudn't. Make sure you enabled freetype library in settings. (LogicalFont familyName: 'Arial' pointSize: 20) realFont. should answer a freetype font, not strike font instance. > With AthensBallonSurface does not understand Clear: > > If it helps, others examples like example8, exampleDrawForm and > exampleDrawForm2 don't work for me with AthensBallonSurface. And > exampleStrokeRect with AthensCairoSurface only shows a black rectangle. > Sorry, i did not tested balloon surface for a while. That's trivial to fix though. The problem with balloon that many features may not work there properly, because balloon capabilities is very limiting. Balloon backend will stay there as a 'last resort', when nothing else works. .. but perhaps i should do a pass on it, to prevent to much bitrotting. > I'm particularly interesting in the one with rendering text. > just make sure you don't use strike fonts. freetype should work fine with balloon backend. > Thanks, > Vanessa. > -- Best regards, Igor Stasenko.

Nov. 28, 2012

Re: [Pharo-project] Getting started with Athens

by Casimiro de Almeida Barreto

In Fedora 17 it seems to be a CogVM problem. For instance, if I compile the B3DAccelerationPlugin as internal plugin, then OpenGL works OK. Otherwise it fails because libGL is not found. I had this problem before, just forgot about it (using stackVM). If someone know how to fix the problem I'm all ears. PS: I've tried all tricks concerning ld.conf.so, LD_LIBRARY_PATH, etc.

Nov. 28, 2012

Re: [Pharo-project] Getting started with Athens

by Vanessa PeÃ±a Araya

Actually this happens with Pharo 1.4 too, at least the example with rendering text :P Vanessa. On 11/28/2012 04:01 PM, Vanessa PeÃ±a Araya wrote: > Stef > > I was trying Athens on Pharo 2.0 today (I really like Pharo 2.0!! <3), > but I had a couple of problems with the examples. I was going to post > it later but I'll add them here: > > - exampleDrawText > With AthensCairoSurface StrikeFont does not understand glyphRendererOn: > > With AthensBallonSurface does not understand Clear: > > If it helps, others examples like example8, exampleDrawForm and > exampleDrawForm2 don't work for me with AthensBallonSurface. And > exampleStrokeRect with AthensCairoSurface only shows a black rectangle. > > I'm particularly interesting in the one with rendering text. > > Thanks, > Vanessa. > > On 11/28/2012 03:51 PM, StÃ©phane Ducasse wrote: >> Vanessa >> >> Now I suggest to work on pharo 2.0. >> >> Stef >> >> On Nov 28, 2012, at 7:39 PM, Vanessa PeÃ±a Araya wrote: >> >>> I had the same problem yesterday in Linux, My libcairo.so was on >>> another folder. I created a symlink of >>> >>> /usr/lib/libcairo.so >>> >>> and worked perfect without changing anything on Athens :) >>> >>> On 11/28/2012 03:19 PM, Casimiro de Almeida Barreto wrote: >>>> On 28-11-2012 14:34, Igor Stasenko wrote: >>>>> Try: >>>>> >>>>> CairoLibraryLoader getLibraryHandle >>>>> >>>>> also check what >>>>> >>>>> CairoLibraryLoader getLibraryPath >>>> had to change to /usr/lib/libcairo.so.1 >>>> Path is hard coded... not the best of worlds... >>>> But problems remainded... >>>> I'll have to take some time to see what's going on. >>>>> answers and if the cairo library exists under that path. >>>>> >>>>> If not, change the implementation to point to right location of >>>>> library. >>>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko. >>> >> >> >

Nov. 28, 2012

[Pharo-project] monticello not tracking recategorization

by Camillo Bruni

currently monticello does not track method recategorization! anybody has a direct hint where to look at? in the mean time I start a binary search on the images to figure out when we introduced the bug...

Nov. 28, 2012

Re: [Pharo-project] Getting started with Athens

by Vanessa PeÃ±a Araya

Stef I was trying Athens on Pharo 2.0 today (I really like Pharo 2.0!! <3), but I had a couple of problems with the examples. I was going to post it later but I'll add them here: - exampleDrawText With AthensCairoSurface StrikeFont does not understand glyphRendererOn: With AthensBallonSurface does not understand Clear: If it helps, others examples like example8, exampleDrawForm and exampleDrawForm2 don't work for me with AthensBallonSurface. And exampleStrokeRect with AthensCairoSurface only shows a black rectangle. I'm particularly interesting in the one with rendering text. Thanks, Vanessa. On 11/28/2012 03:51 PM, StÃ©phane Ducasse wrote: > Vanessa > > Now I suggest to work on pharo 2.0. > > Stef > > On Nov 28, 2012, at 7:39 PM, Vanessa PeÃ±a Araya wrote: > >> I had the same problem yesterday in Linux, My libcairo.so was on another folder. I created a symlink of >> >> /usr/lib/libcairo.so >> >> and worked perfect without changing anything on Athens :) >> >> On 11/28/2012 03:19 PM, Casimiro de Almeida Barreto wrote: >>> On 28-11-2012 14:34, Igor Stasenko wrote: >>>> Try: >>>> >>>> CairoLibraryLoader getLibraryHandle >>>> >>>> also check what >>>> >>>> CairoLibraryLoader getLibraryPath >>> had to change to /usr/lib/libcairo.so.1 >>> Path is hard coded... not the best of worlds... >>> But problems remainded... >>> I'll have to take some time to see what's going on. >>>> answers and if the cairo library exists under that path. >>>> >>>> If not, change the implementation to point to right location of library. >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko. >> > >

Nov. 28, 2012

Re: [Pharo-project] Getting started with Athens

by StÃ©phane Ducasse

Vanessa Now I suggest to work on pharo 2.0. Stef On Nov 28, 2012, at 7:39 PM, Vanessa PeÃ±a Araya wrote: > I had the same problem yesterday in Linux, My libcairo.so was on another folder. I created a symlink of > > /usr/lib/libcairo.so > > and worked perfect without changing anything on Athens :) > > On 11/28/2012 03:19 PM, Casimiro de Almeida Barreto wrote: >> On 28-11-2012 14:34, Igor Stasenko wrote: >>> Try: >>> >>> CairoLibraryLoader getLibraryHandle >>> >>> also check what >>> >>> CairoLibraryLoader getLibraryPath >> had to change to /usr/lib/libcairo.so.1 >> Path is hard coded... not the best of worlds... >> But problems remainded... >> I'll have to take some time to see what's going on. >>> answers and if the cairo library exists under that path. >>> >>> If not, change the implementation to point to right location of library. >>> >>> -- >>> Best regards, >>> Igor Stasenko. >> > >

Nov. 28, 2012

Re: [Pharo-project] a probably stupid question on canvas

by StÃ©phane Ducasse

So reply to my question? Should we merge alpha and color? ifTrue: I will do it. Stef On Nov 28, 2012, at 12:11 AM, Igor Stasenko wrote: > And this is not the only example. > same goes for > BitBlt > GrafPort > WarpBlt > > which are products of adding new features to VM without > reconsidering/cleaning up > the whole model/interface(s). > And of course, as always, keeping backwards compatibility is a good excuse. ;) > > so we end up with many faces of same beast.. > and as original developers gone, nobody dares go inside and clean it up. > > -- > Best regards, > Igor Stasenko. >

Nov. 28, 2012