May 2017 - Pharo-users - lists.pharo.org

New booklet available

by Stephane Ducasse

A new booklet is joining the collection and it is on Voyage the object to document mapper developed by E. Lorenzano. Available in beta http://files.pharo.org/books/ and open to contributors at https://github.com/SquareBracketAssociates/Booklet-Voyage Enjoy Stef

May 14, 2017

Where does inspector store snippets?

by Sean P. DeNigris

I see the "play-cache" folder but no "inspect-cache". It would be nice to keep these when rebuilding an image from scratch... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Where-does-inspector-store-snippets-tp4947096.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 14, 2017

Re: [Pharo-users] PetitParser installation fails in Pharo 5.0

by Andreas Sunardi

Hi Ben, It's the linux download page from Pharo website http://pharo.org/gnu-linux-installation -- Andreas On Sun, May 14, 2017 at 5:20 AM, Ben Coman <btc(a)openinworld.com> wrote: > On Sun, May 14, 2017 at 8:03 AM, Andreas Sunardi <a.sunardi(a)gmail.com> > wrote: > > Hi Stephane, > > > > I shall read that Metacello chapter. I had considered this case closed > until > > you replied again. I took another peek and I think I found the root > cause. > > And for the sake of those who stumble on this email thread, I should > clarify > > this. > > > > This is probably related to my old email thread about running Pharo 5.0 > on > > linux with old glibc, which resulted in Pharo5.0-linux-oldLibC download > to > > work properly. > > http://lists.pharo.org/pipermail/pharo-users_lists. > pharo.org/2016-October/028431.html > > > > Following your solution, after installing PetitParser from Catalog > Browser > > in Windows version, I noticed the ConfigurationOfPetitParser version is > > TudorGirba.80, the version I had problem in linux. I then wondered why it > > didn't work on my linux with old glibc versions. Here's what I found > > > > Download and version (SystemVersion current imageVersionString): > > centos Pharo-5.0-50761- > > linux Pharo-5.0-50772- > > linux-oldLibC *Pharo-6.0-60257-* > > Can you provide the links for those downloads? > > cheers -ben > > > > > Pharo5.0-linux-oldLibC has image for Pharo 6.0. This is the one I use > where > > PetitParser installation failed. > > > > Using Catalog Browser, or Gofer instruction from smalltalkhub, for #load > and > > #loadDevelopment versions, PetitParser installation works fine for images > > that come from linux and centos versions, but not from linux-oldLibC. > > > > So, I believe that is the problem. I'm not sure what's the right > solution, > > but I think I can stay in this image and use TudorGirba.77 version or I > can > > try using image from linux version. > > > > Thanks again. If you hadn't replied about Metacello, I'd have never taken > > another look and found this. > > > > -- > > Andreas Sunardi > > > > On Sat, May 13, 2017 at 12:45 AM, Stephane Ducasse < > stepharo.self(a)gmail.com> > > wrote: > >> > >> You should read the beginning of the chapter on metacello. > >> Metacello is a map > >> Monticello element of the map > >> > >> You load elements by asking the map. > >> > >> Stef > >> > >> On Sat, May 13, 2017 at 3:43 AM, Andreas Sunardi <a.sunardi(a)gmail.com> > >> wrote: > >>> > >>> Hi Stephane, > >>> > >>> Indeed, PetitParser installation from Catalog Browser works just fine! > >>> Thank you very much. > >>> > >>> I used Monticello Browser before, but not Catalog Browser. I didn't > know > >>> this is the preferred method to install package. I don't think > DeepIntoPharo > >>> mentions about Catalog Browser, but maybe my version is outdated. > >>> > >>> Thanks again, Stephane. > >>> > >>> -- > >>> Andreas Sunardi > >>> > >>> On Fri, May 12, 2017 at 12:48 PM, Stephane Ducasse > >>> <stepharo.self(a)gmail.com> wrote: > >>>> > >>>> Sorry I meant the catalogBrowser. > >>>> Using the catalogBrowser on a given version of Pharo you should access > >>>> the configuration for this version (if people updated it correctly). > >>>> Our plan is to make sure that such configurations are validated. > >>>> Stef > >>>> > >>>> On Fri, May 12, 2017 at 9:47 PM, Stephane Ducasse > >>>> <stepharo.self(a)gmail.com> wrote: > >>>>> > >>>>> Hi andreas > >>>>> > >>>>> Normally you should be able to load a package using the > >>>>> ConfigurationBrowser and the configuration (now I do not know the > one of > >>>>> PetitParser) > >>>>> should take care of the pharo version for you. > >>>>> > >>>>> stef > >>>>> > >>>>> > >>>>> On Fri, May 12, 2017 at 7:06 PM, Andreas Sunardi < > a.sunardi(a)gmail.com> > >>>>> wrote: > >>>>>> > >>>>>> Following DeepIntoPharo, I tried to install PetitParser into my > Pharo > >>>>>> 5.0 image (I noticed PetitParser installation problem email in > March). It > >>>>>> failed with the message WinPlatform class was undefined. I went to > Moose's > >>>>>> PetitParser site in smalltalkhub and followed the instruction > there, and > >>>>>> this also failed. > >>>>>> > >>>>>> Out of frustration, I downloaded Moose 6.0 and thought I'd start > from > >>>>>> Moose image instead. But then I noticed Moose's PetitParser package > has > >>>>>> ConfigurationOfPetitParser from version TudorGirba.77 and the > instruction I > >>>>>> followed was trying to install it using version TudorGirba.80. Back > to my > >>>>>> Pharo 5 image, I unload/remove ConfigurationOfPetitParser and load > version > >>>>>> TudorGirba.77. And this works! > >>>>>> > >>>>>> But this way to solve PetitParser installation problem seems wrong. > I > >>>>>> figure if this could very well happen with other packages too. What > is the > >>>>>> right way to find package version that works with my image/pharo > version? Or > >>>>>> is this an issue with PetitParser package itself and should I > ask/report > >>>>>> this to Moose team? > >>>>>> > >>>>>> -- > >>>>>> Andreas Sunardi > >>>>> > >>>>> > >>>> > >>> > >> > > > >

May 14, 2017

Re: [Pharo-users] A Logo Proposal for Smalltalk

by horrido

Sven Van Caekenberghe-2 wrote > I think a stylised balloon is not bad, it just has to be less complex, > more logo like, more abstract. I've taken your comment to heart and I believe I've come up with the ideal logo: <http://forum.world.st/file/n4947093/hotairballoon-red-300.png> Beautifully abstract. Nice and simple. And it harkens back to the very famous BYTE 1981 cover *without tying Smalltalk to the past*. The hot air balloon motif for Smalltalk is universally recognized, and we cannot ignore it. -- View this message in context: http://forum.world.st/A-Logo-Proposal-for-Smalltalk-tp4945122p4947093.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 14, 2017

Re: [Pharo-users] PetitParser installation fails in Pharo 5.0

by Ben Coman

On Sun, May 14, 2017 at 8:03 AM, Andreas Sunardi <a.sunardi(a)gmail.com> wrote: > Hi Stephane, > > I shall read that Metacello chapter. I had considered this case closed until > you replied again. I took another peek and I think I found the root cause. > And for the sake of those who stumble on this email thread, I should clarify > this. > > This is probably related to my old email thread about running Pharo 5.0 on > linux with old glibc, which resulted in Pharo5.0-linux-oldLibC download to > work properly. > http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2016-October/0… > > Following your solution, after installing PetitParser from Catalog Browser > in Windows version, I noticed the ConfigurationOfPetitParser version is > TudorGirba.80, the version I had problem in linux. I then wondered why it > didn't work on my linux with old glibc versions. Here's what I found > > Download and version (SystemVersion current imageVersionString): > centos Pharo-5.0-50761- > linux Pharo-5.0-50772- > linux-oldLibC *Pharo-6.0-60257-* Can you provide the links for those downloads? cheers -ben > > Pharo5.0-linux-oldLibC has image for Pharo 6.0. This is the one I use where > PetitParser installation failed. > > Using Catalog Browser, or Gofer instruction from smalltalkhub, for #load and > #loadDevelopment versions, PetitParser installation works fine for images > that come from linux and centos versions, but not from linux-oldLibC. > > So, I believe that is the problem. I'm not sure what's the right solution, > but I think I can stay in this image and use TudorGirba.77 version or I can > try using image from linux version. > > Thanks again. If you hadn't replied about Metacello, I'd have never taken > another look and found this. > > -- > Andreas Sunardi > > On Sat, May 13, 2017 at 12:45 AM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: >> >> You should read the beginning of the chapter on metacello. >> Metacello is a map >> Monticello element of the map >> >> You load elements by asking the map. >> >> Stef >> >> On Sat, May 13, 2017 at 3:43 AM, Andreas Sunardi <a.sunardi(a)gmail.com> >> wrote: >>> >>> Hi Stephane, >>> >>> Indeed, PetitParser installation from Catalog Browser works just fine! >>> Thank you very much. >>> >>> I used Monticello Browser before, but not Catalog Browser. I didn't know >>> this is the preferred method to install package. I don't think DeepIntoPharo >>> mentions about Catalog Browser, but maybe my version is outdated. >>> >>> Thanks again, Stephane. >>> >>> -- >>> Andreas Sunardi >>> >>> On Fri, May 12, 2017 at 12:48 PM, Stephane Ducasse >>> <stepharo.self(a)gmail.com> wrote: >>>> >>>> Sorry I meant the catalogBrowser. >>>> Using the catalogBrowser on a given version of Pharo you should access >>>> the configuration for this version (if people updated it correctly). >>>> Our plan is to make sure that such configurations are validated. >>>> Stef >>>> >>>> On Fri, May 12, 2017 at 9:47 PM, Stephane Ducasse >>>> <stepharo.self(a)gmail.com> wrote: >>>>> >>>>> Hi andreas >>>>> >>>>> Normally you should be able to load a package using the >>>>> ConfigurationBrowser and the configuration (now I do not know the one of >>>>> PetitParser) >>>>> should take care of the pharo version for you. >>>>> >>>>> stef >>>>> >>>>> >>>>> On Fri, May 12, 2017 at 7:06 PM, Andreas Sunardi <a.sunardi(a)gmail.com> >>>>> wrote: >>>>>> >>>>>> Following DeepIntoPharo, I tried to install PetitParser into my Pharo >>>>>> 5.0 image (I noticed PetitParser installation problem email in March). It >>>>>> failed with the message WinPlatform class was undefined. I went to Moose's >>>>>> PetitParser site in smalltalkhub and followed the instruction there, and >>>>>> this also failed. >>>>>> >>>>>> Out of frustration, I downloaded Moose 6.0 and thought I'd start from >>>>>> Moose image instead. But then I noticed Moose's PetitParser package has >>>>>> ConfigurationOfPetitParser from version TudorGirba.77 and the instruction I >>>>>> followed was trying to install it using version TudorGirba.80. Back to my >>>>>> Pharo 5 image, I unload/remove ConfigurationOfPetitParser and load version >>>>>> TudorGirba.77. And this works! >>>>>> >>>>>> But this way to solve PetitParser installation problem seems wrong. I >>>>>> figure if this could very well happen with other packages too. What is the >>>>>> right way to find package version that works with my image/pharo version? Or >>>>>> is this an issue with PetitParser package itself and should I ask/report >>>>>> this to Moose team? >>>>>> >>>>>> -- >>>>>> Andreas Sunardi >>>>> >>>>> >>>> >>> >> >

May 14, 2017

Re: [Pharo-users] PetitParser installation fails in Pharo 5.0

by Stephane Ducasse

I do not really see why loading a package would be related to old glibc but may be :) With software.... who knows. Now what is important for you is that you always tries to load and produce configurations. Stef On Sun, May 14, 2017 at 2:03 AM, Andreas Sunardi <a.sunardi(a)gmail.com> wrote: > Hi Stephane, > > I shall read that Metacello chapter. I had considered this case closed > until you replied again. I took another peek and I think I found the root > cause. And for the sake of those who stumble on this email thread, I should > clarify this. > > This is probably related to my old email thread about running Pharo 5.0 on > linux with old glibc, which resulted in Pharo5.0-linux-oldLibC download to > work properly. > http://lists.pharo.org/pipermail/pharo-users_lists. > pharo.org/2016-October/028431.html > > Following your solution, after installing PetitParser from Catalog Browser > in Windows version, I noticed the ConfigurationOfPetitParser version is > TudorGirba.80, the version I had problem in linux. I then wondered why it > didn't work on my linux with old glibc versions. Here's what I found > > Download and version (SystemVersion current imageVersionString): > centos Pharo-5.0-50761- > linux Pharo-5.0-50772- > linux-oldLibC *Pharo-6.0-60257-* > > Pharo5.0-linux-oldLibC has image for Pharo 6.0. This is the one I use > where PetitParser installation failed. > > Using Catalog Browser, or Gofer instruction from smalltalkhub, for #load > and #loadDevelopment versions, PetitParser installation works fine for > images that come from linux and centos versions, but not from > linux-oldLibC. > > So, I believe that is the problem. I'm not sure what's the right solution, > but I think I can stay in this image and use TudorGirba.77 version or I can > try using image from linux version. > > Thanks again. If you hadn't replied about Metacello, I'd have never taken > another look and found this. > > -- > Andreas Sunardi > > On Sat, May 13, 2017 at 12:45 AM, Stephane Ducasse < > stepharo.self(a)gmail.com> wrote: > >> You should read the beginning of the chapter on metacello. >> Metacello is a map >> Monticello element of the map >> >> You load elements by asking the map. >> >> Stef >> >> On Sat, May 13, 2017 at 3:43 AM, Andreas Sunardi <a.sunardi(a)gmail.com> >> wrote: >> >>> Hi Stephane, >>> >>> Indeed, PetitParser installation from Catalog Browser works just fine! >>> Thank you very much. >>> >>> I used Monticello Browser before, but not Catalog Browser. I didn't know >>> this is the preferred method to install package. I don't think >>> DeepIntoPharo mentions about Catalog Browser, but maybe my version is >>> outdated. >>> >>> Thanks again, Stephane. >>> >>> -- >>> Andreas Sunardi >>> >>> On Fri, May 12, 2017 at 12:48 PM, Stephane Ducasse < >>> stepharo.self(a)gmail.com> wrote: >>> >>>> Sorry I meant the catalogBrowser. >>>> Using the catalogBrowser on a given version of Pharo you should access >>>> the configuration for this version (if people updated it correctly). >>>> Our plan is to make sure that such configurations are validated. >>>> Stef >>>> >>>> On Fri, May 12, 2017 at 9:47 PM, Stephane Ducasse < >>>> stepharo.self(a)gmail.com> wrote: >>>> >>>>> Hi andreas >>>>> >>>>> Normally you should be able to load a package using the >>>>> ConfigurationBrowser and the configuration (now I do not know the one of >>>>> PetitParser) >>>>> should take care of the pharo version for you. >>>>> >>>>> stef >>>>> >>>>> >>>>> On Fri, May 12, 2017 at 7:06 PM, Andreas Sunardi <a.sunardi(a)gmail.com> >>>>> wrote: >>>>> >>>>>> Following DeepIntoPharo, I tried to install PetitParser into my Pharo >>>>>> 5.0 image (I noticed PetitParser installation problem email in March). It >>>>>> failed with the message WinPlatform class was undefined. I went to Moose's >>>>>> PetitParser site in smalltalkhub and followed the instruction there, and >>>>>> this also failed. >>>>>> >>>>>> Out of frustration, I downloaded Moose 6.0 and thought I'd start from >>>>>> Moose image instead. But then I noticed Moose's PetitParser package has >>>>>> ConfigurationOfPetitParser from version TudorGirba.77 and the instruction I >>>>>> followed was trying to install it using version TudorGirba.80. Back to my >>>>>> Pharo 5 image, I unload/remove ConfigurationOfPetitParser and load version >>>>>> TudorGirba.77. And this works! >>>>>> >>>>>> But this way to solve PetitParser installation problem seems wrong. I >>>>>> figure if this could very well happen with other packages too. What is the >>>>>> right way to find package version that works with my image/pharo version? >>>>>> Or is this an issue with PetitParser package itself and should I ask/report >>>>>> this to Moose team? >>>>>> >>>>>> -- >>>>>> Andreas Sunardi >>>>>> >>>>> >>>>> >>>> >>> >> >

May 14, 2017

Re: [Pharo-users] Meta-clicking to bring up the halo

by Stephane Ducasse

Hi Normally bringing the halo is done using Shift+command(on mac)+alt. Now in Pharo there is also a Platform class and I do not know if the keybinding dispatch to it. So this is not clear that this is a vm things. With the introduction of SDL20 we want to manage all the event interpretation at the image level. Right now the VM is doing too much and badly - we handled touch events via OSWindow (SDL inside) - in the VM there is no way to know if some keys have been pressed. Moving all the logic to the image with make the vm slimmer and focused more on its key job. We should continue to integrate more SDL20. Stef On Sun, May 14, 2017 at 1:14 AM, horrido <horrido.hobbies(a)gmail.com> wrote: > I have Pharo 5.0 running under both Windows 7 and Raspbian (using the Spur > VM). Curiously, I can bring up the halo in Windows by meta-clicking, but > not > so in Raspbian. In Raspbian, the only thing I can do is 'add halo' from a > context menu (which I can also do in Windows). > > I'm just guessing but this issue must be related to the VM, since the Pharo > 5.0 image *should* be the same on both platforms (?). > > > > -- > View this message in context: http://forum.world.st/Meta- > clicking-to-bring-up-the-halo-tp4947067.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

May 14, 2017

Re: [Pharo-users] [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding

by monty

> Sent: Friday, May 12, 2017 at 5:30 AM > From: PBKResearch <peter(a)pbkresearch.co.uk> > To: "'Any question about pharo is welcome'" <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding > > With reference to Norbert's comment, there /may/ be an ambiguity about the > word 'header' in Udo's reply. It could refer to the http HEAD section, in > which case Norbert is of course right. It could also refer to the <head> > section of the html file, which is part of the content of the http response. > If it is the latter, this is similar to a question that Paul deBruicker > posted last November ("[Pharo-users] ZnClient GET, but just the content of > the <head> tag?"). I tried the method I devised for Paul's case on Udo's > problem website, and read the html header with no problem. Incidentally, the > header includes 'charset=iso-8859-1', which does not agree with Sven's > findings. > > In case it is of interest, I used XMLHTMLParser to read and parse the > header. Try the following in a Playground: > > par := XMLHTMLParser onURL: > 'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns- > with-a-new-(borrowed)-distribution-method/a/d-id/1328723'. > par parseDocumentUntil: [|top|(top := par topNode) notNil and: [ top > isElement and:[ top isNamed: 'body']]]. > par parsingResult findElementNamed: 'head'. > > If you 'Do it and go', the full header appears. The way I get it to stop > after the header may not be quite correct, because it uses > XMLHTMLParser>>topNode, which is a private method. On the other hand, I > can't see how to make the stop condition for > XMLHTMLParser>>parseDocumentUntil: depend on the parsed results without > using a private method. There's always #document. But since I can't see any possible harm, I'll make it public. > Hope this is helpful > > Peter Kenny > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of > Norbert Hartl > Sent: 12 May 2017 08:04 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] [Zinc] ZnInvalidUTF8: Illegal leading byte for > utf-8 encoding > > Just to mention. If you are not interested in the content body you could do > a HEAD request instead of GET. > > Norbert > > > Am 11.05.2017 um 22:44 schrieb Udo Schneider > <udo.schneider(a)homeaddress.de>: > > > > Hi Sven, > > > > that's perfect. To be honest I don't care about the content - I'm just > parsing the header. And even if there is a wrong decoding in there... I can > live with that. > > > > Thank you very very much! For your help but also your stuff in general. > > > > CU, > > > > Udo > > > > > >> Am 11/05/17 um 22:35 schrieb Sven Van Caekenberghe: > >> Hi Udo, > >>> On 11 May 2017, at 21:37, Udo Schneider <udo.schneider(a)homeaddress.de> > wrote: > >>> > >>> All, > >>> > >>> I'm hitting an error where fetching web content fails. The website does > indeed use invalid characters. > >>> > >>> The easiest way to reproduce: > >>> > >>> ZnEasy get: > 'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns- > with-a-new-(borrowed)-distribution-method/a/d-id/1328723' > >>> > >>> Is there any way to tell Zinc to simply ignore that error and to > continue? > >>> > >>> CU, > >>> > >>> Udo > >> That server/page has a mime-type text/plain with no explicit encoding > (charset) setting, so we have to guess. Like utf-8, pure latin1/iso88591 > does not work. The following does work, but you can't be sure everything > went well (beLenient takes some bytes as they are). > >> ZnDefaultCharacterEncoder > >> value: ZnCharacterEncoder latin1 beLenient > >> during: [ > >> ZnClient new > >> get: > 'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns- > with-a-new-(borrowed)-distribution-method/a/d-id/1328723'; > >> yourself ]. > >> I added some API earlier today, so that the following should also work > (you need to load Zn #bleedingEdge first). > >> ZnClient new > >> defaultEncoder: ZnCharacterEncoder latin1 beLenient; > >> get: > 'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns- > with-a-new-(borrowed)-distribution-method/a/d-id/1328723'; > >> yourself. > >> HTH, > >> Regards, > >> Sven > > > > > > > > > >

May 14, 2017

Re: [Pharo-users] PetitParser installation fails in Pharo 5.0

by Andreas Sunardi

Hi Stephane, I shall read that Metacello chapter. I had considered this case closed until you replied again. I took another peek and I think I found the root cause. And for the sake of those who stumble on this email thread, I should clarify this. This is probably related to my old email thread about running Pharo 5.0 on linux with old glibc, which resulted in Pharo5.0-linux-oldLibC download to work properly. http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2016-October/0… Following your solution, after installing PetitParser from Catalog Browser in Windows version, I noticed the ConfigurationOfPetitParser version is TudorGirba.80, the version I had problem in linux. I then wondered why it didn't work on my linux with old glibc versions. Here's what I found Download and version (SystemVersion current imageVersionString): centos Pharo-5.0-50761- linux Pharo-5.0-50772- linux-oldLibC *Pharo-6.0-60257-* Pharo5.0-linux-oldLibC has image for Pharo 6.0. This is the one I use where PetitParser installation failed. Using Catalog Browser, or Gofer instruction from smalltalkhub, for #load and #loadDevelopment versions, PetitParser installation works fine for images that come from linux and centos versions, but not from linux-oldLibC. So, I believe that is the problem. I'm not sure what's the right solution, but I think I can stay in this image and use TudorGirba.77 version or I can try using image from linux version. Thanks again. If you hadn't replied about Metacello, I'd have never taken another look and found this. -- Andreas Sunardi On Sat, May 13, 2017 at 12:45 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > You should read the beginning of the chapter on metacello. > Metacello is a map > Monticello element of the map > > You load elements by asking the map. > > Stef > > On Sat, May 13, 2017 at 3:43 AM, Andreas Sunardi <a.sunardi(a)gmail.com> > wrote: > >> Hi Stephane, >> >> Indeed, PetitParser installation from Catalog Browser works just fine! >> Thank you very much. >> >> I used Monticello Browser before, but not Catalog Browser. I didn't know >> this is the preferred method to install package. I don't think >> DeepIntoPharo mentions about Catalog Browser, but maybe my version is >> outdated. >> >> Thanks again, Stephane. >> >> -- >> Andreas Sunardi >> >> On Fri, May 12, 2017 at 12:48 PM, Stephane Ducasse < >> stepharo.self(a)gmail.com> wrote: >> >>> Sorry I meant the catalogBrowser. >>> Using the catalogBrowser on a given version of Pharo you should access >>> the configuration for this version (if people updated it correctly). >>> Our plan is to make sure that such configurations are validated. >>> Stef >>> >>> On Fri, May 12, 2017 at 9:47 PM, Stephane Ducasse < >>> stepharo.self(a)gmail.com> wrote: >>> >>>> Hi andreas >>>> >>>> Normally you should be able to load a package using the >>>> ConfigurationBrowser and the configuration (now I do not know the one of >>>> PetitParser) >>>> should take care of the pharo version for you. >>>> >>>> stef >>>> >>>> >>>> On Fri, May 12, 2017 at 7:06 PM, Andreas Sunardi <a.sunardi(a)gmail.com> >>>> wrote: >>>> >>>>> Following DeepIntoPharo, I tried to install PetitParser into my Pharo >>>>> 5.0 image (I noticed PetitParser installation problem email in March). It >>>>> failed with the message WinPlatform class was undefined. I went to Moose's >>>>> PetitParser site in smalltalkhub and followed the instruction there, and >>>>> this also failed. >>>>> >>>>> Out of frustration, I downloaded Moose 6.0 and thought I'd start from >>>>> Moose image instead. But then I noticed Moose's PetitParser package has >>>>> ConfigurationOfPetitParser from version TudorGirba.77 and the instruction I >>>>> followed was trying to install it using version TudorGirba.80. Back to my >>>>> Pharo 5 image, I unload/remove ConfigurationOfPetitParser and load version >>>>> TudorGirba.77. And this works! >>>>> >>>>> But this way to solve PetitParser installation problem seems wrong. I >>>>> figure if this could very well happen with other packages too. What is the >>>>> right way to find package version that works with my image/pharo version? >>>>> Or is this an issue with PetitParser package itself and should I ask/report >>>>> this to Moose team? >>>>> >>>>> -- >>>>> Andreas Sunardi >>>>> >>>> >>>> >>> >> >

May 14, 2017

Meta-clicking to bring up the halo

by horrido

I have Pharo 5.0 running under both Windows 7 and Raspbian (using the Spur VM). Curiously, I can bring up the halo in Windows by meta-clicking, but not so in Raspbian. In Raspbian, the only thing I can do is 'add halo' from a context menu (which I can also do in Windows). I'm just guessing but this issue must be related to the VM, since the Pharo 5.0 image *should* be the same on both platforms (?). -- View this message in context: http://forum.world.st/Meta-clicking-to-bring-up-the-halo-tp4947067.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 13, 2017