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

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

by David T. Lewis

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

Sept. 28, 2014

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

by Eliot Miranda

Hi Nicolai, On Sep 28, 2014, at 2:19 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > Who is the maintainer of the FFI-Package for > Squeak and/or Pharo ? I guess I'm the de facto maintainer because I'm the one who has changed things most recently, reimplementing the FFI plugin via the ThreadedFFIPlugin. > 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) Can you give me a reproducible case? I'd this with a Cog,Stack or Interpreter VM? Which specific things fail and how? > > regards > Nicolai Eliot (phone)

Sept. 28, 2014

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

by Eliot Miranda

Hi Martin, On Sep 28, 2014, at 1:18 AM, Martin McClure <martin(a)hand2mouse.com> wrote: > I'm updating the exceptions chapter of Deep Into Pharo, which currently contains this text: > > "...some Smalltalk implementations use the native C execution stack of the virtual machine to avoid creating objects all the time. > The current Pharo virtual machine does actually use full Smalltalk objects all the time; for speed, it recycles old method context objects rather than creating a new one for each message-send." > > Is this still true as of Pharo 4? I'd gotten the idea that this hadn't been true for a while, that the Cog VMs that Pharo is using did use a non-object stack to cache the top N contexts, only converting to actual Context objects when necessary. So both are true; it depends on the virtual machine. The interpreter VM works as described in the existing chapter. The Cog and Stack VMs work exactly as described in my blog post on context to stack mapping. It's not really the top N contexts. The stack zone, which is allocated on the native stack at startup, is divided into pages, each of which can hold up to ~ 40 activations (depending on stack depth, determined by #temps and nested call complexity). By default there are 160 pages. That either means 160 pages full of activations of a single process (eg one that is deeply recursive) or 1 page of up to 40 activations of 160 different processes or any combination in between. ie a page can only be used by a single process. When a new page is needed the oldest one is emptied by ensuring all activations on the page have contexts (on the heap), and updating the state of those contexts, effectively writing the page to the heap in the form of contexts. > Thanks, > > -Martin Eliot (phone)

Sept. 28, 2014

Re: [Pharo-dev] Data Analysis in Pharo

by Tudor Girba

Indeed, this is nice! It is for this reason that Moose is a data analysis platform, and what we see now is just only tip of the iceberg, Once these tools get embedded deep in the environment the potential simply explodes. Cheers, Doru On Sun, Sep 28, 2014 at 8:27 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > [sorry for the cross-post] > > Dear all, > > There has been quite some work around analyzing non-software related data. > The teams of Serge, Thierry and Noury have been doing wonderful things. I > am not sure you are aware of this, but I found this a nice achievement of > what our community can do. > > Using sensors networks in Jakarta, Indonesia, to monitor floods. > > https://www.facebook.com/ObjectProfile/photos/a.341189379300999.82969.34054… > > CAR: Components, Agents, and Robots > https://www.facebook.com/ObjectProfile/posts/704750642944869 > > Fantastic model from the Vietnam crew working on Ebola spreading > > https://www.facebook.com/ObjectProfile/photos/a.341189379300999.82969.34054… > > Another picture from the crew studying Ebola. > > https://www.facebook.com/ObjectProfile/photos/a.341189379300999.82969.34054… > > Ebola fatalities in Guinea. > > https://www.facebook.com/ObjectProfile/photos/a.341189379300999.82969.34054… > > Visualizing Astronomy pictures > https://www.facebook.com/ObjectProfile/posts/702429986510268 > > Visualization of Network Latency by Leonel Merino > http://t.co/xJN6qk1AEG > > Being this work, there is quite some sweat. This work does not happen > randomly, and their authors deserve our encouragements. > > I do not know if this make sense to crosspost all these urls (looks like a > spam isnât it?) but I am really happy to see all that happening. > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 28, 2014

Data Analysis in Pharo

by Alexandre Bergel

[sorry for the cross-post] Dear all, There has been quite some work around analyzing non-software related data. The teams of Serge, Thierry and Noury have been doing wonderful things. I am not sure you are aware of this, but I found this a nice achievement of what our community can do. Using sensors networks in Jakarta, Indonesia, to monitor floods. https://www.facebook.com/ObjectProfile/photos/a.341189379300999.82969.34054… CAR: Components, Agents, and Robots https://www.facebook.com/ObjectProfile/posts/704750642944869 Fantastic model from the Vietnam crew working on Ebola spreading https://www.facebook.com/ObjectProfile/photos/a.341189379300999.82969.34054… Another picture from the crew studying Ebola. https://www.facebook.com/ObjectProfile/photos/a.341189379300999.82969.34054… Ebola fatalities in Guinea. https://www.facebook.com/ObjectProfile/photos/a.341189379300999.82969.34054… Visualizing Astronomy pictures https://www.facebook.com/ObjectProfile/posts/702429986510268 Visualization of Network Latency by Leonel Merino http://t.co/xJN6qk1AEG Being this work, there is quite some sweat. This work does not happen randomly, and their authors deserve our encouragements. I do not know if this make sense to crosspost all these urls (looks like a spam isnât it?) but I am really happy to see all that happening. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 28, 2014

Re: [Pharo-dev] Pharo Balloon

by kilon alios

thanks for the info, I will take a deeper look into the code for more details. By flat I assume you mean squared , so that it does not need anti-aliasing so much. Anti-aliasing is definitely something that interests me deeply but so far I have been happy with Athens in this department hence why I asked about the usefulness of Balloon. So that means Morphic supports anti-aliasing through Ballon which is indeed very good news for me. On Sun, Sep 28, 2014 at 12:51 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > Athens came after Balloon. > Morphics rendering is based on Balloon. > Balloon engine is used for special rendering (see asBalloonCanvas), for > example > complex borders, it uses a plugin (B2DPlugin), has (has better) > antialiasing. > > I think balloon based rendering is much more importent for squeak than > pharo. > (Pharo looks more flat). Take a look at older squeak releases (screenshots) > to get a feel of it). > > > > > > 2014-09-28 10:43 GMT+02:00 kilon alios <kilon.alios(a)gmail.com>: > >> Can someone explain to me the importance of Pharo's Balloon engine ? What >> it offers that Athens and Morphic dont already have ? In which scenarios >> its worth using ? Where I can find documentation about it ? >> > >

Sept. 28, 2014

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

by David T. Lewis

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. Dave

Sept. 28, 2014

Re: [Pharo-dev] Pharo Balloon

by Nicolai Hess

Athens came after Balloon. Morphics rendering is based on Balloon. Balloon engine is used for special rendering (see asBalloonCanvas), for example complex borders, it uses a plugin (B2DPlugin), has (has better) antialiasing. I think balloon based rendering is much more importent for squeak than pharo. (Pharo looks more flat). Take a look at older squeak releases (screenshots) to get a feel of it). 2014-09-28 10:43 GMT+02:00 kilon alios <kilon.alios(a)gmail.com>: > Can someone explain to me the importance of Pharo's Balloon engine ? What > it offers that Athens and Morphic dont already have ? In which scenarios > its worth using ? Where I can find documentation about it ? >

Sept. 28, 2014

Maintainer of FFI-Package

by Nicolai Hess

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) regards Nicolai

Sept. 28, 2014

Pharo Balloon

by kilon alios

Can someone explain to me the importance of Pharo's Balloon engine ? What it offers that Athens and Morphic dont already have ? In which scenarios its worth using ? Where I can find documentation about it ?

Sept. 28, 2014