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

Notifications with more details (something like improved #inform:

by Offray Vladimir Luna CÃ¡rdenas

Hi, Nowadays task bar in several desktop environments gives you a condensed view of notifications and in you click on them, can see detailed notifications. For example they show a notification saying "5 new telegram messages" and you click on the notification and shows individual messages. We have #inform: but if you use it for several notifications they pile up and soon becomes unmanageable. Do we have something like that desktop notifications with more details in Pharo? Thanks, Offray

April 4, 2017

Survey about the Roassal visualization engine

by Alexandre Bergel

Hi! We are doing a survey about Roassal. Giving about 2 minutes of your time to fill the survey can have a tremendous impact on it. https://goo.gl/forms/zEt7VdkLSYvBG6jf2 Help us improving Roassal :-) The Object Profile team

April 3, 2017

Re: [Pharo-users] FileReference / and parent

by Sven Van Caekenberghe

> On 3 Apr 2017, at 21:11, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Sven, > > On Mon, Apr 03, 2017 at 06:06:57PM +0200, Sven Van Caekenberghe wrote: >> That might be OK, I guess, but you have to add enough unit tests to >> cover all edge cases. > > I'll certainly have unit tests in place when I submit the proposed > changes. (the current unit tests have the same results after > applying the code below). > > Which edge cases are you thinking of? As arg: empty / foo/ /foo /foo/ // //foo foo// //foo// /foo//bar/ I guess you get the idea. > Thanks! > Alistair > > >> In the past, the reasoning was, AFAIU, that the right side argument to >> #/ did not get interpreted. >> >> But that indeed gives some inconsistencies. >> >>> On 3 Apr 2017, at 14:04, Alistair Grant <akgrant0710(a)gmail.com> >>> wrote: >>> >>> Hi All, >>> >>> I previously suggested a change to Path>>/ which actually covered >>> two issues: >>> >>> 1. The handling of the parent directory notation, i.e. ".." 2. The >>> construction of path segments when appending a string. >>> >>> As Damien pointed out, the first issue needs a bit more >>> consideration. >>> >>> I think the second point is still problematic and can be addressed >>> separately. In particular: >>> >>> ('/a/b/c' asFileReference / 'd/e/f') parent "File @ /a/b/c" >>> >>> I would expect the result to be "File @ /a/b/c/d/e" >>> >>> The fix is straightforward (although someone may be able to propose >>> a more elgant solution): >>> >>> -- >>> / aString | path additionalPath index | >>> >>> aString isEmptyOrNil ifTrue: [ Error signal: 'Path element >>> cannot be empty or nil']. >>> >>> additionalPath := Path from: aString. path := self >>> class new: self size + additionalPath size. path copyFrom: >>> self. index := self size + 1. additionalPath do: [ :each | >>> path at: index put: each. index := index + 1. ]. ^ path >>> -- >>> >>> 1. Do you agree with the proposed change? >>> 2. (Assuming you agree): >>> Should we target Pharo 6.0 or 7.0? On one side, this is clearly a >>> bug, on the other, no one has reported it to date, so it isn't >>> having a big impact. >>> >>> Thanks, Alistair >>> >> >> >

April 3, 2017

Re: [Pharo-users] FileReference / and parent

by Alistair Grant

Hi Sven, On Mon, Apr 03, 2017 at 06:06:57PM +0200, Sven Van Caekenberghe wrote: > That might be OK, I guess, but you have to add enough unit tests to > cover all edge cases. I'll certainly have unit tests in place when I submit the proposed changes. (the current unit tests have the same results after applying the code below). Which edge cases are you thinking of? Thanks! Alistair > In the past, the reasoning was, AFAIU, that the right side argument to > #/ did not get interpreted. > > But that indeed gives some inconsistencies. > > > On 3 Apr 2017, at 14:04, Alistair Grant <akgrant0710(a)gmail.com> > > wrote: > > > > Hi All, > > > > I previously suggested a change to Path>>/ which actually covered > > two issues: > > > > 1. The handling of the parent directory notation, i.e. ".." 2. The > > construction of path segments when appending a string. > > > > As Damien pointed out, the first issue needs a bit more > > consideration. > > > > I think the second point is still problematic and can be addressed > > separately. In particular: > > > > ('/a/b/c' asFileReference / 'd/e/f') parent "File @ /a/b/c" > > > > I would expect the result to be "File @ /a/b/c/d/e" > > > > The fix is straightforward (although someone may be able to propose > > a more elgant solution): > > > > -- > > / aString | path additionalPath index | > > > > aString isEmptyOrNil ifTrue: [ Error signal: 'Path element > > cannot be empty or nil']. > > > > additionalPath := Path from: aString. path := self > > class new: self size + additionalPath size. path copyFrom: > > self. index := self size + 1. additionalPath do: [ :each | > > path at: index put: each. index := index + 1. ]. ^ path > > -- > > > > 1. Do you agree with the proposed change? > > 2. (Assuming you agree): > > Should we target Pharo 6.0 or 7.0? On one side, this is clearly a > > bug, on the other, no one has reported it to date, so it isn't > > having a big impact. > > > > Thanks, Alistair > > > >

April 3, 2017

Re: [Pharo-users] Today is GSOC deadline

by Offray Vladimir Luna CÃ¡rdenas

Thanks Serge and all the others behind the logistics to make Pharo GSoC possible. Cheers, Offray On 03/04/17 04:07, Serge Stinckwich wrote: > Dear all, > > just a reminder for all mentors&students: the deadline for submitting > your GSOC proposal is today at 6pm CEST. You have to submit the final > pdf paper before that time. > > Thank you. > Regards,

April 3, 2017

Re: [Pharo-users] FileReference / and parent

by Sven Van Caekenberghe

That might be OK, I guess, but you have to add enough unit tests to cover all edge cases. In the past, the reasoning was, AFAIU, that the right side argument to #/ did not get interpreted. But that indeed gives some inconsistencies. > On 3 Apr 2017, at 14:04, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi All, > > I previously suggested a change to Path>>/ which actually covered two > issues: > > 1. The handling of the parent directory notation, i.e. ".." > 2. The construction of path segments when appending a string. > > As Damien pointed out, the first issue needs a bit more consideration. > > I think the second point is still problematic and can be addressed > separately. In particular: > > ('/a/b/c' asFileReference / 'd/e/f') parent "File @ /a/b/c" > > I would expect the result to be "File @ /a/b/c/d/e" > > The fix is straightforward (although someone may be able to propose a > more elgant solution): > > -- > / aString > | path additionalPath index | > > aString isEmptyOrNil > ifTrue: [ Error signal: 'Path element cannot be empty or nil']. > > additionalPath := Path from: aString. > path := self class new: self size + additionalPath size. > path copyFrom: self. > index := self size + 1. > additionalPath do: [ :each | > path at: index put: each. > index := index + 1. > ]. > ^ path > -- > > 1. Do you agree with the proposed change? > 2. (Assuming you agree): Should we target Pharo 6.0 or 7.0? > On one side, this is clearly a bug, on the other, no one has reported > it to date, so it isn't having a big impact. > > Thanks, > Alistair >

April 3, 2017

FileReference / and parent

by Alistair Grant

Hi All, I previously suggested a change to Path>>/ which actually covered two issues: 1. The handling of the parent directory notation, i.e. ".." 2. The construction of path segments when appending a string. As Damien pointed out, the first issue needs a bit more consideration. I think the second point is still problematic and can be addressed separately. In particular: ('/a/b/c' asFileReference / 'd/e/f') parent "File @ /a/b/c" I would expect the result to be "File @ /a/b/c/d/e" The fix is straightforward (although someone may be able to propose a more elgant solution): -- / aString | path additionalPath index | aString isEmptyOrNil ifTrue: [ Error signal: 'Path element cannot be empty or nil']. additionalPath := Path from: aString. path := self class new: self size + additionalPath size. path copyFrom: self. index := self size + 1. additionalPath do: [ :each | path at: index put: each. index := index + 1. ]. ^ path -- 1. Do you agree with the proposed change? 2. (Assuming you agree): Should we target Pharo 6.0 or 7.0? On one side, this is clearly a bug, on the other, no one has reported it to date, so it isn't having a big impact. Thanks, Alistair

April 3, 2017

Today is GSOC deadline

by Serge Stinckwich

Dear all, just a reminder for all mentors&students: the deadline for submitting your GSOC proposal is today at 6pm CEST. You have to submit the final pdf paper before that time. Thank you. Regards, -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

April 3, 2017

Re: [Pharo-users] Breaking News

by Offray Vladimir Luna CÃ¡rdenas

Hi, Comments below ;-) On 02/04/17 04:18, Ben Coman wrote: > > > On Sun, Apr 2, 2017 at 4:54 AM, Dimitris Chloupis > <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: > > Ironically and this is not April's Fool joke, Scratch has been > exploding in popularity > > https://www.tiobe.com/tiobe-index/ > <https://www.tiobe.com/tiobe-index/> > > https://www.tiobe.com/tiobe-index/scratch/ > <https://www.tiobe.com/tiobe-index/scratch/> > > So what Smalltalk has failed to achieve, Scratch is achieving it > now even though it was made with Smalltalk. Makes sense though, > many countries have been pushing coding into schools and Scratch > was always a No1 choice, its just lately this push has been a lot > more severe because of the severe lack of pro and amateur coders. > > > With a 12 month lag, you might say it fairly well follows the rise of > RPi sales... > https://docs.google.com/spreadsheets/d/1zWwpcckDEEVAhNH3y7JQGxxbjP42nUywPOz… > Now Pharo is aiming at a business market and maybe not kids, > but some of those kids have parents that in the tech industry, > and of course they will want to help their kid's with their projects. > So now you have a few hours attention from a decision maker > who otherwise wouldn't have time to poke something new with a barge pole. > On the path of passing from visual metaphors to coding I remember using Scratch, Etoys, and Bots Inc (in that order) with my undergrad students in 2006 and 2007. Now I'm using data activism to join visualization with code for grown ups. I think that this kind of bridges in two directions (from code to visuals and vice-versa) are important. In that sense, project like Phratch are a good way to introduce novices to programming and let them to deconstruct/traverse their way to underlying coding behind GUI without all the extra layers that now has Scratch, since its "migration to the web". Complementary ways of approaching the divide between coders and non coders are important to get more diversity, with kids, data scientist journalist and activists and others knowing the advantages of live coding moldability and others that are brought by the Pharo/Smalltalk Ecosystem. > > > On Sat, Apr 1, 2017 at 8:54 PM Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: > > Well... I was just trying to get myself unembarrassed... but > was not catch was not mine... next years I will let it run > wildly and help to it. > > > Of course :) > For a few minutes it *really* made my day also (until I searched and > the other half of my brain caught up). > With all this post-true issues now is difficult for more me not to ask for sources... is more difficult to fall into Aprils fools, but asking for sources on a fake new on that day is kind of falling in the joke :-). Cheers, Offray

April 3, 2017

Re: [Pharo-users] PetitParser question parsing HTML meta tags

by monty

XMLParserHTML is the fastest HTML parser on Pharo, Squeak, and GS. It has DOM and SAX parsers and works with other libs such as PharoExtras/XPath and PharoExtras/XMLParserStAX. Element and attribute names are normalized to lowercase, and printing XML DOM trees back as HTML is complicated by browsers not recognizing XML-style self-closing tags ending with "/>" for some elements (like "script"), so use #printedWithoutSelfClosingTags/#printWithoutSelfClosingTagsOn:/#printWithoutSelfClosingTagsToFileNamed: instead. > Sent: Thursday, March 30, 2017 at 1:58 PM > From: "PAUL DEBRUICKER" <pdebruic(a)gmail.com> > To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] PetitParser question parsing HTML meta tags > > This is kind of a "I'm tired of thinking about this and not making much progress for the amount of time I'm putting in question" but here it is: > > > > I'm trying to parse descriptions from HTML meta elements. I can't use Soup because there isn't a working GemStone port. > > I've got it to work with the structure: > > <meta name="description" content="my description"> > > and > > <meta name="Description" content="my description"> > > > but I'm running into instances of: > > <meta http-equiv="description" content="my description"> > > and > > <meta http-equiv="Description" content="my description"> > > > and am having trouble adapting my parsing code (such as it is). > > > The parsing code that addresses the first two cases is: > > > > parseHtmlPageForDescription: htmlString > | startParser endParser ppStream descParser result text lower str doubleQuoteIndex | > lower := 'escription' asParser. > startParser := '<meta name=' asParser , #'any' asParser , #'any' asParser. > endParser := '>' asParser. > ppStream := htmlString readStream asPetitStream. > descParser := ((#'any' asParser starLazy: startParser , lower) > , (#'any' asParser starLazy: endParser)) ==> #'second'. > result := descParser parse: ppStream. > text := (result > inject: (WriteStream on: String new) > into: [ :stream :char | > stream nextPut: char. > stream ]) > contents trimBoth. > str := text copyFrom: (text findString: 'content=') + 9 to: text size. > doubleQuoteIndex := 8 - ((str last: 7) indexOf: $"). > ^ str copyFrom: 1 to: str size - doubleQuoteIndex > > > I can't figure out how to change the startParser parser to accept the second idiom. And maybe there's a better approach altogether. Anyway. If anyone has any ideas on different approaches I'd appreciate learning them. > > > Thanks for giving it some thought > > Paul >

April 2, 2017