- Pharo-users - lists.pharo.org

Re: [Pharo-users] [Moose-dev] feenk log

by Ben Coman

On Fri, 17 Aug 2018 at 12:48, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > We again got carried away and forgot to update the world about what is up in our corner. Here is a summary: Thanks for the update. Nice to see the progress. > > -- > Bloc & Brick > -- > > - Text editor stability has been significantly improved > - Improved support for selection in the text editor > - Support for typical editing keybindings (copy, cut, paste) > - Text editor debuggability: > https://twitter.com/feenkcom/status/1024680215379959808 > https://twitter.com/feenkcom/status/1020768298017992704 Nice demos. If possible, it would be interesting to see movement or a selection in the first video, dynamically updating a treeview in a second-Inspector-pane. cheers -ben

Aug. 17, 2018

Re: [Pharo-users] Making TDD in pharo work properly (aka - walkback on a missing class is nasty)

by Tim Mackinnon

The direct link to instructions is here: https://exercism.io/tracks/pharo/installation <https://exercism.io/tracks/pharo/installation> (not sure if you have to be signed up to see it otherwise its in the repo here: https://github.com/exercism/pharo/blob/master/docs/INSTALLATION.md <https://github.com/exercism/pharo/blob/master/docs/INSTALLATION.md>) Tim > On 17 Aug 2018, at 07:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 17 Aug 2018, at 13:00, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> >> Hi Marcus - I can put an image somewhere if that helps (do you just need the .image and .changes)? >> >> Or you can repro from a fresh 6.1 if you follow the exercism Pharo instructions (https://exercism.io/tracks/pharo <https://exercism.io/tracks/pharo>) to load the first hello world-world example and run the tests. This has my code changes to make create work with a nil class - but maybe we can do better? >> > I will do that and have a look! > >> Tim >> >> >> Sent from my iPhone >> >> On 17 Aug 2018, at 06:21, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >>> >>> >>>> On 10 Aug 2018, at 23:16, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>>> >>>> Actually I think I figured that bit out - a bit clumsily - (pointers appreciated) >>>> >>>> createMissingClassActionFor: aMessage in: aContext >>>> |errorNode senderContext newClass variableNode | >>>> senderContext := aContext sender. >>>> errorNode := senderContext method sourceNodeExecutedForPC: senderContext pc. >>>> variableNode := errorNode receiver receiver. >>>> >>>> newClass := OCUndeclaredVariableWarning new node: variableNode; defineClass: variableNode name. >>>> aContext restart. >>>> >>>> However that last line is wrong, as it doesnât restart with my newly defined class - I also tried >>>> >>>> aContext restartWithNewReceiver: newClass >>>> >>>> But again, I get a debugger where my class is still bound to nil. So whatâs the trick to re-evaluate with the new class Iâve created? Or maybe Iâm totally on the wrong track (still its very interestingâ¦) >>>> >>> >>> >>> what is a bit bad is that you catch the problem âtoo lateâ (that is, the DNU to nil, not the read of nil), so nil is already pushed on the stack at this point. >>> >>> I tried it in the inspector and at least the class binding was correct after defining the classâ¦ do you have an image with the whole code to try? >>> >>> Marcus >>> >>> >

Aug. 17, 2018

Re: [Pharo-users] Trait method override

by tesonep＠gmail.com

Jajajja, yes I like the power that there is in the language. It opens a lot of doors and possibilities. You can check the implementation of deep alias that rewrites the users of the aliased method. There is also the ability to implement new operations to traits algebra. You can check how they are implemented and implement new operations. Cheers On Fri, Aug 17, 2018 at 1:23 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > Hello Pablo, > > Don't think it is ugly, I personally think it is wonderfull how those > extensions to the language can be done with normal messaging passing code! > But the information about this seems scattered a bit, I found in google and > was not certain if the information was official or correct. > > Also, there could be some default aliases in hand, in a way similar to > groovy: > http://docs.groovy-lang.org/latest/html/documentation/#_user_conflict_resol… > > So, if I use TraitA with a methodX, this method could be aliased by > default with something like TraitA_methodX. Don't know if this have some > problem, just an idea (maybe I will explore this here :) ) > > regards, > Vitor > > On Fri, Aug 17, 2018 at 4:37 AM, tesonep(a)gmail.com <tesonep(a)gmail.com> > wrote: > >> Hi Vitor, >> as Julien correctly said there is no super call in traits. Currently >> the solution, maybe is a bit ugly, it is to use aliasing. >> Cheers, >> Pablo >> >> On Fri, Aug 17, 2018 at 12:10 AM Vitor Medina Cruz <vitormcruz(a)gmail.com> >> wrote: >> >>> Thanks Julian! >>> >>> On Thu, Aug 16, 2018 at 5:38 PM, Julien <julien.delplanque(a)inria.fr> >>> wrote: >>> >>>> Hello Vitor, >>>> >>>> Yeah, I was talking about that with Pablo (who implemented stateful >>>> traits) some times ago. >>>> >>>> He told me that aliasing was he way to go. >>>> >>>> There is no other option to override a trait method without aliasing it. >>>> >>>> Cheers, >>>> >>>> Julien >>>> >>>> --- >>>> Julien Delplanque >>>> Doctorant Ã lâUniversitÃ© de Lille >>>> http://juliendelplanque.be/phd.html >>>> Equipe Rmod, Inria >>>> BÃ¢timent B 40, Avenue Halley 59650 >>>> <https://maps.google.com/?q=40,+Avenue+Halley+59650+Villeneuve+d'Ascq&entry=gmail&source=g> >>>> Villeneuve >>>> <https://maps.google.com/?q=40,+Avenue+Halley+59650+Villeneuve+d'Ascq&entry=gmail&source=g> >>>> d'Ascq >>>> <https://maps.google.com/?q=40,+Avenue+Halley+59650+Villeneuve+d'Ascq&entry=gmail&source=g> >>>> NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 >>>> >>>> Le 16 aoÃ»t 2018 Ã 19:32, Vitor Medina Cruz <vitormcruz(a)gmail.com> a >>>> Ã©crit : >>>> >>>> Well, found out about aliasing in >>>> http://pharo.gemtalksystems.com/book/LanguageAndLibraries/Traits/, is >>>> that the correct way of doint it? >>>> >>>> On Thu, Aug 16, 2018 at 11:30 AM, Vitor Medina Cruz < >>>> vitormcruz(a)gmail.com> wrote: >>>> >>>>> Hello, >>>>> >>>>> In a class that uses a Trait, how can I override one of it's method by >>>>> appending behavior to the method implemented by the Trait? In a typical >>>>> override, this is done by calling super: >>>>> >>>>> method >>>>> >>>>> super method >>>>> "extended behavior" >>>>> ... >>>>> >>>>> >>>>> Is there a way to change "super" to a reference the Trait? >>>>> >>>>> Regards, >>>>> Vitor >>>>> >>>> >>>> >>>> >>> >> >> -- >> Pablo Tesone. >> tesonep(a)gmail.com >> > > -- Pablo Tesone. tesonep(a)gmail.com

Aug. 17, 2018

Re: [Pharo-users] Trait method override

by Vitor Medina Cruz

Hello Pablo, Don't think it is ugly, I personally think it is wonderfull how those extensions to the language can be done with normal messaging passing code! But the information about this seems scattered a bit, I found in google and was not certain if the information was official or correct. Also, there could be some default aliases in hand, in a way similar to groovy: http://docs.groovy-lang.org/latest/html/documentation/#_user_conflict_resol… So, if I use TraitA with a methodX, this method could be aliased by default with something like TraitA_methodX. Don't know if this have some problem, just an idea (maybe I will explore this here :) ) regards, Vitor On Fri, Aug 17, 2018 at 4:37 AM, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > Hi Vitor, > as Julien correctly said there is no super call in traits. Currently > the solution, maybe is a bit ugly, it is to use aliasing. > Cheers, > Pablo > > On Fri, Aug 17, 2018 at 12:10 AM Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: > >> Thanks Julian! >> >> On Thu, Aug 16, 2018 at 5:38 PM, Julien <julien.delplanque(a)inria.fr> >> wrote: >> >>> Hello Vitor, >>> >>> Yeah, I was talking about that with Pablo (who implemented stateful >>> traits) some times ago. >>> >>> He told me that aliasing was he way to go. >>> >>> There is no other option to override a trait method without aliasing it. >>> >>> Cheers, >>> >>> Julien >>> >>> --- >>> Julien Delplanque >>> Doctorant Ã lâUniversitÃ© de Lille >>> http://juliendelplanque.be/phd.html >>> Equipe Rmod, Inria >>> BÃ¢timent B 40, Avenue Halley 59650 >>> <https://maps.google.com/?q=40,+Avenue+Halley+59650+Villeneuve+d'Ascq&entry=gmail&source=g> >>> Villeneuve >>> <https://maps.google.com/?q=40,+Avenue+Halley+59650+Villeneuve+d'Ascq&entry=gmail&source=g> >>> d'Ascq >>> <https://maps.google.com/?q=40,+Avenue+Halley+59650+Villeneuve+d'Ascq&entry=gmail&source=g> >>> NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 >>> >>> Le 16 aoÃ»t 2018 Ã 19:32, Vitor Medina Cruz <vitormcruz(a)gmail.com> a >>> Ã©crit : >>> >>> Well, found out about aliasing in http://pharo.gemtalksystems. >>> com/book/LanguageAndLibraries/Traits/, is that the correct way of doint >>> it? >>> >>> On Thu, Aug 16, 2018 at 11:30 AM, Vitor Medina Cruz < >>> vitormcruz(a)gmail.com> wrote: >>> >>>> Hello, >>>> >>>> In a class that uses a Trait, how can I override one of it's method by >>>> appending behavior to the method implemented by the Trait? In a typical >>>> override, this is done by calling super: >>>> >>>> method >>>> >>>> super method >>>> "extended behavior" >>>> ... >>>> >>>> >>>> Is there a way to change "super" to a reference the Trait? >>>> >>>> Regards, >>>> Vitor >>>> >>> >>> >>> >> > > -- > Pablo Tesone. > tesonep(a)gmail.com >

Aug. 17, 2018

Re: [Pharo-users] Making TDD in pharo work properly (aka - walkback on a missing class is nasty)

by Marcus Denker

> On 17 Aug 2018, at 13:00, Tim Mackinnon <tim(a)testit.works> wrote: > > > Hi Marcus - I can put an image somewhere if that helps (do you just need the .image and .changes)? > > Or you can repro from a fresh 6.1 if you follow the exercism Pharo instructions (https://exercism.io/tracks/pharo <https://exercism.io/tracks/pharo>) to load the first hello world-world example and run the tests. This has my code changes to make create work with a nil class - but maybe we can do better? > I will do that and have a look! > Tim > > > Sent from my iPhone > > On 17 Aug 2018, at 06:21, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > >> >> >>> On 10 Aug 2018, at 23:16, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>> >>> Actually I think I figured that bit out - a bit clumsily - (pointers appreciated) >>> >>> createMissingClassActionFor: aMessage in: aContext >>> |errorNode senderContext newClass variableNode | >>> senderContext := aContext sender. >>> errorNode := senderContext method sourceNodeExecutedForPC: senderContext pc. >>> variableNode := errorNode receiver receiver. >>> >>> newClass := OCUndeclaredVariableWarning new node: variableNode; defineClass: variableNode name. >>> aContext restart. >>> >>> However that last line is wrong, as it doesnât restart with my newly defined class - I also tried >>> >>> aContext restartWithNewReceiver: newClass >>> >>> But again, I get a debugger where my class is still bound to nil. So whatâs the trick to re-evaluate with the new class Iâve created? Or maybe Iâm totally on the wrong track (still its very interestingâ¦) >>> >> >> >> what is a bit bad is that you catch the problem âtoo lateâ (that is, the DNU to nil, not the read of nil), so nil is already pushed on the stack at this point. >> >> I tried it in the inspector and at least the class binding was correct after defining the classâ¦ do you have an image with the whole code to try? >> >> Marcus >> >>

Aug. 17, 2018

Re: [Pharo-users] Making TDD in pharo work properly (aka - walkback on a missing class is nasty)

by Tim Mackinnon

Hi Marcus - I can put an image somewhere if that helps (do you just need the .image and .changes)? Or you can repro from a fresh 6.1 if you follow the exercism Pharo instructions (https://exercism.io/tracks/pharo) to load the first hello world-world example and run the tests. This has my code changes to make create work with a nil class - but maybe we can do better? Tim Sent from my iPhone > On 17 Aug 2018, at 06:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 10 Aug 2018, at 23:16, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Actually I think I figured that bit out - a bit clumsily - (pointers appreciated) >> >> createMissingClassActionFor: aMessage in: aContext >> |errorNode senderContext newClass variableNode | >> senderContext := aContext sender. >> errorNode := senderContext method sourceNodeExecutedForPC: senderContext pc. >> variableNode := errorNode receiver receiver. >> >> newClass := OCUndeclaredVariableWarning new node: variableNode; defineClass: variableNode name. >> aContext restart. >> >> However that last line is wrong, as it doesnât restart with my newly defined class - I also tried >> >> aContext restartWithNewReceiver: newClass >> >> But again, I get a debugger where my class is still bound to nil. So whatâs the trick to re-evaluate with the new class Iâve created? Or maybe Iâm totally on the wrong track (still its very interestingâ¦) >> > > > what is a bit bad is that you catch the problem âtoo lateâ (that is, the DNU to nil, not the read of nil), so nil is already pushed on the stack at this point. > > I tried it in the inspector and at least the class binding was correct after defining the classâ¦ do you have an image with the whole code to try? > > Marcus > >

Aug. 17, 2018

Re: [Pharo-users] Is the debugger known to be unstable on recent Pharo 7?

by Tim Mackinnon

I forgot to give the exact image number - it was build 1167 from around 13/Aug. Sent from my iPhone > On 17 Aug 2018, at 06:32, Tim Mackinnon <tim(a)testit.works> wrote: > > > Hi, Iâm doing some travelling and had a stretch on a plane with Pharo 7 - 64bit b166, and was trying out some changes to Calypso to plug in some potential keyboard extensions. > > Anyway, in figuring stuff out I noticed the debugger had a number of issues - which I can try to investigate more but wanted to say something before ploughing on. > > When I hit a method invoked from the keyboard which has self halt (not a soft breakpoint, as I was changing code and didnât want to keep losing the breakpoint) - when I made a change and hit save I get an extra empty predebug window ? The older debug window also has a my single method but no stack and is not debuggable. The upshot is that I have to start debugging all over again? > > I also noticed that when I hit an error and got a debugger and then fixed the error, resumed but then hit another - the title of the window was still the old error msg and not the new one (so quite confusing). > > Has there been recent work done in the debugger that might explain these? > > Tim > > Sent from my iPhone >

Aug. 17, 2018

Is the debugger known to be unstable on recent Pharo 7?

by Tim Mackinnon

Hi, Iâm doing some travelling and had a stretch on a plane with Pharo 7 - 64bit b166, and was trying out some changes to Calypso to plug in some potential keyboard extensions. Anyway, in figuring stuff out I noticed the debugger had a number of issues - which I can try to investigate more but wanted to say something before ploughing on. When I hit a method invoked from the keyboard which has self halt (not a soft breakpoint, as I was changing code and didnât want to keep losing the breakpoint) - when I made a change and hit save I get an extra empty predebug window ? The older debug window also has a my single method but no stack and is not debuggable. The upshot is that I have to start debugging all over again? I also noticed that when I hit an error and got a debugger and then fixed the error, resumed but then hit another - the title of the window was still the old error msg and not the new one (so quite confusing). Has there been recent work done in the debugger that might explain these? Tim Sent from my iPhone

Aug. 17, 2018

Re: [Pharo-users] separate native window of same Pharo image

by kmo

Who knows whether OSWindow is maintained? Who knows if anybody cares that it doesn't work on Windows? OSWindow is like lots of things that suddenly appear in the Pharo standard image. There's no documentation. There's no plan. That's the Pharo way. Give it a year or two and it will be superseded by another framework doing the same thing which will also have no documentation, killer bugs, and no plan. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 17, 2018

Re: [Pharo-users] Making TDD in pharo work properly (aka - walkback on a missing class is nasty)

by Marcus Denker

> On 10 Aug 2018, at 23:16, Tim Mackinnon <tim(a)testit.works> wrote: > > Actually I think I figured that bit out - a bit clumsily - (pointers appreciated) > > createMissingClassActionFor: aMessage in: aContext > |errorNode senderContext newClass variableNode | > senderContext := aContext sender. > errorNode := senderContext method sourceNodeExecutedForPC: senderContext pc. > variableNode := errorNode receiver receiver. > > newClass := OCUndeclaredVariableWarning new node: variableNode; defineClass: variableNode name. > aContext restart. > > However that last line is wrong, as it doesnât restart with my newly defined class - I also tried > > aContext restartWithNewReceiver: newClass > > But again, I get a debugger where my class is still bound to nil. So whatâs the trick to re-evaluate with the new class Iâve created? Or maybe Iâm totally on the wrong track (still its very interestingâ¦) > what is a bit bad is that you catch the problem âtoo lateâ (that is, the DNU to nil, not the read of nil), so nil is already pushed on the stack at this point. I tried it in the inspector and at least the class binding was correct after defining the classâ¦ do you have an image with the whole code to try? Marcus

Aug. 17, 2018