[Pharo-project] about events :)
hi may be I'm wrong but I have the impression that we have around three different kinds of event system in the system - actionMap - announcement - changed: Could we simplify that? Stef
Stéphane Ducasse wrote:
hi
may be I'm wrong but I have the impression that we have around three different kinds of event system in the system
- actionMap - announcement - changed:
Could we simplify that? Stef
Yes! Kill #changed: And if you adopt announcements, kill actionMap too! Cheers, Juan Vuletich
ok I would love to :) On Sep 19, 2010, at 3:42 PM, Juan Vuletich wrote:
Stéphane Ducasse wrote:
hi may be I'm wrong but I have the impression that we have around three different kinds of event system in the system
- actionMap - announcement - changed: Could we simplify that? Stef
Yes! Kill #changed: And if you adopt announcements, kill actionMap too!
Cheers, Juan Vuletich
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I don't really care what it is, but we need some way for things unknown to the framework to spy on what is happening; Announcements are fine. I am no big fan of the changed mechanism, but that will be a breaking change if ever there were one. Stef, are we up for that? ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Juan Vuletich [juan@jvuletich.org] Sent: Sunday, September 19, 2010 9:42 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] about events :) Stéphane Ducasse wrote:
hi
may be I'm wrong but I have the impression that we have around three different kinds of event system in the system
- actionMap - announcement - changed:
Could we simplify that? Stef
Yes! Kill #changed: And if you adopt announcements, kill actionMap too! Cheers, Juan Vuletich _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
We should not stack 3 different ways of doing things on top of the other.
I don't really care what it is, but we need some way for things unknown to the framework to spy on what is happening; Announcements are fine. I am no big fan of the changed mechanism, but that will be a breaking change if ever there were one. Stef, are we up for that?
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Juan Vuletich [juan@jvuletich.org] Sent: Sunday, September 19, 2010 9:42 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] about events :)
Stéphane Ducasse wrote:
hi
may be I'm wrong but I have the impression that we have around three different kinds of event system in the system
- actionMap - announcement - changed:
Could we simplify that? Stef
Yes! Kill #changed: And if you adopt announcements, kill actionMap too!
Cheers, Juan Vuletich
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Stef, I didn't ask whether we *should* kill the changed mechanism, I asked whether we had the (pardon me) balls do do so? :) Seriously, that will torch a lot of Morphic code. I personally volunteer to rewrite the little bit of Morphic code I have to accommodate the change. In the spirit of "somebody has to say it," the complaints will go like this: "there is a LOT of code outside the image, and you guys don't care about it - you just break it." I suspect that most of that code is broken anyway, and can/should be loaded carefully, but it will certainly be broken under this proposal. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Sunday, September 19, 2010 10:49 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] about events :) We should not stack 3 different ways of doing things on top of the other.
I don't really care what it is, but we need some way for things unknown to the framework to spy on what is happening; Announcements are fine. I am no big fan of the changed mechanism, but that will be a breaking change if ever there were one. Stef, are we up for that?
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Juan Vuletich [juan@jvuletich.org] Sent: Sunday, September 19, 2010 9:42 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] about events :)
Stéphane Ducasse wrote:
hi
may be I'm wrong but I have the impression that we have around three different kinds of event system in the system
- actionMap - announcement - changed:
Could we simplify that? Stef
Yes! Kill #changed: And if you adopt announcements, kill actionMap too!
Cheers, Juan Vuletich
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On 19 September 2010 16:42, Juan Vuletich <juan@jvuletich.org> wrote:
Stéphane Ducasse wrote:
hi may be I'm wrong but I have the impression that we have around three different kinds of event system in the system
    - actionMap     - announcement     - changed: Could we simplify that? Stef
Yes! Kill #changed: And if you adopt announcements, kill actionMap too!
amen. But we have to add weak subscriptions to announcements first, otherwise you won't be able to properly reimplement actionMap/changed: without that. I provided some code for that, but i'm not sure if it integrated into pharo yet.
Cheers, Juan Vuletich
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.
+10 - Weak subscriptions are a must. Absent that, we'll end up with bloated images and lots of unhappy users. ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua@gmail.com] Sent: Sunday, September 19, 2010 8:01 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] about events :) On 19 September 2010 16:42, Juan Vuletich <juan@jvuletich.org> wrote:
Stéphane Ducasse wrote:
hi may be I'm wrong but I have the impression that we have around three different kinds of event system in the system
- actionMap - announcement - changed: Could we simplify that? Stef
Yes! Kill #changed: And if you adopt announcements, kill actionMap too!
amen. But we have to add weak subscriptions to announcements first, otherwise you won't be able to properly reimplement actionMap/changed: without that. I provided some code for that, but i'm not sure if it integrated into pharo yet.
Cheers, Juan Vuletich
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Thinking aloud, How difficult can be to make #changed: and actionMaps use Announcements as a first step? So we don't break the existing contract changing the behavior :) But I'm talking from my ignorance, because I don't have in mind how all of them works... On Sun, Sep 19, 2010 at 9:11 PM, Schwab,Wilhelm K <bschwab@anest.ufl.edu>wrote:
+10 - Weak subscriptions are a must. Absent that, we'll end up with bloated images and lots of unhappy users.
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [ pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko [ siguctua@gmail.com] Sent: Sunday, September 19, 2010 8:01 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] about events :)
On 19 September 2010 16:42, Juan Vuletich <juan@jvuletich.org> wrote:
Stéphane Ducasse wrote:
hi may be I'm wrong but I have the impression that we have around three different kinds of event system in the system
- actionMap - announcement - changed: Could we simplify that? Stef
Yes! Kill #changed: And if you adopt announcements, kill actionMap too!
amen. But we have to add weak subscriptions to announcements first, otherwise you won't be able to properly reimplement actionMap/changed: without that. I provided some code for that, but i'm not sure if it integrated into pharo yet.
Cheers, Juan Vuletich
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
open ticket so that not to forget :) 2010/9/20 Guillermo Polito <guillermopolito@gmail.com>
Thinking aloud, How difficult can be to make #changed: and actionMaps use Announcements as a first step? So we don't break the existing contract changing the behavior :)
But I'm talking from my ignorance, because I don't have in mind how all of them works...
On Sun, Sep 19, 2010 at 9:11 PM, Schwab,Wilhelm K <bschwab@anest.ufl.edu>wrote:
+10 - Weak subscriptions are a must. Absent that, we'll end up with bloated images and lots of unhappy users.
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [ pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko [ siguctua@gmail.com] Sent: Sunday, September 19, 2010 8:01 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] about events :)
On 19 September 2010 16:42, Juan Vuletich <juan@jvuletich.org> wrote:
Stéphane Ducasse wrote:
hi may be I'm wrong but I have the impression that we have around three different kinds of event system in the system
- actionMap - announcement - changed: Could we simplify that? Stef
Yes! Kill #changed: And if you adopt announcements, kill actionMap too!
amen. But we have to add weak subscriptions to announcements first, otherwise you won't be able to properly reimplement actionMap/changed: without that. I provided some code for that, but i'm not sure if it integrated into pharo yet.
Cheers, Juan Vuletich
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Mariano Martinez Peck wrote
open ticket so that not to forget :)
I didn't see one, so I added it http://code.google.com/p/pharo/issues/detail?id=5044 -- View this message in context: http://forum.world.st/about-events-tp2545766p4144203.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
participants (7)
-
Guillermo Polito -
Igor Stasenko -
Juan Vuletich -
Mariano Martinez Peck -
Schwab,Wilhelm K -
Sean P. DeNigris -
Stéphane Ducasse