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

Hi, Bindings is an issue indeed. They are at the same level as theming and we are not at that level yet. At present time we are focused on showing the breadth of what we can achieve with the new infrastructure. We are currently using only the Bloc keybinding mechanism (equivalent to

[Pharo-users] Working with an entire project in git

Hey, all.. I was just checking in to see the progress of managing an entire project with git. The last I checked in, this was a work in progress. My current pet project consists of a handful of classes with maybe two handfuls of required packages. Is the entire metacello configuration being

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

On Fri, 17 Aug 2018 at 12:48, Tudor Girba 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

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

The direct link to instructions is here: 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

Re: [Pharo-users] Trait method override

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

Re: [Pharo-users] Trait method override

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.

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

> On 17 Aug 2018, at 13:00, Tim Mackinnon 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 >

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

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

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

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

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

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

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

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

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

> On 10 Aug 2018, at 23:16, Tim Mackinnon 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.

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

-- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

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

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:

Re: [Pharo-users] feenk log

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 wrote: > > Hi, > > We again got carried away and forgot to update the world about what is up in > our corner. Here is

Re: [Pharo-users] Trait method override

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 wrote: > Thanks Julian! > > On Thu, Aug 16, 2018 at 5:38 PM, Julien > wrote: > >> Hello