Just for the record I am in agreement as I think most of us are about this.

But....

I think as a community must make one thing clear

Pharo is environment meant to be hacked. Its not always to do so but similarly to Squeak, the goal here is to give developers and environment that they can design and modify themselves with ease. At least a lot more than other languages and this is where Pharo really excels.

In the end Pharo does not tries to be the most popular thing out there, it tries to fill a gap that others dont or cant. Sure we want to make Pharo popular but making something that is a ready made solution is not our top priority.  Making something modifiable and direct so much more.

I think its our responsibility to make this clear to newcomers.

Or else people will wonder, why not use python, ruby or whatelse which comes with sophisticated IDEs far more lazy friendly than Pharo.

Pharo is definetly  , by nature, lazy coder friendly. Its for coders that like to design their own workflow.

On Sat, Apr 16, 2016 at 1:51 PM kmo <[hidden email]> wrote:

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-tp4890079p4890285.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.