- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] spotter preview

by Marcus Denker

> On 02 Feb 2015, at 22:02, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > The Glamorous Team is happy to present a new feature in Spotter: preview (you toggle it with Cmd+p). We think this boosts the usefulness of the Spotter interface significantly. > > <spotter-method-preview.png> > > For more details, please take a look at: > http://www.humane-assessment.com/blog/boosting-gtspotter-with-preview <http://www.humane-assessment.com/blog/boosting-gtspotter-with-preview> > > This is available in the Moose image, and it will soon be integrated in the Pharo one. > This is now in Pharo4 update 473 (the latest one from today). Marcus

Feb. 3, 2015

Re: [Pharo-dev] Slides from the Pharo Status talk at FOSDEM 2015

by Marcus Denker

> On 02 Feb 2015, at 21:19, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > Here are the slides from my talk from yesterday: > > http://www.slideshare.net/MarcusDenker/2015-fosdempharo > The part in between Pharo3 and Pharo4 tries a bit to explain the philosophyâ¦ I did a longer talk at ESUG last year about that: Nomads do not build Cathedrals http://www.slideshare.net/MarcusDenker/2014-esugcathedral The video of that is online: Video Part 1: https://www.youtube.com/watch?v=Vcoy5gwUvOA Video Part 2: https://www.youtube.com/watch?v=5LrH9r4FNzY In the spirit of the talk, I should do a pass over it and make a version 2â¦ e.g. one book that was very influential to my thinking was Finite and Infinite Games by James P. Carse: http://kk.org/cooltools/archives/000434 To me a software system should always be thought as an âinfinite gameââ¦ Marcus

Feb. 3, 2015

Re: [Pharo-dev] ||

by Yuriy Tymchuk

Yes, Iâve reported that already and it was fixed in Pharo 4 Uko > On 03 Feb 2015, at 09:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 02 Feb 2015, at 21:47, Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: >> >> Hi All, >> >> code as in the double bars forming the end of block arguments and the beginning of block temporaries in >> > > This is fixed in Pharo4 (I think we did that in Pharo3 already): > > > <Untitled.png> > > In general, I really am convinced that we should continue to reduce the number of Smalltalk parsers > in the system. Imagine there would be only *one*, then bugs like this would never happen, we would > have less code to maintain and every improvement would benefit directly all subsystems that use > the Parser or the AST. > > We already did that for the tools (RB) and the Compiler. We use the handwritten RBParser for now > (I would like to use PetitParserâ¦). > The next would be to replace the Shout Parser+Tokenstreamâ¦ we already in all tools create an AST > as soon as you select a method anyway. (the is for per-AST-Node Navigation + the âsuggestionsâ menu). > > RBParser already has #parseFaultyMethod:, this means it can generate an AST even for incomplete input > (with an error node). e.g. you can parse the expression â1+â: > > <Untitled.png> > > There is already a SHRBTextStyler which uses it, we should finish that and replace the Shout parser. > > Marcus > >

Feb. 3, 2015

Re: [Pharo-dev] [Pharo-users] Slides from the Pharo Status talk at FOSDEM 2015

by Marcus Denker

> On 02 Feb 2015, at 21:26, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > On Mon, Feb 2, 2015 at 12:19 PM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > Hi, > > Here are the slides from my talk from yesterday: > > http://www.slideshare.net/MarcusDenker/2015-fosdempharo <http://www.slideshare.net/MarcusDenker/2015-fosdempharo> > > very cool, Marcus! will there be audio of the Q&A? Do you have any recollections of the Q&A? > It was recordedâ¦ the Q&A after was not that many questionsâ¦ I donât actually remember. I think the impact is more the slides+video, not the presentation itself there. Marcus

Feb. 3, 2015

Re: [Pharo-dev] ||

by Marcus Denker

> On 02 Feb 2015, at 21:47, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi All, > > code as in the double bars forming the end of block arguments and the beginning of block temporaries in > This is fixed in Pharo4 (I think we did that in Pharo3 already): In general, I really am convinced that we should continue to reduce the number of Smalltalk parsers in the system. Imagine there would be only *one*, then bugs like this would never happen, we would have less code to maintain and every improvement would benefit directly all subsystems that use the Parser or the AST. We already did that for the tools (RB) and the Compiler. We use the handwritten RBParser for now (I would like to use PetitParserâ¦). The next would be to replace the Shout Parser+Tokenstreamâ¦ we already in all tools create an AST as soon as you select a method anyway. (the is for per-AST-Node Navigation + the âsuggestionsâ menu). RBParser already has #parseFaultyMethod:, this means it can generate an AST even for incomplete input (with an error node). e.g. you can parse the expression â1+â: There is already a SHRBTextStyler which uses it, we should finish that and replace the Shout parser. Marcus

Feb. 3, 2015

Re: [Pharo-dev] [squeak-dev] ||

by David T. Lewis

On Mon, Feb 02, 2015 at 12:47:45PM -0800, Eliot Miranda wrote: > Hi All, > > code as in the double bars forming the end of block arguments and the > beginning of block temporaries in > > convertInstances > | new old | > old := Binding allInstances. > new := old collect: [:ea | ClassBinding key: ea key value: ea value]. > old elementsForwardIdentityTo: new. > old := ReadOnlyVariableBinding allInstances. > new := old collect: [:ea | ClassBinding key: ea key value: ea value]. > old elementsForwardIdentityTo: new. > Environment allInstancesDo: > [:env | > #('contents' 'bindings' 'public' 'undeclared') do: > => [:var || dict | > old := Array new writeStream. > new := Array new writeStream. > dict := env instVarNamed: var. > dict associations do: > [:binding | > binding class == Association ifTrue: > [old nextPut: binding. > new nextPut: binding key => binding value]]. > old contents elementsForwardIdentityTo: new contents]] > > is legal but highlighted as a syntax error by shout. > > What do you prefer, editing the source to | | or fixing Shout to accept the > syntax? The right answer should be fixing shout but the fix will be ugly > because || is a binary selector and so this will need to be special cased. If anything needs to be fixed, I would vote for fixing Shout. The syntax is legal, and to me it intuitively looks like it *should* be legal. On the other hand, adding some whitespace between the vertical bars is a good idea for readability, even if it is not a necessary part of the syntax. So it does not bother me if Shout complains about the missing whitespace. But I have to admit that it is confusing if Shout displays an apparent syntax error when in fact nothing is wrong with the syntax. Dave

Feb. 3, 2015

spotter preview

by Tudor Girba

Hi, The Glamorous Team is happy to present a new feature in Spotter: preview (you toggle it with Cmd+p). We think this boosts the usefulness of the Spotter interface significantly. [image: Inline image 1] For more details, please take a look at: http://www.humane-assessment.com/blog/boosting-gtspotter-with-preview This is available in the Moose image, and it will soon be integrated in the Pharo one. Please let us know what you think. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Feb. 2, 2015

||

by Eliot Miranda

Hi All, code as in the double bars forming the end of block arguments and the beginning of block temporaries in convertInstances | new old | old := Binding allInstances. new := old collect: [:ea | ClassBinding key: ea key value: ea value]. old elementsForwardIdentityTo: new. old := ReadOnlyVariableBinding allInstances. new := old collect: [:ea | ClassBinding key: ea key value: ea value]. old elementsForwardIdentityTo: new. Environment allInstancesDo: [:env | #('contents' 'bindings' 'public' 'undeclared') do: => [:var || dict | old := Array new writeStream. new := Array new writeStream. dict := env instVarNamed: var. dict associations do: [:binding | binding class == Association ifTrue: [old nextPut: binding. new nextPut: binding key => binding value]]. old contents elementsForwardIdentityTo: new contents]] is legal but highlighted as a syntax error by shout. What do you prefer, editing the source to | | or fixing Shout to accept the syntax? The right answer should be fixing shout but the fix will be ugly because || is a binary selector and so this will need to be special cased. -- best, Eliot

Feb. 2, 2015

Re: [Pharo-dev] Slides from the Pharo Status talk at FOSDEM 2015

by Eliot Miranda

On Mon, Feb 2, 2015 at 12:19 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Here are the slides from my talk from yesterday: > > http://www.slideshare.net/MarcusDenker/2015-fosdempharo > very cool, Marcus! will there be audio of the Q&A? Do you have any recollections of the Q&A? -- best, Eliot

Feb. 2, 2015

Slides from the Pharo Status talk at FOSDEM 2015

by Marcus Denker

Hi, Here are the slides from my talk from yesterday: http://www.slideshare.net/MarcusDenker/2015-fosdempharo <http://www.slideshare.net/MarcusDenker/2015-fosdempharo> Marcus

Feb. 2, 2015