Le 16/4/16 12:18, kmo a écrit :
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 you are :)
30 min a week is enough :)
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.
We know that.
Now I will not give the HUGE list of the things we are working on and
that default
developers are in need:
- good file library
- good list widget
- FFI
- decent texteditor
- a compiler :)
- ...
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.
Indeed. We started to push that when damien worked on the launcher and
we should continue.
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.