- Pharo-dev - lists.pharo.org

is it me or we cannot use shortcut in debugger inspector?

by stepharo

Hi I authorised myself a littel coding session today and is it me or we cannot use shortcut in debugger inspector? stef

Nov. 29, 2015

Re: [Pharo-dev] learning from errors....

by stepharo

Hi henrik indeed and no need 4 classes 3 singletons and a garbage collector stresser. Stef Le 25/11/15 00:34, Henrik Nergaard a Ã©crit : > > You could use one of those images and rotate it when drawing, changing > the angle by #step. > > I attached an example. > > Best regards, > > Henrik > > *From:*Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *On Behalf > Of *Yuriy Tymchuk > *Sent:* Tuesday, November 24, 2015 7:58 PM > *To:* Pharo Development List <pharo-dev(a)lists.pharo.org> > *Subject:* Re: [Pharo-dev] learning from errors.... > > Good catch. > > At the time when I was developing it, the loading morph implementation > was such a magic for me, that I was super happy after finishing it and > forgot that I depend on Komitter. > > Is there any alternative for that? Otherwise I will simply remove the > spinning cog, I donât feel that this is super important. > > Uko > > On 24 Nov 2015, at 19:51, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > BTW: it would be good that QA does not refer to Komitter. And > package it as a separate project. > QA should not dependent on Komitter because we can remove > Komitter. And it makes no sense! >

Nov. 29, 2015

Re: [Pharo-dev] Autoscrolling (in FastTable)

by Thierry Goubier

Le 29/11/2015 19:04, stepharo a Ã©crit : > > > Le 28/11/15 18:32, Thierry Goubier a Ã©crit : >> Le 28/11/2015 18:24, stepharo a Ã©crit : >>> We are working on Bloc so I would not invest too much improving >>> dramatically Morphic. >> >> Most of what is being done will port to Bloc. No improvements of >> Morphic are considered; just using it correctly. > > then supercool :) Very interesting. We're now talking easy-in-out animations for scrolling, like in the Self paper of 1993 (and as in CSS these days). Thierry

Nov. 29, 2015

Re: [Pharo-dev] Autoscrolling (in FastTable)

by stepharo

Le 28/11/15 18:32, Thierry Goubier a Ã©crit : > Le 28/11/2015 18:24, stepharo a Ã©crit : >> We are working on Bloc so I would not invest too much improving >> dramatically Morphic. > > Most of what is being done will port to Bloc. No improvements of > Morphic are considered; just using it correctly. then supercool :) > > Thierry > >

Nov. 29, 2015

Re: [Pharo-dev] [Pharo5] Semantic Warnings as icons in the editor

by Nicolas Cellier

Oh, the rate of false positive is so low in this case, less than 1 out of 1000 I guess... Here is a super twisty workaround (I don't really recommend it, but for the fun) A := [:a | ... a value: a]. self doSomethingLike: [A value: A]. 2015-11-29 16:37 GMT+01:00 Johan Fabry <jfabry(a)dcc.uchile.cl>: > > > On Nov 29, 2015, at 10:21, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > > > Le 29/11/2015 14:14, Nicolas Cellier a Ã©crit : > >> It's nice, but I like the Compiler to be pedantic in such cases and > >> manifest itself BEFORE accepting the method. > >> One thing is suspicious patterns, another is obviously wrong code. Can't > >> we have graduated responses? > > > > The problem is that certain semantic warnings were false positives, as > the recursive block definition. > > > > A := [ ... A value ]. > > Indeed, this warning happens to me from time to time (I tend to use blocks > as lambdas in some cases) and it is *extremely* annoying to have to close > the warning window every time. I think I will address that tomorrow â¦ > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University > of Chile > > >

Nov. 29, 2015

Re: [Pharo-dev] [Pharo5] Semantic Warnings as icons in the editor

by Johan Fabry

> On Nov 29, 2015, at 10:21, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 29/11/2015 14:14, Nicolas Cellier a Ã©crit : >> It's nice, but I like the Compiler to be pedantic in such cases and >> manifest itself BEFORE accepting the method. >> One thing is suspicious patterns, another is obviously wrong code. Can't >> we have graduated responses? > > The problem is that certain semantic warnings were false positives, as the recursive block definition. > > A := [ ... A value ]. Indeed, this warning happens to me from time to time (I tend to use blocks as lambdas in some cases) and it is *extremely* annoying to have to close the warning window every time. I think I will address that tomorrow â¦ ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Nov. 29, 2015

Re: [Pharo-dev] [Pharo5] Semantic Warnings as icons in the editor

by Thierry Goubier

Le 29/11/2015 14:14, Nicolas Cellier a Ã©crit : > It's nice, but I like the Compiler to be pedantic in such cases and > manifest itself BEFORE accepting the method. > One thing is suspicious patterns, another is obviously wrong code. Can't > we have graduated responses? The problem is that certain semantic warnings were false positives, as the recursive block definition. A := [ ... A value ]. Thierry > > 2015-11-29 0:52 GMT+01:00 Johan Fabry <jfabry(a)dcc.uchile.cl > <mailto:jfabry@dcc.uchile.cl>>: > > > And now the question for the monday morning development effort is: > what more semantic warnings of the compiler can we reveal like this? :-) > >> On Nov 28, 2015, at 19:06, Cyril Ferlicot >> <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote: >> >> This is really cool ! :) >> One more step to get a nice IDE! >> Thank you for your efforts :) >> >> On Saturday, November 28, 2015, Marcus Denker >> <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> Hi, >> >> One result of Fridayâs Pharo Sprint in Chile: Use the nice >> icons of the new text editor >> to display some of the semantic errors nicely (instead of >> breaking flow with a intrusive dialog): >> >> This was done by Johan based on the prototype Miguel did in >> September: >> >> 1) unused temps: >> >> <unused.png> >> >> (the âdrag the crosshairâr is an artefact of the snapshot tool) >> >> 2) temps used that are not initialised: >> >> <uninit.png> >> >> >> In a next step, we need to integrate that with the QA toolâ¦ no >> need to have this reported >> twice. >> >> What is nice is that this simplified the Compiler: instead of >> having an Exception and raising >> it, we now just annotate the AST: >> >> unusedVariable: variableNode >> >> variableNode propertyAt: #semanticWarning put: 'unused variableâ >> >> (this is very simple for now, with a node just being able to >> have one kind of semanticWarning). >> >> SemanticWarningIconStyler is what adds the icon. It has 4 >> methods with one line each. >> >> Marcus >> >> >> >> -- >> Cheers >> Cyril Ferlicot >> > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - > University of Chile > >

Nov. 29, 2015

Re: [Pharo-dev] [Pharo5] Semantic Warnings as icons in the editor

by Nicolas Cellier

It's nice, but I like the Compiler to be pedantic in such cases and manifest itself BEFORE accepting the method. One thing is suspicious patterns, another is obviously wrong code. Can't we have graduated responses? 2015-11-29 0:52 GMT+01:00 Johan Fabry <jfabry(a)dcc.uchile.cl>: > > And now the question for the monday morning development effort is: what > more semantic warnings of the compiler can we reveal like this? :-) > > On Nov 28, 2015, at 19:06, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> > wrote: > > This is really cool ! :) > One more step to get a nice IDE! > Thank you for your efforts :) > > On Saturday, November 28, 2015, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> Hi, >> >> One result of Fridayâs Pharo Sprint in Chile: Use the nice icons of the >> new text editor >> to display some of the semantic errors nicely (instead of breaking flow >> with a intrusive dialog): >> >> This was done by Johan based on the prototype Miguel did in September: >> >> 1) unused temps: >> >> <unused.png> >> >> (the âdrag the crosshairâr is an artefact of the snapshot tool) >> >> 2) temps used that are not initialised: >> >> <uninit.png> >> >> >> In a next step, we need to integrate that with the QA toolâ¦ no need to >> have this reported >> twice. >> >> What is nice is that this simplified the Compiler: instead of having an >> Exception and raising >> it, we now just annotate the AST: >> >> unusedVariable: variableNode >> >> variableNode propertyAt: #semanticWarning put: 'unused variableâ >> >> (this is very simple for now, with a node just being able to have one >> kind of semanticWarning). >> >> SemanticWarningIconStyler is what adds the icon. It has 4 methods with >> one line each. >> >> Marcus >> >> > > -- > Cheers > Cyril Ferlicot > > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University > of Chile > >

Nov. 29, 2015

Re: [Pharo-dev] [Pharo5] Semantic Warnings as icons in the editor

by Johan Fabry

And now the question for the monday morning development effort is: what more semantic warnings of the compiler can we reveal like this? :-) > On Nov 28, 2015, at 19:06, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > This is really cool ! :) > One more step to get a nice IDE! > Thank you for your efforts :) > > On Saturday, November 28, 2015, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > Hi, > > One result of Fridayâs Pharo Sprint in Chile: Use the nice icons of the new text editor > to display some of the semantic errors nicely (instead of breaking flow with a intrusive dialog): > > This was done by Johan based on the prototype Miguel did in September: > > 1) unused temps: > > <unused.png> > > (the âdrag the crosshairâr is an artefact of the snapshot tool) > > 2) temps used that are not initialised: > > <uninit.png> > > > In a next step, we need to integrate that with the QA toolâ¦ no need to have this reported > twice. > > What is nice is that this simplified the Compiler: instead of having an Exception and raising > it, we now just annotate the AST: > > unusedVariable: variableNode > > variableNode propertyAt: #semanticWarning put: 'unused variableâ > > (this is very simple for now, with a node just being able to have one kind of semanticWarning). > > SemanticWarningIconStyler is what adds the icon. It has 4 methods with one line each. > > Marcus > > > > -- > Cheers > Cyril Ferlicot > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Nov. 28, 2015

Re: [Pharo-dev] [Pharo5] Semantic Warnings as icons in the editor

by Cyril Ferlicot

This is really cool ! :) One more step to get a nice IDE! Thank you for your efforts :) On Saturday, November 28, 2015, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > One result of Fridayâs Pharo Sprint in Chile: Use the nice icons of the > new text editor > to display some of the semantic errors nicely (instead of breaking flow > with a intrusive dialog): > > This was done by Johan based on the prototype Miguel did in September: > > 1) unused temps: > > > (the âdrag the crosshairâr is an artefact of the snapshot tool) > > 2) temps used that are not initialised: > > > > In a next step, we need to integrate that with the QA toolâ¦ no need to > have this reported > twice. > > What is nice is that this simplified the Compiler: instead of having an > Exception and raising > it, we now just annotate the AST: > > unusedVariable: variableNode > > variableNode propertyAt: #semanticWarning put: 'unused variableâ > > (this is very simple for now, with a node just being able to have one kind > of semanticWarning). > > SemanticWarningIconStyler is what adds the icon. It has 4 methods with one > line each. > > Marcus > > -- Cheers Cyril Ferlicot

Nov. 28, 2015