On 22 November 2012 08:11, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I like the separation.
i have only one question: - shall we do this surgery (with announcer stuff) in base model, or - shall we make a separate model which wraps around existing model,and then provides a notification(s).
my main source of disdain about notifications is that in single class we will have to mix an action and notification about it i.e..
Selection>>cut self doThingsToCut. ... self announcer announce: IJustCutMyself.
this is IMO a bit stinky.
I would prefer a notification(s) to be in a separate layer:
ActiveText?
you suggest the name?
SelectionWatcher/Controller>>cut selection cut. ... self announcer announce: SelectionWasJustCut
despite that it looks like more costly in terms of implementation. But i don't like mixing multiple concerns in single place.
-- Best regards, Igor Stasenko.