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

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

Re: [Pharo-users] RubShoutStylerDecorator doesnotunderstand: #move:for:controller:

by Jeff Gray

<http://forum.world.st/file/t160774/error.png> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 17, 2018

RubShoutStylerDecorator doesnotunderstand: #move:for:controller:

by Jeff Gray

Hi all, I was debugging my seaside application yesterday. I saved and closed the image. Then when I opened Pharo tonight I got the RubShoutStylerDecorator error. If I close the error window another one immediately pops up. Any idea what I can do? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 17, 2018

Re: [Pharo-users] feenk log

by Marcus Denker

Thanks, recorded for the newsletter: http://newsletter.pharo.org (the one after the next which is going out today, I think). > On 17 Aug 2018, at 06:47, 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: > > -- > 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 > - The text editor can handle emojis: > https://twitter.com/feenkcom/status/1021872214151507968 > > -- > GT > -- > > - Inspector > We now have an initial version of a working inspector with resizable panes: > https://twitter.com/feenkcom/status/1030091849795612672 > https://twitter.com/feenkcom/status/1030314856736538624 > It shows a display string for the current object: > https://twitter.com/feenkcom/status/1024564065870512129 > It can handle errors in the definition of views gracefully: > https://twitter.com/feenkcom/status/1009174937217720320 > We now have multiple extensions expressed in the new Inspector: > https://twitter.com/feenkcom/status/1024321868566814720 > https://twitter.com/feenkcom/status/1022393383850008576 > > - Documenter saw multiple enhancements. > We can now resize various previews live: > https://twitter.com/feenkcom/status/1002851190475026432 > https://twitter.com/feenkcom/status/1001407762285375490 > https://twitter.com/feenkcom/status/1001152789874167808 > It now relies on the annotation mechanism from Pillar: > https://twitter.com/feenkcom/status/1006508725409079298 > We can now link classes and expand their definition: > https://twitter.com/feenkcom/status/1014609460520775681 > https://twitter.com/feenkcom/status/1029085603948843008 > The preview of examples can handle errors gracefully: > https://twitter.com/feenkcom/status/1022123808524836864 > We can run examples in place, enabling a smoother tutorial experience: > https://twitter.com/feenkcom/status/1028390957023223809 > We have new documentation expressed in it: > https://twitter.com/feenkcom/status/1007008814204444672 > > > > Have fun, > The feenk team > > -- > www.feenk.com > > "Presenting is storytelling." > >

Aug. 17, 2018

Re: [Pharo-users] Trait method override

by tesonep＠gmail.com

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

feenk log

by Tudor Girba

Hi, We again got carried away and forgot to update the world about what is up in our corner. Here is a summary: -- 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 - The text editor can handle emojis: https://twitter.com/feenkcom/status/1021872214151507968 -- GT -- - Inspector We now have an initial version of a working inspector with resizable panes: https://twitter.com/feenkcom/status/1030091849795612672 https://twitter.com/feenkcom/status/1030314856736538624 It shows a display string for the current object: https://twitter.com/feenkcom/status/1024564065870512129 It can handle errors in the definition of views gracefully: https://twitter.com/feenkcom/status/1009174937217720320 We now have multiple extensions expressed in the new Inspector: https://twitter.com/feenkcom/status/1024321868566814720 https://twitter.com/feenkcom/status/1022393383850008576 - Documenter saw multiple enhancements. We can now resize various previews live: https://twitter.com/feenkcom/status/1002851190475026432 https://twitter.com/feenkcom/status/1001407762285375490 https://twitter.com/feenkcom/status/1001152789874167808 It now relies on the annotation mechanism from Pillar: https://twitter.com/feenkcom/status/1006508725409079298 We can now link classes and expand their definition: https://twitter.com/feenkcom/status/1014609460520775681 https://twitter.com/feenkcom/status/1029085603948843008 The preview of examples can handle errors gracefully: https://twitter.com/feenkcom/status/1022123808524836864 We can run examples in place, enabling a smoother tutorial experience: https://twitter.com/feenkcom/status/1028390957023223809 We have new documentation expressed in it: https://twitter.com/feenkcom/status/1007008814204444672 Have fun, The feenk team -- www.feenk.com "Presenting is storytelling."

Aug. 17, 2018

Re: [Pharo-users] Trait method override

by Vitor Medina Cruz

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 >> > > >

Aug. 16, 2018

Re: [Pharo-users] Trait method override

by Julien

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 Villeneuve d'Ascq 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/ <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 <mailto:vitormcruz@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 >

Aug. 16, 2018

Re: [Pharo-users] Zinc loading problems (as project dep) - versions mess

by Petr Fischer

That Metacello code snip did not update the ConfigurationOfZincHTTPComponents to the latest version, so actual stable version was not loaded :( Weird. pf > Yes, those .TheIntegrator versions are not real, can't explain that further. > > If you want to go to the very latest version, you also have to load the latest version of ConfigurationOfZincHTTPComponents first, else you get an older latest version (yes this is a bit confusing, but it makes perfect sense when you think of it). > > All this is normally done by the Metacello mechanism. Here is how you can do that in direct scripting: > > Metacello new > configuration: 'ZincHTTPComponents'; > repository: 'http://mc.stfx.eu/ZincHTTPComponents'; > version: #stable; > load: #('Core' 'WebSocket' ). > > (Untested though). > > > On 16 Aug 2018, at 19:45, Petr Fischer via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > > > > From: Petr Fischer <petr.fischer(a)me.com> > > Subject: Re: [Pharo-users] Zinc loading problems (as project dep) - versions mess > > Date: 16 August 2018 at 19:45:41 GMT+2 > > To: pharo-users(a)lists.pharo.org > > > > > > I can't understand a mess in Zinc packages versions. I downloaded fresh 6.1 (32bit) image from pharo.org, opened Monticelo Browser and searced for 'Zinc-HTTP' package. > > There is version Zinc-HTTP (TheIntegrator.461). Repository info points to "http://mc.stfx.eu/ZincHTTPComponents" by default, so I opened the repository and there is no packages with "TheIntegrator". Even version numbers are different - version SvenVanCaekenberghe.461 is different if I diff it. It looks like the version TheIntegrator.461 is close to SvenVanCaekenberghe.453. > > > > Next test: when I run this code in fresh image: > > > > ConfigurationOfZincHTTPComponents project load: #stable > > > > there is Zinc-HTTP (SvenVanCaekenberghe.453) after load. Why not 475 (it's stable or not)? > > > > And now, I'm totally confused. > > > > pf > > > > > >> Hi Petr, > >> > >> I also have > >> > >> project: 'ZincHTTPComponents' with: [ > >> spec > >> className: 'ConfigurationOfZincHTTPComponents'; > >> repository: 'http://mc.stfx.eu/ZincHTTPComponents'; > >> loads: #('Core' 'Tests' 'REST' 'AWS'); > >> versionString: #stable ]; > >> > >> in my main project, which has not changed in years and always works, AFAIK. > >> > >> I also use(d) the load expression > >> > >> ConfigurationOfZincHTTPComponents project load: #stable > >> > >> a lot and it normally works. > >> > >> Metacello sometimes acts weird when you already have code/projects loaded. > >> > >> I am afraid I don't know what could be wrong. > >> > >> Sven > >> > >>> On 16 Aug 2018, at 17:09, Petr Fischer via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > >>> > >>> > >>> From: Petr Fischer <petr.fischer(a)me.com> > >>> Subject: Zinc loading problems (as project dep) > >>> Date: 16 August 2018 at 17:09:41 GMT+2 > >>> To: pharo-users(a)lists.pharo.org > >>> > >>> > >>> Hello, > >>> > >>> I am trying to load stable Zinc as dependency in my project, like this: > >>> > >>> ... > >>> project: 'ZincHTTPComponents' with: [ > >>> spec > >>> className: #ConfigurationOfZincHTTPComponents; > >>> versionString: #'stable'; > >>> loads: #('Core' 'WebSocket' ); > >>> repository: 'http://mc.stfx.eu/ZincHTTPComponents/' ]. > >>> ... > >>> > >>> I need WebSocket package, whiuch is not loaded by default and updated Core package (there is new method ZnClient defaultEncoder: - I need this). > >>> > >>> Actual stable version of ZincHTTPComponents is 2.9.4 (for Pharo 6.x) and in this 2.9.4 stable version, there is Zinc-HTTP package with version Zinc-HTTP-SvenVanCaekenberghe.475. > >>> > >>> Default version in Pharo 6.1 image is Zinc-HTTP-TheIntegrator.461. > >>> > >>> After my project configuration load, there is no updated Zinc in my image. > >>> > >>> When I try to load manually by: > >>> > >>> ConfigurationOfZincHTTPComponents project load: #stable. > >>> > >>> error dialog occurs complaining about Zinc-HTTP have unsaved changes in the image (load/merge/cancel) - so, maybe, automatic load of Zinc as project depenedency is ignored due to this reason. > >>> > >>> How to solve this situation? Can I force dependency to load (in my project ConfigurationOf)? > >>> > >>> Thanks! Petr Fischer > >>> > >>> > >>> > >>> > >>> > >> > > > > > > >

Aug. 16, 2018

Re: [Pharo-users] Zinc loading problems (as project dep) - versions mess

by Sven Van Caekenberghe

Yes, those .TheIntegrator versions are not real, can't explain that further. If you want to go to the very latest version, you also have to load the latest version of ConfigurationOfZincHTTPComponents first, else you get an older latest version (yes this is a bit confusing, but it makes perfect sense when you think of it). All this is normally done by the Metacello mechanism. Here is how you can do that in direct scripting: Metacello new configuration: 'ZincHTTPComponents'; repository: 'http://mc.stfx.eu/ZincHTTPComponents'; version: #stable; load: #('Core' 'WebSocket' ). (Untested though). > On 16 Aug 2018, at 19:45, Petr Fischer via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Re: [Pharo-users] Zinc loading problems (as project dep) - versions mess > Date: 16 August 2018 at 19:45:41 GMT+2 > To: pharo-users(a)lists.pharo.org > > > I can't understand a mess in Zinc packages versions. I downloaded fresh 6.1 (32bit) image from pharo.org, opened Monticelo Browser and searced for 'Zinc-HTTP' package. > There is version Zinc-HTTP (TheIntegrator.461). Repository info points to "http://mc.stfx.eu/ZincHTTPComponents" by default, so I opened the repository and there is no packages with "TheIntegrator". Even version numbers are different - version SvenVanCaekenberghe.461 is different if I diff it. It looks like the version TheIntegrator.461 is close to SvenVanCaekenberghe.453. > > Next test: when I run this code in fresh image: > > ConfigurationOfZincHTTPComponents project load: #stable > > there is Zinc-HTTP (SvenVanCaekenberghe.453) after load. Why not 475 (it's stable or not)? > > And now, I'm totally confused. > > pf > > >> Hi Petr, >> >> I also have >> >> project: 'ZincHTTPComponents' with: [ >> spec >> className: 'ConfigurationOfZincHTTPComponents'; >> repository: 'http://mc.stfx.eu/ZincHTTPComponents'; >> loads: #('Core' 'Tests' 'REST' 'AWS'); >> versionString: #stable ]; >> >> in my main project, which has not changed in years and always works, AFAIK. >> >> I also use(d) the load expression >> >> ConfigurationOfZincHTTPComponents project load: #stable >> >> a lot and it normally works. >> >> Metacello sometimes acts weird when you already have code/projects loaded. >> >> I am afraid I don't know what could be wrong. >> >> Sven >> >>> On 16 Aug 2018, at 17:09, Petr Fischer via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >>> >>> >>> From: Petr Fischer <petr.fischer(a)me.com> >>> Subject: Zinc loading problems (as project dep) >>> Date: 16 August 2018 at 17:09:41 GMT+2 >>> To: pharo-users(a)lists.pharo.org >>> >>> >>> Hello, >>> >>> I am trying to load stable Zinc as dependency in my project, like this: >>> >>> ... >>> project: 'ZincHTTPComponents' with: [ >>> spec >>> className: #ConfigurationOfZincHTTPComponents; >>> versionString: #'stable'; >>> loads: #('Core' 'WebSocket' ); >>> repository: 'http://mc.stfx.eu/ZincHTTPComponents/' ]. >>> ... >>> >>> I need WebSocket package, whiuch is not loaded by default and updated Core package (there is new method ZnClient defaultEncoder: - I need this). >>> >>> Actual stable version of ZincHTTPComponents is 2.9.4 (for Pharo 6.x) and in this 2.9.4 stable version, there is Zinc-HTTP package with version Zinc-HTTP-SvenVanCaekenberghe.475. >>> >>> Default version in Pharo 6.1 image is Zinc-HTTP-TheIntegrator.461. >>> >>> After my project configuration load, there is no updated Zinc in my image. >>> >>> When I try to load manually by: >>> >>> ConfigurationOfZincHTTPComponents project load: #stable. >>> >>> error dialog occurs complaining about Zinc-HTTP have unsaved changes in the image (load/merge/cancel) - so, maybe, automatic load of Zinc as project depenedency is ignored due to this reason. >>> >>> How to solve this situation? Can I force dependency to load (in my project ConfigurationOf)? >>> >>> Thanks! Petr Fischer >>> >>> >>> >>> >>> >> > > >

Aug. 16, 2018