Wesley wrote:
As an example: in an instant messenger a new text message arrives. The
application puts it into the message log. The chat window automatically
updates with the new text. The statistics window about total # of
messages updates. Possibly other things happen. The point is I don't want
to have to think about the 'possible other things'. If the program gets
fat, I'll screw this up.
Sam wrote:
Personally I think a database should provide long-term storage for your
application's state, not drive the application's UI. If you need to
update
views based on state then that state should be in memory with mechanisms
to
easily detect changes.
True.
http://en.wikipedia.org/wiki/Model-view-controller
A change to the Model would raise events that the View can react to.
Hope this helps,
- Trey
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
