Re: MVC
- From: "black ares" <matematicianu2003@xxxxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Wed, 8 Sep 2010 06:37:28 +0300
a little bit different...
1. the model is formed from classes that assembles your domain and your
business logic.
Let say that there you will find classes like person, account, or something
similar.
But the model does not power lifting, it simply offer services.
2. The controller takes al user information/events from the view and uses the
services ofered by the model to make necesary changes.
3. View pass to the controller al user information/events and then query the
model about its state changes to reflect them on the view.
Simply:
the user does something, the view announce the controller that the user has
done something.
The controler, makes necesary calls to the model to cary out the needed actions.
The view sees if there are model changes and display them.
----- Original Message -----
From: Homme, James
To: programmingblind@xxxxxxxxxxxxx
Sent: Tuesday, September 07, 2010 9:59 PM
Subject: MVC
Hi,
Is this how Model View Controller works?
1. You have something on the back end, the model, that does all the heavy
lifting.
2. On top of that, you have the controller, which sits between the user and
the model that calls the methods of the model.
3. The view simply passes information from the user to the controller which
the controller interprets for the model.
Thanks.
Jim
Jim Homme,
Usability Services,
Phone: 412-544-1810. Skype: jim.homme
Internal recipients, Read my accessibility blog. Discuss accessibility here.
Accessibility Wiki: Breaking news and accessibility advice
------------------------------------------------------------------------------
This e-mail and any attachments to it are confidential and are intended
solely for use of the individual or entity to whom they are addressed. If you
have received this e-mail in error, please notify the sender immediately and
then delete it. If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this e-mail without the author's prior permission.
The views expressed in this e-mail message do not necessarily represent the
views of Highmark Inc., its subsidiaries, or affiliates.
Other related posts:
