Hi, On 11 Dec 2011, at 08:07, Igor Stasenko wrote:
On 10 December 2011 10:41, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I would not say useless may be you need the composite and you do not need to repeat AddChild, RemoveChild all the times but use the composite
well.. usually a different events suppose different reactions to them, otherwise why care making lot event kinds if you handle them similarily?
Often the UI is built after/independently from the model. You want to have the model raise fine grained announcements to enable the layers on top, but sometimes it is easier in the UI to refresh everything whenever something happens. Cheers, Doru
Igor Stasenko wrote
which is pretty useless IMO.
The collaborative book says:
If you want to register the same action for multiple events, simply create an AnnouncementSet using a comma:
Parent>>initialize super initialize. self session announcer on: AddChild, RemoveChild do: [:it | self changeChild: it child]
-- View this message in context: http://forum.world.st/Re-Pharo-users-COTDC-94-AnnouncementSet-tp4178427p4179... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one."