13 Jul
2000
13 Jul
'00
7:29 p.m.
Stefan Matthias Aust wrote:
Actually, separating controller and view isn't that useful, but separating the model is.
You're kidding! By separating view from controller you get to have a variety of controller classes to do different things with the visual presentation. At the most trivial level this allows you to have read-only and read-write widgets for the same model without the model having to worry about it. You can have controllers that interact via mouse type inputs or key type inputs, or both or neither. You can have controllers that read interactions from a stream and auto-demonstrate an application.
--
Tim Rowledge, tim@sumeru.stanford.edu, http://sumeru.stanford.edu/tim
Klingon Code Warrior:- 4) "This machine is a piece of GAGH! I need dual
StrongARM2(*) processors if I am to do battle with this code!"
(*)What other sort of processor would a Klingon use?