March 2017 - Pharo-dev - lists.pharo.org

Tools > Calypso

by Ben Coman

hi Dennis, When installing Calypso from the Catalog, its a pain to have to search the forums to lookup up to do... #ClySystemBrowser asClass open. Could you add an entry under World > Tools? cheers -ben

March 3, 2017

Spotter - could ignore message parameters

by Ben Coman

Just a quick note... I find that I often copy a long keyword message like this... dispatchEvent: anEvent with: from source code and paste it into spotter. But Spotter gets confused by the "anEvent" parameter, and even spaces, so I have to edit all those out. It would be cool if Spotter was smart enough to ignore any characters that don't parse as part of message syntax. also btw, is there a keyboard shortcut to open Spotter on selected text much like we do for Senders and Implementors? cheers -ben

March 3, 2017

Re: [Pharo-dev] Epicea - showing latest lost changes

by Ben Coman

On Tue, Feb 28, 2017 at 7:04 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > Uko: OK, added it as: https://pharo.fogbugz.com/ > f/cases/19768/Epicea-Lost-Changes-Detector-Add-Apply-all- > button-on-top-of-the-list-of-change > > Stef: I see... each line should have a checkbox. I remember to see in > Spec's FastTableModel a method to enable that... I will try. > > Ben: I think that's not necessary because the EpLostChangesDetector > already opens a browser where only the "lost changes" are visible. Where > "lost changes" means everything logged by Epicea after last Image Save. > I paid particular attention this time to starting after a crash and one thing I'm uncertain about. Its good that the window says "Lost Changes Detected" but its not clear the meaning at the bottom where it says "22 filtered entries" Does this mean these 22 entries were not lost? Or is it some other reason? Also, I've a (only mild) concern that I can't see what these other entries are, since I don't know if they are important? Can you make it more explicit what the filter is? Oh, after a while I realise there is a tab for this. Perhaps at the bottom of the changes list you could say "22 filtered entries (see Active Filters tab)" to help slow people like me. So if 'remove all filters", what is the easy way to return to the identical previous "Lost Changes" filter. I realise now that I've been missing the old "indication of save points" Then I guess I'd be able to select that line and filter "afterwards" cheers -ben

March 3, 2017

Re: [Pharo-dev] [Moose-dev] Re: Segmentation fault on Moose 6.1 Build

by Ben Coman

To confirm specific reproducibility, using... http://files.pharo.org/image/60/60421.zip I did... $ cd opensmalltalk-vm $ git checkout d54edc56 $ git log commit d54edc5638c9f90c80f214e59e19240f8ead87f8 Author: Eliot Miranda <eliot.miranda(a)gmail.com> Date: Thu Mar 2 09:53:05 2017 -0800 CogVM source as per VMMaker.oscog-eem.2143 Fix regression in Sista sources due to receiverTags work. $ cd build.linux32x86/pharo.cog.spur/build.debug $ cd products/debug/phcogspurlinuxht $ pharo ~/temp/Case19785/Pharo-60421.image World > Playground, evaluate... surf := AthensCairoSurface extent: Display extent. Display getCanvas drawImage: surf asForm at: 0@0 70% ==> image seg fault 30% ==> PrimitiveFailed: primitive #primSignal:andReturnAs:fromContext: but doing Smalltalk snapshot: true andQuit: true. surf := AthensCairoSurface extent: Display extent. Display getCanvas drawImage: surf asForm at: 0@0. 100% ==> PrimitiveFailed: primitive #primSignal:andReturnAs:fromContext: Evaluate the following in Playground for 100% segfault from command line. EllipseMorph compile: 'step |surf| [ surf := AthensCairoSurface extent: Display extent. Display getCanvas drawImage: surf asForm at: 0@0. ] on: Error do: [ ]. self position: self position + (50@0). "To observe survival of seg fault" '. Smalltalk snapshot: true andQuit: true. EllipseMorph new openInWorld. btw, I'm on 32-bit Debian 8 Jessie $ uname -a Linux dom0 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) i686 GNU/Linux cheers -ben On Fri, Mar 3, 2017 at 12:08 AM, Blondeau Vincent < vincent.blondeau(a)worldline.com> wrote: > Hi Eliot, > > > > Thanks to take care of this issue! > > > > Pavel opened a bug issue here: > https://pharo.fogbugz.com/f/cases/19785/Athens-crashes-the-VM . You need the > latest Pharo image and VM and it crashes under Linux (32-bit) and OSX (El > Captain, 32-bit VM). And I personally tried with Windows7 and the bug > happens too. > > > > To reproduce: Morph new testAthensRender > > > > An extract of the opened issue: > > > > Edited by Pavel Krivanek 02/03/2017 (Today) 16:10 > > An empty surface crashes it too: > surf := AthensCairoSurface extent: Display extent. > Display getCanvas drawImage: surf asForm at: 0@0 > > > > The problem is in the method AthensCairoSurface>>#asForm where the previous > slice started to add 1 to surface heigth > > > > Well, I tried to revert AthensCairoSurface>>#asForm which fixes this > particular case but Roassal still crashes on copyBits > > > > Cheers, > > Vincent > > > > De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la part de > Eliot Miranda > EnvoyÃ© : jeudi 2 mars 2017 17:03 > Ã : Pharo Development List > Cc : Moose-related development; Squeak Virtual Machine Development > Discussion > Objet : [Moose-dev] Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build > > Hi Vincent, > > first, apologies for the inconvenience, second, thanks! I badly need > reproducible failure cases to get the remaining bugs out of the compactor > and you have just provided me with one. Can you send me the information I > need to reproduce the build? What platforms does it fall on? > > On Thu, Mar 2, 2017 at 2:23 AM, Blondeau Vincent > <vincent.blondeau(a)worldline.com> wrote: > > Hi, > > The latest builds of the Moose6.1 image are failing due to a segmentation > fault. > > Here is the link to the last build: > https://ci.inria.fr/moose/job/moose-6.1/550/console > > How can we fix this?

March 3, 2017

Re: [Pharo-dev] Helvetia in Pharo?

by Tudor Girba

Hi, Helvetia requires a couple of things: - Flexible parsing. Lukas built PetitParser for this and now PetitParser2 is even faster and more powerful (for example, with bounded seas parsing) while preserving the same flexibility. - Flexible compilation toolchain. At the time, Lukas employed a significant amount of overrides. Now we have Opal which makes this step easier. - Moldable development tools. GT was designed with moldability in mind so at least the debugging part should be easier to handle. We still need work in the area of syntax highlighting, completion and editing. Cheers, Doru > On Mar 2, 2017, at 9:12 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > > Hello Doru > > On 3/2/17, Tudor Girba <tudor(a)tudorgirba.com> wrote: > ..... >> That said, I do want to have mechanisms that allow us to embed other >> languages and DSLs in our environment. In this area I prefer the approach >> put forward by Helvetia because it is not invasive and highly flexible (and >> now should even not be expensive to have anymore). > > Just wondering what you mean by this. > Could you please elaborate a bit what you mean that it would now be > less expensive to have a Helvetia system in Pharo? The last time it > was implemented was in Pharo 1.1.2 ** > > Regards > Hannes > > **http://scg.unibe.ch/research/helvetia -- www.tudorgirba.com www.feenk.com "What we can governs what we wish."

March 2, 2017

Helvetia in Pharo?

by H. Hirzel

Hello Doru On 3/2/17, Tudor Girba <tudor(a)tudorgirba.com> wrote: ..... > That said, I do want to have mechanisms that allow us to embed other > languages and DSLs in our environment. In this area I prefer the approach > put forward by Helvetia because it is not invasive and highly flexible (and > now should even not be expensive to have anymore). Just wondering what you mean by this. Could you please elaborate a bit what you mean that it would now be less expensive to have a Helvetia system in Pharo? The last time it was implemented was in Pharo 1.1.2 ** Regards Hannes **http://scg.unibe.ch/research/helvetia

March 2, 2017

Re: [Pharo-dev] [squeak-dev] Re: [vwnc] Does anyone have a "new" string literal?

by DavidLeibs

Hi Doru, I understand your argument and I have heard it for years as to the reason not to make a programming language as good as what we have known how to do since the 1970s. I really don't have a very big dog in this fight (meaning that I don't care all that much whether these features end up in Smalltalk80), and I have felt that way for 20 years. I just wound up on this thread because I Googled myself in the context of working with another group on the development of advanced programming tools. I am much more interested in a programming environment that uses several iPad Pros and something like a ES2015+ Morphic framework that uses Force Touch plus Image Recognition on "real world passive objects" as a general approace to the "Use vs. Mention Problem" in graphical programming. The use versus mention problem is about not having any kind of a "run mode" vs. "design mode" switch. Having a finger press with pressure give you a number between: 0 and: 1 beats the hell out of shift+yellowButton hacks. :-) It's funny how the transition between programming and meta-programming is always there. Were I to do anything in Smalltalk and the Compiler and Parser frameworks still supported the #compilerClass and #parserClass invocations at the right place I know what I need to do to give myself a huge leg up in expressibility and performance. cheers, -David Leibs -- View this message in context: http://forum.world.st/Re-vwnc-Does-anyone-have-a-new-string-literal-tp46670… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 2, 2017

Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build

by Tudor Girba

Hi Eliot, There is no inconvenience! This is what it means when we have multiple projects working on the head of both the Pharo image and the VM: We improve significantly our ability to capture deep issues. While this might seem a rather risky proposition, but it is rather the opposite. To put it in perspective, since we moved the development of Moose to Pharo 6 (9 months ago) we had zero issues until now. I cannot urge people enough to adopt this approach. Cheers, Doru > On Mar 2, 2017, at 5:02 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Vincent, > > first, apologies for the inconvenience, second, thanks! I badly need reproducible failure cases to get the remaining bugs out of the compactor and you have just provided me with one. Can you send me the information I need to reproduce the build? What platforms does it fall on? > > On Thu, Mar 2, 2017 at 2:23 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > Hi, > > > > The latest builds of the Moose6.1 image are failing due to a segmentation fault. > > Here is the link to the last build: https://ci.inria.fr/moose/job/moose-6.1/550/console > > > > How can we fix this? > > > > Thanks in advance, > > > > Cheers, > > Vincent > > > > > !!!************************************************************************************* > "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!" > > > > -- > _,,,^..^,,,_ > best, Eliot -- www.tudorgirba.com www.feenk.com "From an abstract enough point of view, any two things are similar."

March 2, 2017

Re: [Pharo-dev] [Vm-dev] Segmentation fault on Moose 6.1 Build

by Pavel Krivanek

Hi Eliot, it seems to be purely FFI related issue. It works with an older version of the package Athens-Cairo with 32-bit dependent interface specification. Cheers, -- Pavel 2017-03-02 17:02 GMT+01:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > > Hi Vincent, > > first, apologies for the inconvenience, second, thanks! I badly need > reproducible failure cases to get the remaining bugs out of the compactor > and you have just provided me with one. Can you send me the information I > need to reproduce the build? What platforms does it fall on? > > On Thu, Mar 2, 2017 at 2:23 AM, Blondeau Vincent < > vincent.blondeau(a)worldline.com> wrote: > >> Hi, >> >> >> >> The latest builds of the Moose6.1 image are failing due to a segmentation >> fault. >> >> Here is the link to the last build: https://ci.inria.fr/moose/job/ >> moose-6.1/550/console >> >> >> >> How can we fix this? >> >> >> >> Thanks in advance, >> >> >> >> Cheers, >> >> Vincent >> >> >> >> !!!********************************************************* >> **************************** >> "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã >> l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par >> le secret professionnel. Si vous recevez ce message par erreur, merci d'en >> avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du >> message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de >> Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien >> que les meilleurs efforts soient faits pour maintenir cette transmission >> exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et >> sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant >> d'un virus transmis. >> >> This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive this >> e-mail in error, please notify the sender immediately and destroy it. As >> its integrity cannot be secured on the Internet, the Worldline liability >> cannot be triggered for the message content. Although the sender endeavours >> to maintain a computer virus-free network, the sender does not warrant that >> this transmission is virus-free and will not be liable for any damages >> resulting from any virus transmitted.!!!" >> > > > > -- > _,,,^..^,,,_ > best, Eliot > >

March 2, 2017

Re: [Pharo-dev] [Moose-dev] Re: Segmentation fault on Moose 6.1 Build

by Blondeau Vincent

Hi Eliot, Thanks to take care of this issue! Pavel opened a bug issue here: https://pharo.fogbugz.com/f/cases/19785/Athens-crashes-the-VM . You need the latest Pharo image and VM and it crashes under Linux (32-bit) and OSX (El Captain, 32-bit VM). And I personally tried with Windows7 and the bug happens too. To reproduce: Morph new testAthensRender An extract of the opened issue: Edited by Pavel Krivanek<https://pharo.fogbugz.com/f/personInfo/activity/36> 02/03/2017 (Today) 16:10<https://pharo.fogbugz.com/f/cases/19785/Athens-crashes-the-VM#BugEvent.1851…> An empty surface crashes it too: surf := AthensCairoSurface extent: Display extent. Display getCanvas drawImage: surf asForm at: 0@0<mailto:0@0> The problem is in the method AthensCairoSurface>>#asForm where the previous slice started to add 1 to surface heigth Well, I tried to revert AthensCairoSurface>>#asForm which fixes this particular case but Roassal still crashes on copyBits Cheers, Vincent De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la part de Eliot Miranda EnvoyÃ© : jeudi 2 mars 2017 17:03 Ã : Pharo Development List Cc : Moose-related development; Squeak Virtual Machine Development Discussion Objet : [Moose-dev] Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build Hi Vincent, first, apologies for the inconvenience, second, thanks! I badly need reproducible failure cases to get the remaining bugs out of the compactor and you have just provided me with one. Can you send me the information I need to reproduce the build? What platforms does it fall on? On Thu, Mar 2, 2017 at 2:23 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: Hi, The latest builds of the Moose6.1 image are failing due to a segmentation fault. Here is the link to the last build: https://ci.inria.fr/moose/job/moose-6.1/550/console How can we fix this? Thanks in advance, Cheers, Vincent !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!" -- _,,,^..^,,,_ best, Eliot !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

March 2, 2017