April 2016 - Pharo-users - lists.pharo.org

RBRefactoring docs

by Peter UhnÃ¡k

Hi, is there any documentation for RBRefactoring? Since there are not even class comments the only thing I found is judging from tests. Thanks, Peter

April 16, 2016

Re: [Pharo-users] First impressions, was About Box

by Cyril Ferlicot

On Saturday, 16 April 2016, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > Thanks. I had started reading Pharo by Example, but it looks like Deep > into Pharo is more up to date. > > A new version of PBE is almost ready. You can find it at https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample… . Other formats https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample… <https://ci.inria.fr/pharo-contribution/view/Books/job/UpdatedPharoByExample…> > Thanks again, > Alistair > > >From my phone~~ -- Cheers Cyril Ferlicot

April 16, 2016

Re: [Pharo-users] First impressions, was About Box

by Alistair Grant

On Thu, Apr 14, 2016 at 08:37:39AM +0200, stepharo wrote: > Have a look at the chapter about command handler in Deep into Pharo > because you have all you need > > You can script the loading and execution of expressions easily. > > People like julien, damien at Pharodays started to resume a better DSL for > command descriptions. Thanks. I had started reading Pharo by Example, but it looks like Deep into Pharo is more up to date. Thanks again, Alistair

April 16, 2016

Re: [Pharo-users] Trapping the Pharo window close event

by Damien Pollet

On 16 April 2016 at 11:33, kmo <voxkmp(a)gmail.com> wrote: > /Pharo is yours, so you can add it. :)/ > > Yes, but I don't want to add it. I expect it to be there out of the box. > If you expect a perfect system out of the box, you will never get it. > think it's quite enough work for me to add my own code on window close. I > don't want to have to write the framework for doing it as well. > Point is, it's not by design if the feature you're asking for is absent out of the box; nobody in Pharo decided you should HAVE to implement it yourself. I think everyone agrees that the platform should provide that feature, however everyone is focused on different issues, and you seem to be the first one for whom it's an itch worth scratching. It's open-source, so the system is yours too and it's the responsibility of everyone to improve it. If you really need the feature but don't want to implement it yourself, you could sponsor someone via the Pharo association or the consortium.

April 16, 2016

Re: [Pharo-users] Trapping the Pharo window close event

by kmo

Well, my reply was rather tongue-in-cheek. I was mocking my own laziness and the laziness of developers like me. But really I have no problem in doing these things for myself. And I hope that soon I will be in a position to contribute to pharo myself. But overriding the close event is something any application developer is going to want to do. And every time you make a developer work harder than necessary to implement a basic feature you make the pharo platform less attractive. If you want more developers to use pharo you have to make basic things like this easy to do and easy to find out how to do. I do think that deployment of applications gets very little attention in pharo - yet it's a major issue of you want to make pharo a widely-used application platform. I'm not the only lazy developer, you know . -- View this message in context: http://forum.world.st/Trapping-the-Pharo-window-close-event-tp4890079p48902… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 16, 2016

Re: [Pharo-users] Trapping the Pharo window close event

by Peter UhnÃ¡k

Ah, right, that certainly sounds interesting. :) Pharo is yours, so you can add it. :) We already have a SystemAnnouncer so maybe it would be quite easy to addâ¦ it might be a nice exercise to get a bit more familiar with the system. Peter On Sat, Apr 16, 2016 at 11:01 AM, kmo <voxkmp(a)gmail.com> wrote: > The Dolphin approach was described by Estaban earlier in this thread. I've > never used Dolphin myself so cannot expand on it. > > > > -- > View this message in context: > http://forum.world.st/Trapping-the-Pharo-window-close-event-tp4890079p48902… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

April 16, 2016

Re: [Pharo-users] Trapping the Pharo window close event

by kmo

/Pharo is yours, so you can add it. :)/ Yes, but I don't want to add it. I expect it to be there out of the box. I think it's quite enough work for me to add my own code on window close. I don't want to have to write the framework for doing it as well. -- View this message in context: http://forum.world.st/Trapping-the-Pharo-window-close-event-tp4890079p48902… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 16, 2016

Re: [Pharo-users] Trapping the Pharo window close event

by Peter UhnÃ¡k

What's Doplin's approach? Also adding a configuration option for this situation is rather trivial. On Sat, Apr 16, 2016 at 9:42 AM, kmo <voxkmp(a)gmail.com> wrote: > As a developer you need to be able to control the program shut down. That > is > a given. > > I think I was expecting something like the Dolphin approach but it doesn't > exist in pharo. Having to overwrite an existing method is not elegant but > it > works. > > A similar issue exists with Growl notifications - I have a post on this as > well. > > > > -- > View this message in context: > http://forum.world.st/Trapping-the-Pharo-window-close-event-tp4890079p48902… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

April 16, 2016

Re: [Pharo-users] Trapping the Pharo window close event

by kmo

The Dolphin approach was described by Estaban earlier in this thread. I've never used Dolphin myself so cannot expand on it. -- View this message in context: http://forum.world.st/Trapping-the-Pharo-window-close-event-tp4890079p48902… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 16, 2016

Re: [Pharo-users] Trapping the Pharo window close event

by kmo

As a developer you need to be able to control the program shut down. That is a given. I think I was expecting something like the Dolphin approach but it doesn't exist in pharo. Having to overwrite an existing method is not elegant but it works. A similar issue exists with Growl notifications - I have a post on this as well. -- View this message in context: http://forum.world.st/Trapping-the-Pharo-window-close-event-tp4890079p48902… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 16, 2016