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

Re: [Pharo-users] #parseMethod:onError: isn't as obvious as expected - is it me?

by Marcus Denker

> On 31 Aug 2017, at 19:07, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > On Wed, Aug 30, 2017 at 9:50 PM, Tim Mackinnon <tim(a)testit.works> wrote: >> Iâm looking for some feedback on the usage of RBParser>>#parseMethod:onError:. >> >> I am looking at ways of improving the way we edit code - and making things work (as least for me - but maybe for everyone) a bit more like IntelliJ where they have some great code operations and very good keyboard support. We are certainly close, but at times feel a bit clumsy - which is a shame as we have far better infrastructure to support equivalent features. So I thought I would have a go. > > Excellent!!! > > >> Anyway - step one (which I think Iâve come close on), was to teach senders/implementors to look at the AST so you donât have to highlight exactly what you want to search on - instead it can infer from your cursorâ¦ however my next step was to improve how we can select code to ease refactoring, bracketing etcâ¦ > > Yes but we have to handle broken code then. > Did you check how smart suggestions did it for code that compiled? > I looked some weeks ago and made some notes what to doâ¦ but I fear this has to wait for next week, there is no way that I can do anything till ESUGâ¦ Marcus

Aug. 31, 2017

Re: [Pharo-users] #parseMethod:onError: isn't as obvious as expected - is it me?

by Stephane Ducasse

On Wed, Aug 30, 2017 at 9:50 PM, Tim Mackinnon <tim(a)testit.works> wrote: > Iâm looking for some feedback on the usage of RBParser>>#parseMethod:onError:. > > I am looking at ways of improving the way we edit code - and making things work (as least for me - but maybe for everyone) a bit more like IntelliJ where they have some great code operations and very good keyboard support. We are certainly close, but at times feel a bit clumsy - which is a shame as we have far better infrastructure to support equivalent features. So I thought I would have a go. Excellent!!! > Anyway - step one (which I think Iâve come close on), was to teach senders/implementors to look at the AST so you donât have to highlight exactly what you want to search on - instead it can infer from your cursorâ¦ however my next step was to improve how we can select code to ease refactoring, bracketing etcâ¦ Yes but we have to handle broken code then. Did you check how smart suggestions did it for code that compiled? > > So this is where Iâve hit a few issues which strike me as confusing (and I will freely admit that Iâm not a mega compiler, parser guy - but Iâd love to beâ¦). > > The following code blows up strangely - and I think its very confusingâ¦ as it turns out that #parseMethod:onError: doesnât work like I would expect (and this is where Iâm after feedback). It seems that the onError block doesât actually exit parsing - it takes the result and then keeps running with something in an intermediate state - thus below, when I try to parse with a subset of the code (and maybe this is a naive approach to handle the case when you start typing code in the middle of a complete method, but want to parse it before youâve entered a final â.â or â;â) - you actually end up with an AST that is using all of the source code because the result of the error block is then applied inside the executing method. > > I find this very confusing? There are no comments in this code, and for me the convention of onError: is to execute in isolation unless there is a parameter that the error block can interact with. Iâm wondering if those with more knowledge agree - or if it is my naivetÃ©? > > This was my original code (and yes it needs refactoring a bit) - but anyway: > > bestNodeInTextAreaOnError: aBlock > "Find the best node in the editor text area at the current pointer location" > > | ast start stop node source | > > start := self textArea startIndex. > stop := self textArea stopIndex. > > source := self textArea string trimRight. > > ast := RBParser parseMethod: source onError: [ > RBParser parseExpression: source onError: [ > source := (source truncateTo: stop) trimRight. > > RBParser parseMethod: source onError: [ > RBParser parseExpression: source onError: aBlock ]]]. > > stop > source size ifTrue: [ > start := stop := source size]. > > node := ast bestNodeFor: (start to: stop). > > node ifNil: aBlock. > > ^node > > But this doesnât work, as âastâ is incorrect when it parses truncated source. To work around what Iâm seeing I have to instead extract the ast assignment to another method that looks as follows - but to me it seems very unexpected to have the explicit ^ statements? > > agressivelyParse: source at: loc > "Find the best node in the editor text area at the current pointer location" > > ^RBParser parseMethod: source onError: [ > ^RBParser parseExpression: source onError: [ | reducedSrc | > reducedSrc := (source truncateTo: loc) trimRight. > > ^RBParser parseMethod: reducedSrc onError: [ > ^RBParser parseExpression: reducedSrc onError: [^nil]]]]. > > This forces the ast to be exactly what I would expect - but Iâm wondering if I am missing something obvious? > > Tim

Aug. 31, 2017

Re: [Pharo-users] [Pillar] Pillar source code of ESUG 2015 presentation? Presentations done with Pillar?

by H. Hirzel

Thank you, Stef https://github.com/SquareBracketAssociates/PharoMooc/tree/master/support/be… On 8/31/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hannes > > the beamer templates manage the first page. > Have a look in the support/ folder. > > Stef > > On Thu, Aug 31, 2017 at 4:12 PM, Cyril Ferlicot > <cyril.ferlicot(a)gmail.com> wrote: >> There is some doc in the section 3.12 of the documentation >> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> >> I don't know if everything is here but there is some doc at least :) >> >> On Thu, Aug 31, 2017 at 4:08 PM, H. Hirzel <hannes.hirzel(a)gmail.com> >> wrote: >>> On 8/31/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>> A useful file which shows what is possible to do slides >>>> >>>> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >>> >>> Correction: >>> This file shows how to do slides with Pillar >>> >>> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >>> >>> My questions thus are specifically: >>> >>> 1. How do I do a title slide? >>> 2. What do I do inside the ${....}$ . >>> Where do I find documentation on the options for these $ enclosed >>> commands? >>> >>> --Hannes >>> >> >> >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr >> >> http://www.synectique.eu >> 2 rue Jacques PrÃ©vert 01, >> 59650 Villeneuve d'ascq France >> > >

Aug. 31, 2017

Re: [Pharo-users] new chapter on double dispatch for new book :)

by Stephane Ducasse

Yes I like this book. Now what I suggest is to try on a separate class hierarchy because breaking + can blow up your image. On Tue, Aug 29, 2017 at 10:28 PM, Yves Lenfant <lenfantyv(a)wanadoo.fr> wrote: > Thanks for your quick reply. > OK, your chapter highligths the polymorpism not the inheritance. > > So I will try to change the Number methods in a dedicated image... > > Anyway, in the book InsideSmalltalk P. 250, it explains that (I quote) > > I suppose the "Number" mecanism is more complex than I can expect. > > Yves > > > > -- > View this message in context: http://forum.world.st/new-chapter-on-double-dispatch-for-new-book-tp4963645… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 31, 2017

Re: [Pharo-users] [Pillar] Pillar source code of ESUG 2015 presentation? Presentations done with Pillar?

by Stephane Ducasse

Hannes the beamer templates manage the first page. Have a look in the support/ folder. Stef On Thu, Aug 31, 2017 at 4:12 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > There is some doc in the section 3.12 of the documentation > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > I don't know if everything is here but there is some doc at least :) > > On Thu, Aug 31, 2017 at 4:08 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> On 8/31/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> A useful file which shows what is possible to do slides >>> >>> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >> >> Correction: >> This file shows how to do slides with Pillar >> >> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >> >> My questions thus are specifically: >> >> 1. How do I do a title slide? >> 2. What do I do inside the ${....}$ . >> Where do I find documentation on the options for these $ enclosed commands? >> >> --Hannes >> > > > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Aug. 31, 2017

Re: [Pharo-users] sharing context/variables between multiple playgrounds

by Marcus Denker

> On 31 Aug 2017, at 17:46, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Pavel Krivanek-3 wrote >> In that cases I simply make them global. > > It seems that a variable defined with a capitalized name in an inspector is > still local. How do you make it global? Something like: `Smalltalk globals > at: #MyVar put: expression`? > Yes, there was a discussion about fixing the inspectorâ¦ I have a fixâ¦ but not yet the time to integrate it: https://pharo.fogbugz.com/f/cases/20254/Playground-should-ask-to-create-cla… Marcus

Aug. 31, 2017

Re: [Pharo-users] sharing context/variables between multiple playgrounds

by Sean P. DeNigris

Pavel Krivanek-3 wrote > In that cases I simply make them global. It seems that a variable defined with a capitalized name in an inspector is still local. How do you make it global? Something like: `Smalltalk globals at: #MyVar put: expression`? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 31, 2017

Re: [Pharo-users] The Spec UI Framework. first translation to korean finish.

by Damien Pollet

Hi Peter, On 31 August 2017 at 16:04, peter yoo <onionmixer(a)gmail.com> wrote: > > Spec git file location have "korean charactor" then book compile fail. > Yeahâ¦ non-ascii characters and spaces in file names often cause problemsâ¦ However in this case, it might be due to differences between various encodings: - what your system is using for file names - what you wrote into pillar.conf (is it UTF-8 or some korean-specific encoding?) - what pillar reads pillar.conf as (that should be UTF-8 and nothing else, in my opinion) - how Pharo converts strings to filenames (I doubt there is any conversion there, as different platforms accept and support different encodings) > 2. TeX base > ok.. can look this. > https://github.com/cdlm/sbabook > > i know polygrossia. but not use before. i can try some TeX then report > later. > I just managed to write korean characters in an sbabook document (see below, this compiles with lualatex). Unfortunately the documentation for kotex and oblivoir are all in korean so I didnt' get much out of them. It looks like simply loading kotex and picking fonts with enough international coverage is enough, though. Polyglossia has an option for korean but it conflicts with something else; maybe this is explained in the oblivoir documentation ? \documentclass{sbabook} \usepackage[cjk,hangul]{kotex} \usepackage{noto} \usepackage{polyglossia} \setmainlanguage{english} \begin{document} \section{Latin alphabet} Hello world. Äu vi parolas la esperanton? \section{CJK} (Chinese) ä½ å¥½, æ©æ¨, (Japanese) ããã«ã¡ã¯, (Korean, hangul) ìëíì¸ì. \end{document}

Aug. 31, 2017

Re: [Pharo-users] [Pillar] Pillar source code of ESUG 2015 presentation? Presentations done with Pillar?

by Cyril Ferlicot

There is some doc in the section 3.12 of the documentation https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… I don't know if everything is here but there is some doc at least :) On Thu, Aug 31, 2017 at 4:08 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > On 8/31/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> A useful file which shows what is possible to do slides >> >> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… > > Correction: > This file shows how to do slides with Pillar > > https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… > > My questions thus are specifically: > > 1. How do I do a title slide? > 2. What do I do inside the ${....}$ . > Where do I find documentation on the options for these $ enclosed commands? > > --Hannes > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Aug. 31, 2017

Re: [Pharo-users] [Pillar] Pillar source code of ESUG 2015 presentation? Presentations done with Pillar?

by H. Hirzel

On 8/31/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > A useful file which shows what is possible to do slides > > https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… Correction: This file shows how to do slides with Pillar https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… My questions thus are specifically: 1. How do I do a title slide? 2. What do I do inside the ${....}$ . Where do I find documentation on the options for these $ enclosed commands? --Hannes

Aug. 31, 2017