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