- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Vm-dev] [squeak-dev] Maintainer of FFI-Package

by Eliot Miranda

Hi Annick, On Mon, Sep 29, 2014 at 5:30 AM, Annick Fron <list(a)afceurope.com> wrote: > Hi, > > > I have recently made some experiments with pharo and FFI, and I have ran > into problems with callbacks. > I am using linux 32 bits. > First question : when calling a dynamic library is it necessary that it > exports all symbols ? What if symbols are noted Â« U Â» (undefined) ? > If you have undefined symbols in an external library, they need to be resoled by the VM or other libraries loaded in the system. If any are not resolved the library will fail to load. > 2) On one of my callbacks got the message Â« callback failed to own the VM > Â» . Have you any idea of where it comes from ? > Yes. This means you're trying to callback from a different thread than the VM thread. hat isn't supported yet. > 3) If the callback is called in a different thread, is it a problem ? > Yes. 4) On Pharo I have an error on the following : is it incorrect ? It is a 64 > bits problem ? > Using FFI Linux examples. > > testGetOurWindowLocation > "self new testGetOurWindowLocation" > > | display ourWindow aParent anX anY aWidth aHeight aBorderWidth aDepth | > display := X11Display XOpenDisplay: nil. > ourWindow := display ourWindow. > (Alien lookup: 'XGetGeometry' inLibrary: 'X11') > primFFICallResult: nil > withArguments: > {display. > ourWindow. > (aParent := Alien new: 4). > (anX := Alien new: 4). > (anY := Alien new: 4). > (aWidth := Alien new: 4). > (aHeight := Alien new: 4). > (aBorderWidth := Alien new: 4). > (aDepth := Alien new: 4)}. > (anX unsignedLongAt: 1) inspect > What's the error you get? Annick > Le 28 sept. 2014 Ã 21:44, David T. Lewis <lewis(a)mail.msen.com> a Ã©crit : > > > On Sun, Sep 28, 2014 at 09:04:59AM -0400, David T. Lewis wrote: > >> > >> On Sun, Sep 28, 2014 at 11:19:30AM +0200, Nicolai Hess wrote: > >>> Who is the maintainer of the FFI-Package for > >>> Squeak and/or Pharo ? > >>> I especially interested in the FFI-Unix examples > >>> and the state on working FFI on linux for current squeak release > >>> (AFAIK it does not work with "squeak all in one" 4.5) > >>> > >> > >> The FFI package, including the FFI-Unix examples that you mention, is at > >> http://source.squeak.org/FFI. > >> > >> The primary author was Andreas Raab. Eliot Miranda is the most recent > >> contributor, and he is probably the most knowledgeable in this area. > >> Currently, the Squeak core developers (those with commit rights to > Squeak > >> trunk) have commit rights to the FFI project, and can make updates as > needed. > >> > >> The FFI examples for Unix work with the old FFI plugin, which is still > >> present in the interpreter VM. The active development of Squeak FFI is > >> taking place in Cog, and I'm not sure if the old FFI examples work with > >> the newer plugins (which would be present in the Squeak all-in-one). > >> The FFI plugin in the interpreter VM (i.e. trunk VMMaker) needs to be > >> updated, and presumably the FFI examples may need some updates as well. > > > > A small but important correction: For the old plugin (currently in the > > interpreter VM), FFI works only for a 32-bit VM. It also works for a > 64-bit > > VM, but only if the patches in http://bugs.squeak.org/view.php?id=7237 > have > > been applied (in other words, if you compiled it yourself and included > > those patches). > > > > This is mainly of historical interest, although it is possible that some > > of the 64-bit patches will prove helpful for the newer FFI plugin. But > > the emphasis now should be on Eliot's more recent FFI work. > > > > Dave > > > > > > > -- best, Eliot

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Andrei Chis

I added backgroundColor a while back to make Glamour compatible with the dark theme. We should remove it. Sorry, I forgot about it. I can make a new version of glamour and submit a bugfix if you didn't do it already. On Tue, Sep 30, 2014 at 8:16 PM, stepharo <stepharo(a)free.fr> wrote: > This is annoying that the backgroundColor is ovverriden by > Glamour-Morphic-Theme. > Because now backgroundColor has been removed from the system and the > Polymorph-Widgets is dirty. > and I lost 40 min because I thought that this was my new changes that were > producing this. > Now if I reintroduce backgroundColor then Glamour is dirty. So I will do > it and Glamour should merge or I do not know > what. > > But we should not integrate systems with override and try to remove > override as much as possible. > > > â¦ that :) >> Which means that now we have a long way to polish them until Pharo4 >> release. >> >> Please test and provide feedback :) >> >> Esteban >> >> > >

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by stepharo

This is annoying that the backgroundColor is ovverriden by Glamour-Morphic-Theme. Because now backgroundColor has been removed from the system and the Polymorph-Widgets is dirty. and I lost 40 min because I thought that this was my new changes that were producing this. Now if I reintroduce backgroundColor then Glamour is dirty. So I will do it and Glamour should merge or I do not know what. But we should not integrate systems with override and try to remove override as much as possible. > â¦ that :) > Which means that now we have a long way to polish them until Pharo4 release. > > Please test and provide feedback :) > > Esteban >

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Esteban Lorenzano

still nothing. So now cmd+o does not work, because it collides with cmd+o+[others]. I hope now we are going to take this and move forward :) Esteban On Tue, Sep 30, 2014 at 6:40 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > So what did you decide to do with shortcuts? > > On 30 Sep 2014, at 18:38, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Ok. I'll do that. > > > Cheers, > Andrei > > On Tue, Sep 30, 2014 at 5:46 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> Hi, >> >> when fixing with configuration, this is the procedure: >> >> 1) you have to copy the configuration into the Inbox (so we keep >> history). >> 2) You complete the fields: âConfigurationOfâ and âConfigurationVersionâ. >> In your case, is: >> >> ConfigurationOf = GTPlayground >> ConfigurationVersion = 1.0.1 >> >> 3) *If* you have some preload or postload scripts to execute, you can >> fill the corresponding fields. >> >> cheers, >> Esteban >> >> >> On 30 Sep 2014, at 17:39, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: >> >> Thanks. >> >> First bugfix: >> https://pharo.fogbugz.com/f/cases/14121/Bugfixes-in-GTools-workspace-and-po… >> >> Is there a way to get a diff of the changes introduced by this >> configuration? (something like when working with slices) >> >> >> Andrei >> >> On Tue, Sep 30, 2014 at 5:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> new project GTools created in fogbugz :) >>> Esteban >>> >>> >>> On 30 Sep 2014, at 17:22, Andrei Chis <chisvasileandrei(a)gmail.com> >>> wrote: >>> >>> I guess a new category would make sense. >>> It would at least make it easy to find and keep track of those bugs >>> related to the GTools >>> >>> On Tue, Sep 30, 2014 at 5:00 PM, Nicolai Hess <nicolaihess(a)web.de> >>> wrote: >>> >>>> 2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>> >>>>> â¦ that :) >>>>> Which means that now we have a long way to polish them until Pharo4 >>>>> release. >>>>> >>>>> Please test and provide feedback :) >>>>> >>>>> Esteban >>>>> >>>> >>>> Great! >>>> >>>> How about a new Project category in fogbugz for GTools >>>> or should we use just "Tools"? >>>> >>>> Nicolai >>>> >>> >>> >>> >> >> > >

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Yuriy Tymchuk

So what did you decide to do with shortcuts? > On 30 Sep 2014, at 18:38, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Ok. I'll do that. > > > Cheers, > Andrei > > On Tue, Sep 30, 2014 at 5:46 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Hi, > > when fixing with configuration, this is the procedure: > > 1) you have to copy the configuration into the Inbox (so we keep history). > 2) You complete the fields: âConfigurationOfâ and âConfigurationVersionâ. In your case, is: > > ConfigurationOf = GTPlayground > ConfigurationVersion = 1.0.1 > > 3) *If* you have some preload or postload scripts to execute, you can fill the corresponding fields. > > cheers, > Esteban > > > On 30 Sep 2014, at 17:39, Andrei Chis <chisvasileandrei(a)gmail.com <mailto:chisvasileandrei@gmail.com>> wrote: > >> Thanks. >> >> First bugfix: https://pharo.fogbugz.com/f/cases/14121/Bugfixes-in-GTools-workspace-and-po… <https://pharo.fogbugz.com/f/cases/14121/Bugfixes-in-GTools-workspace-and-po…> >> >> Is there a way to get a diff of the changes introduced by this configuration? (something like when working with slices) >> >> >> Andrei >> >> On Tue, Sep 30, 2014 at 5:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> new project GTools created in fogbugz :) >> Esteban >> >> >> On 30 Sep 2014, at 17:22, Andrei Chis <chisvasileandrei(a)gmail.com <mailto:chisvasileandrei@gmail.com>> wrote: >> >>> I guess a new category would make sense. >>> It would at least make it easy to find and keep track of those bugs related to the GTools >>> >>> On Tue, Sep 30, 2014 at 5:00 PM, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >>> 2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >>> â¦ that :) >>> Which means that now we have a long way to polish them until Pharo4 release. >>> >>> Please test and provide feedback :) >>> >>> Esteban >>> >>> Great! >>> >>> How about a new Project category in fogbugz for GTools >>> or should we use just "Tools"? >>> >>> Nicolai >>> >> >> > >

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Andrei Chis

Ok. I'll do that. Cheers, Andrei On Tue, Sep 30, 2014 at 5:46 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > when fixing with configuration, this is the procedure: > > 1) you have to copy the configuration into the Inbox (so we keep history). > 2) You complete the fields: âConfigurationOfâ and âConfigurationVersionâ. > In your case, is: > > ConfigurationOf = GTPlayground > ConfigurationVersion = 1.0.1 > > 3) *If* you have some preload or postload scripts to execute, you can fill > the corresponding fields. > > cheers, > Esteban > > > On 30 Sep 2014, at 17:39, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Thanks. > > First bugfix: > https://pharo.fogbugz.com/f/cases/14121/Bugfixes-in-GTools-workspace-and-po… > > Is there a way to get a diff of the changes introduced by this > configuration? (something like when working with slices) > > > Andrei > > On Tue, Sep 30, 2014 at 5:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> new project GTools created in fogbugz :) >> Esteban >> >> >> On 30 Sep 2014, at 17:22, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: >> >> I guess a new category would make sense. >> It would at least make it easy to find and keep track of those bugs >> related to the GTools >> >> On Tue, Sep 30, 2014 at 5:00 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >>> 2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> â¦ that :) >>>> Which means that now we have a long way to polish them until Pharo4 >>>> release. >>>> >>>> Please test and provide feedback :) >>>> >>>> Esteban >>>> >>> >>> Great! >>> >>> How about a new Project category in fogbugz for GTools >>> or should we use just "Tools"? >>> >>> Nicolai >>> >> >> >> > >

Sept. 30, 2014

Re: [Pharo-dev] Context representation in current VM

by Martin McClure

On 09/29/2014 11:36 PM, stepharo wrote: > Martin > > you can add a paragraph saying that it is like that on old VM and that > now it is like described by eliot. Right. Regards, -Martin

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Esteban Lorenzano

Hi, when fixing with configuration, this is the procedure: 1) you have to copy the configuration into the Inbox (so we keep history). 2) You complete the fields: âConfigurationOfâ and âConfigurationVersionâ. In your case, is: ConfigurationOf = GTPlayground ConfigurationVersion = 1.0.1 3) *If* you have some preload or postload scripts to execute, you can fill the corresponding fields. cheers, Esteban On 30 Sep 2014, at 17:39, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Thanks. > > First bugfix: https://pharo.fogbugz.com/f/cases/14121/Bugfixes-in-GTools-workspace-and-po… > > Is there a way to get a diff of the changes introduced by this configuration? (something like when working with slices) > > > Andrei > > On Tue, Sep 30, 2014 at 5:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > new project GTools created in fogbugz :) > Esteban > > > On 30 Sep 2014, at 17:22, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > >> I guess a new category would make sense. >> It would at least make it easy to find and keep track of those bugs related to the GTools >> >> On Tue, Sep 30, 2014 at 5:00 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> 2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> â¦ that :) >> Which means that now we have a long way to polish them until Pharo4 release. >> >> Please test and provide feedback :) >> >> Esteban >> >> Great! >> >> How about a new Project category in fogbugz for GTools >> or should we use just "Tools"? >> >> Nicolai >> > >

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Andrei Chis

Thanks. First bugfix: https://pharo.fogbugz.com/f/cases/14121/Bugfixes-in-GTools-workspace-and-po… Is there a way to get a diff of the changes introduced by this configuration? (something like when working with slices) Andrei On Tue, Sep 30, 2014 at 5:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > new project GTools created in fogbugz :) > > Esteban > > > On 30 Sep 2014, at 17:22, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > I guess a new category would make sense. > It would at least make it easy to find and keep track of those bugs > related to the GTools > > On Tue, Sep 30, 2014 at 5:00 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> 2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> â¦ that :) >>> Which means that now we have a long way to polish them until Pharo4 >>> release. >>> >>> Please test and provide feedback :) >>> >>> Esteban >>> >> >> Great! >> >> How about a new Project category in fogbugz for GTools >> or should we use just "Tools"? >> >> Nicolai >> > > >

Sept. 30, 2014

Re: [Pharo-dev] GTools (GTPlayground and GTInspector) integrated

by Esteban Lorenzano

new project GTools created in fogbugz :) Esteban On 30 Sep 2014, at 17:22, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > I guess a new category would make sense. > It would at least make it easy to find and keep track of those bugs related to the GTools > > On Tue, Sep 30, 2014 at 5:00 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > 2014-09-30 14:51 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > â¦ that :) > Which means that now we have a long way to polish them until Pharo4 release. > > Please test and provide feedback :) > > Esteban > > Great! > > How about a new Project category in fogbugz for GTools > or should we use just "Tools"? > > Nicolai >

Sept. 30, 2014