I'm not sure I understand your question. What are you wanting? Take care, Sina -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of black ares Sent: Wednesday, September 08, 2010 5:34 AM To: programmingblind@xxxxxxxxxxxxx Subject: Re: MVC no personal involvement Sina, the fact that I know and use mvc does not mean I like it. More over I didn't use mvc, but model view presenter. offer me some points/links about what you use as a methodology strictly for architecture. Because agile is a more general concept. I use agile in practice as SCRUM for small teams of programers, but in large teams agile does not work so well so I grow up on PRINCE 2. ----- Original Message ----- From: "Sina Bahram" <sbahram@xxxxxxxxx> To: <programmingblind@xxxxxxxxxxxxx> Sent: Wednesday, September 08, 2010 8:04 AM 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