On Apr 28, 2012, at 2:39 PM, Gastón Dall' Oglio wrote:
Hi Guillermo.
When you combine these triggers with ads (as in your example), I see an analogy with the model of qt ui, see: http://qt-project.org/doc/qt-4.8/signalsandslots.html
In effect: "A signal is emitted when a particular event occurs." -> A Announcement is send when a particular event (trigger) occurs. " Qt's widgets have many predefined signals, but we can always subclass widgets to add our own signals to them" -> Morphic widgets have many predefined triggers, but we can always subclass widgets to add our own triggers to them. "A slot is a function that is called in response to a particular signal. " -> A AnnouncementSubscription is ? that is used in response to a particular announcement.
It's a mechanic for decouple between sender and interested in event occurrence.
As you surely know Morphic Designer follows basic ideas of the QtDesigner: https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki/...
Look at doc here (I never see code of this project), this approach not use announcement framework, but a signal implementation: https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki/...
I do not see the difference between signals and event. And yes we look at the code, it is not a really good idea to use thisContext for every little notifications.