- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Confused by NewListExample

by Sergi Reyner

2014-04-23 11:01 GMT+01:00 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: > What do you think is the reaction people have reading this mail? > "NewList is awful, terrible, and eats babies"? Cheers, Sergi

April 23, 2014

[ANN] Gravatar for Pharo Smalltalk

by Torsten Bergmann

Hi, The "Gravatar" project is a simple wrapper for the Gravatar API allowing you to get small avatar images for a given registered email address. You can easily access and use it in Pharo. The project is located on STHub at http://smalltalkhub.com/#!/~TorstenBergmann/Gravatar To install just open the Pharo configuration browser and load "Gravatar" from there. You can also install manually, read the docu on the project page. Some examples: Gravatar imageURLFor: 'example(a)mail.com' If you require a different size just evaluate: Gravatar imageURLFor: 'example(a)mail.com' size: 32. If you need the real image you can use Pharos Zinc components suite to get the image form over HTTP and open it on your Pharo desk: |form| form := ZnEasy getJpeg: (self imageURLFor: 'example(a)mail.com'). form asMorph openInWorld In the end it is just a simple class - but I think it may be useful for others too. Thx T.

April 23, 2014

Re: [Pharo-dev] Confused by NewListExample

by Benjamin

What do you think is the reaction people have reading this mail? Ben On 22 Apr 2014, at 20:53, Stephan Eggermont <stephan(a)stack.nl> wrote: > - title toggling doesnât work > - doesnât have a usable size > - window title not set > - dragging doesnât work > - disallows selection in one place, > allows it somewhere else > - menu the same on list title > - uses halts directly instead of > calling a method on self displaying > the action (open a dialog, show a growl) > >

April 23, 2014

Re: [Pharo-dev] [Pharo CI] Linux slave problem solved

by Serge Stinckwich

Thank you marcus ! On Wed, Apr 23, 2014 at 3:28 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > The problem with the linux slaves is fixedâ¦ things should get normal again. > > " there was an inconsistency between libvirt (used on CloudStack's hypervisor nodes) > and the configuration of system's locale. As a consequence, a CloudStack test was failing sometimes, > leading to the removal of all the iptables rules and thus, to a full network disruption.â > > Seemingly that was quite hard to findâ¦ > > Marcus -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

April 23, 2014

Re: [Pharo-dev] [Pharo CI] Linux slave problem solved

by Max Leske

Thanks Marcus On 23.04.2014, at 10:28, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > The problem with the linux slaves is fixedâ¦ things should get normal again. > > " there was an inconsistency between libvirt (used on CloudStack's hypervisor nodes) > and the configuration of system's locale. As a consequence, a CloudStack test was failing sometimes, > leading to the removal of all the iptables rules and thus, to a full network disruption.â > > Seemingly that was quite hard to findâ¦ > > Marcus

April 23, 2014

[Pharo CI] Linux slave problem solved

by Marcus Denker

Hi, The problem with the linux slaves is fixedâ¦ things should get normal again. " there was an inconsistency between libvirt (used on CloudStack's hypervisor nodes) and the configuration of system's locale. As a consequence, a CloudStack test was failing sometimes, leading to the removal of all the iptables rules and thus, to a full network disruption.â Seemingly that was quite hard to findâ¦ Marcus

April 23, 2014

Re: [Pharo-dev] Phexample: API Change Proposal (was Phexample: Image Destroying Bug)

by Eliot Miranda

On Tue, Apr 22, 2014 at 7:26 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Stefan Marr-3 wrote > > Still, I will state it anyway: I donât like the change. > > I expected it to be unpopular ;) > > > Stefan Marr-3 wrote > > So, just for the sake of argument, are there other ways? > > I don't know. I'm open... > > As far as making #= mean something different the first time, I think this > gets us further down the difficult-to-understand rabbit hole. Also, #= is > not always sent; it's one of several options, like #beFalse. I guess maybe > you could say "as soon as any expectation is set up, revert to a > traditional > #=. But philosophically, hijacking #= disrupts the uniformity of the system > and adds to the user's cognitive load. Hijacking it only some of the time > makes it even less predictable. > +1. And, what's the specific argument for keeping the behavior of #=? Am I > missing some value that makes it worth all of the above? I think it's > important to separate the logic from the inertia inevitably accompanying > this kind of change. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Phexample-API-Change-Proposal-was-Phexample-Image-Des… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- best, Eliot

April 23, 2014

Re: [Pharo-dev] Phexample: API Change Proposal (was Phexample: Image Destroying Bug)

by Sean P. DeNigris

Stefan Marr-3 wrote > Still, I will state it anyway: I donât like the change. I expected it to be unpopular ;) Stefan Marr-3 wrote > So, just for the sake of argument, are there other ways? I don't know. I'm open... As far as making #= mean something different the first time, I think this gets us further down the difficult-to-understand rabbit hole. Also, #= is not always sent; it's one of several options, like #beFalse. I guess maybe you could say "as soon as any expectation is set up, revert to a traditional #=. But philosophically, hijacking #= disrupts the uniformity of the system and adds to the user's cognitive load. Hijacking it only some of the time makes it even less predictable. And, what's the specific argument for keeping the behavior of #=? Am I missing some value that makes it worth all of the above? I think it's important to separate the logic from the inertia inevitably accompanying this kind of change. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Phexample-API-Change-Proposal-was-Phexample-Image-Des… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 23, 2014

Re: [Pharo-dev] Smalltalk Hub on Chrome

by Sean P. DeNigris

It looks like this: <http://forum.world.st/file/n4755918/Screenshot_2014-04-22_22.png> ----- Cheers, Sean -- View this message in context: http://forum.world.st/Smalltalk-Hub-on-Chrome-tp4755788p4755918.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 23, 2014

Re: [Pharo-dev] [squeak-dev] Monticello Whitewash...

by Chris Muller

I would also be happy for that fix.. On Tue, Apr 22, 2014 at 6:18 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > ugh... after opening a multi-window browser on the Spur classes in the > automatically-created VMMaker image I notice once again that Monticello > doesn't preserve class organization order on load. grr.... Anyone up to > fixing this? > -- > best, > Eliot > > >

April 23, 2014