Why Isn't #abtWhen:perform: etc. Used More?

[dhasegawa]

This PDF describes the #abtWhen:perform:receiver:selector: and #signalEvent: protocol for separating the model from the view.

http://people.engr.ncsu.edu/efg/517/f01 ... /lec10.pdf

I don't recall seeing these methods used much in VAST applications. In fact, in most of the ones that I've worked on, someone has written a controller layer (usually modeled after VisualWorks) to separate the model and view. I was wondering why these methods aren't used more. Is there some known deficiency in the #abtWhen:perform:receiver:selector: framework?

Thanks in advance,
Dave

[marten]

This PDF describes the #abtWhen:perform:receiver:selector: and #signalEvent: protocol for separating the model from the view.

http://people.engr.ncsu.edu/efg/517/f01 ... /lec10.pdf

I don't recall seeing these methods used much in VAST applications. In fact, in most of the ones that I've worked on, someone has written a controller layer (usually modeled after VisualWorks) to separate the model and view. I was wondering why these methods aren't used more. Is there some known deficiency in the #abtWhen:perform:receiver:selector: framework?

Thanks in advance,
Dave

Actually a derivate method call like #abtWhen:perform: and #signalEvent: are used in the automatically generated code of the GUI framework of VASmalltalk - therefore I would say, that these message calls are indeed used in the image.