Re: MVC
- From: "black ares" <matematicianu2003@xxxxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Wed, 8 Sep 2010 18:00:59 +0300
a real benefit of mvc, is that that you can write your calculator
as an eclipse application and at what moment you want, if you well designed
using mvc this app, you will be able to write a swing interface, a web one,
or any other variant you want and that is all for a new application.
Infact that is the point, you write once the business and then you can write
as many clients of that business you want, you can "present" it in what form
you want.
But such design must have a serious reason.
For example if you write a simple application which intent will be never to
be used in different forms
you can gain more time by using other patterns like rad, data driven, table
pattern, or smart ui.
----- Original Message -----
From: "Homme, James" <james.homme@xxxxxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Wednesday, September 08, 2010 2:22 PM
Subject: RE: MVC
Hi,
This started because I wanted to create a very small project in Java to put
together what I'm learning about classes and such as I go along. I was
thinking that if I created a calculator program that a small project like
that wouldn't get in the way of learning too much. The model would be all of
the methods that do the math. The controller would be that part that figures
out which math methods to call. The view would be what the person who runs
the application sees. At first, it would be a command line interface. Later,
if I've done it correctly, it would maybe be a user interface built with
SWT. As I catch onto arrays, I could build a method that, let's say, adds as
many numbers as are in the array. I'm reaching for examples here.
Jim
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
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Sina Bahram
Sent: Wednesday, September 08, 2010 1:05 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: MVC
This is the version of MVC most commonly associated with the web. MVC is not
always under such restrictions. For example, sometimes,
it's necessary to move where you maintain state, simply because of
definitions you've laid out that state the view can't speak to
the model directly, even though other definitions imply a lack of state
being maintained anywhere but in the model.
Frankly, I'm not a huge fan of MVC. I find it impractical, very limiting,
and very rigid. I sort of liken it to the waterfall
development methodology of software engineering. I tend to be more of an
agile/star model guy, which means that I also really like
things like software busses.
Again though, different strokes for different folks.
Take care,
Sina
________________________________
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of black ares
Sent: Tuesday, September 07, 2010 11:37 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: MVC
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 <mailto:james.homme@xxxxxxxxxxxx>
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
<http://mysites.highmark.com/personal/lidikki/Blog/default.aspx> . Discuss
accessibility here
<http://collaborate.highmark.com/COP/technical/accessibility/default.aspx> .
Accessibility Wiki: Breaking news
and accessibility advice
<http://collaborate.highmark.com/COP/technical/accessibility/Accessibility%20Wiki/Forms/AllPages.aspx>
________________________________
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.
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
