This link has been bookmarked by 166 people . It was first bookmarked on 24 Apr 2006, by hanakuso.
-
26 Apr 14
-
23 Nov 13
-
18 Jul 12
-
14 Apr 12
-
16 Oct 11
-
28 Sep 11
-
12 Aug 11
-
-
The controller notifies the model of the user action, possibly resulting in a change in the model's state.
-
A view queries the model in order to generate an appropriate user interface (for example the view lists the shopping cart's contents). The view gets its own data from the model. In some implementations, the controller may issue a general instruction to the view to render itself. In others, the view is automatically notified by the model of changes in state (Observer) that require a screen update.
-
The model manages the behaviour and data of the application domain, responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller). In event-driven systems, the model notifies observers (usually views) when the information changes so that they can react.
-
The view renders the model into a form suitable for interaction, typically a user interface element. Multiple views can exist for a single model for different purposes. A viewport typically has a one to one correspondence with a display surface and knows how to render to it.
-
The controller receives user input and initiates a response by making calls on model objects. A controller accepts input from the user and instructs the model and viewport to perform actions based on that input.
-
-
04 Apr 11
David Naughton"Model–view–controller (MVC) is a software architecture,[1] currently considered an architectural pattern used in software engineering. The pattern isolates "domain logic" (the application logic for the user) from the user interface (input and presentation), permitting independent development, testing and maintenance of each (separation of concerns)."
-
14 Feb 11
-
04 Feb 11
-
24 Jan 11
-
The model manages the behavior and data of the application domain, responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller). In event-driven systems, the model notifies observers (usually views) when the information changes so that they can react.
The view renders the model into a form suitable for interaction, typically a user interface element. Multiple views can exist for a single model for different purposes. A viewport typically has a one to one correspondence with a display surface and knows how to render to it.
The controller receives input and initiates a response by making calls on model objects. A controller accepts input from the user and instructs the model and viewport to perform actions based on that input.
-
The controller receives GET or POST input and decides what to do with it
-
the view is the HTML or XHTML generated by the app
-
handing over to domain objects (i.e. the model) which contain the business rules and know how to carry out specific tasks such as processing a new subscription, and which hand control to (X)HTML-generating components such as templating engines, XML pipelines, Ajax callbacks, etc.
-
the 'model' in MVC is both the data and the business/domain logic needed to manipulate the data in the application
-
MVC does not specifically mention the data access layer because it is understood to be underneath or encapsulated by the model
-
The goal of MVC is, by decoupling models and views, to reduce the complexity in architectural design and to increase flexibility and maintainability of code
-
-
19 Dec 10
-
The model manages the behavior and data of the application domain, responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller). In event-driven systems, the model notifies observers (usually views) when the information changes so that they can react.
-
Multiple views can exist for a single model for different purposes.
-
The controller receives input and initiates a response by making calls on model objects. A controller accepts input from the user and instructs the model and viewport to perform actions based on that input.
-
-
13 Dec 10
brent lawrenceWikipedia- Model View Controller article
programming coding architecture design model view controller concept wikipedia mvc designpatterns Patterns pattern
-
28 Oct 10
-
26 Aug 10
-
18 May 10
-
When a model changes its state, it notifies its associated views so they can be refreshed
-
Models are not data access objects; however, in very simple apps that have little domain logic there is no real distinction to be made.
-
-
05 May 10
-
04 Feb 10
-
27 Jan 10
-
31 Dec 09
-
19 Oct 09
-
13 Oct 09
-
08 Aug 09
-
07 Aug 09
-
21 Jun 09
-
23 May 09
-
from the user interface
-
isolates "domain logic"
-
permitting independent development, testing and maintenance of each
-
converts
-
event from the user interface
-
controller handles the input
-
appropriate user action
-
the event
-
understandable for the model
-
possibly resulting in a change in the model's state
-
of the user action
-
controller notifies the model
-
the controller updates
-
in order to generate an appropriate user interface
-
The view gets its own data from the mode
-
view queries the model
-
the view is automatically notified by the model of changes in state (Observer) that require a screen update.
-
controller may issue a general instruction to the view to render itself
-
user interface waits for further user interactions, which restarts the control flow cycle
-
The goal of MVC is, by decoupling models and views, to reduce the complexity in architectural design and to increase flexibility and maintainability of code.
-
MVC is often seen in web applications, where the view is the actual HTML or XHTML page, and the controller is the code that gathers dynamic data and generates the content within the HTML or XHTML. Finally, the model is represented by the actual content, which is often stored in a database or in XML nodes, and the business rules that transform that content based on user actions.
-
responds to requests
-
responds to instructions to change state (usually from the controller)
-
The model manages the behavior and data
-
the model notifies observers (usually views) when the information changes so that they can react
-
Multiple views can exist for a single model for different purposes
-
The view renders the model into a form
-
accepts input from the user and instructs the model
-
The controller receives user input and initiates a response by making calls on model objects
-
MVC is often seen in web applications where the view is the HTML or XHTML generated by the app
-
handing over to domain objects (i.e. the model) that contain the business rules
-
The controller receives GET or POST input and decides what to do with it
-
know how to carry out specific tasks such as processing a new subscription, and which hand control to (X)HTML-generating components such as templating engines, XML pipelines, Ajax callbacks, etc
-
the 'model' in MVC is both the data and the business/domain logic needed to manipulate the data in the application
-
The model is not necessarily merely a database
-
When considered as a design pattern, MVC is semantically similar to the Observer pattern.
-
Although MVC is typically associated with frameworks, it is essentially an architecture
-
MVC does not specifically mention the data access layer because it is understood to be underneath or encapsulated by the model.
-
Renders the model into a form suitable for interaction, typically a user interface element. Multiple views can exist for a single model for different purposes
-
Processes and responds to events (typically user actions) and may indirectly invoke changes on the model.
-
Microsoft ASP.NET - reusing JQuery libraries and proprietary Microsoft AJAX Libraries.
-
-
-
16 Apr 09
-
15 Apr 09
-
29 Mar 09
-
20 Mar 09
-
16 Mar 09
-
10 Mar 09
-
isolates
-
the model represents the information (the data) of the application
-
-
26 Jan 09
-
14 Jan 09
-
08 Jan 09
-
06 Jan 09
-
22 Dec 08
-
01 Dec 08
-
07 Nov 08
-
02 Nov 08
Model-view-controller (MVC) is both a design pattern and an architectural pattern used in software engineering
architecture pattern model view controller software engineering
-
26 Oct 08
-
07 Oct 08
-
23 Sep 08
Colin HendersonModel-view-controller (MVC) is an architectural pattern used in software engineering. Successful use of the pattern isolates business logic from user interface considerations, resulting in an application where it is easier to modify either the visual appearance of the application or the underlying business rules without affecting the other. In MVC, the model represents the information (the data) of the application and the business rules used to manipulate the data; the view corresponds to elements of the user interface such as text, checkbox items, and so forth; and the controller manages details involving the communication to the model of user actions such as keystrokes and mouse movements.
-
16 Sep 08
-
11 Sep 08
-
05 Sep 08
-
19 Aug 08
-
resulting in an application where it is easier to modify either the visual appearance of the application or the underlying business rules without affecting the other.
-
resulting in an application where it is easier to modify either the visual appearance of the application or the underlying business rules without affecting the other
-
resulting in an application where it is easier to modify either the visual appearance of the application or the underlying business rules without affecting the other.
-
resulting in an application where it is easier to modify either the visual appearance of the application or the underlying business rules without affecting the other.
-
resulting in an application where it is easier to modify either the visual appearance of the application or the underlying business rules without affecting the other.
-
resulting in an application where it is easier to modify either the visual appearance of the application or the underlying business rules without affecting the other.
-
-
14 Aug 08
-
29 Jul 08
-
Successful use of the pattern isolates business logic from user interface considerations, resulting in an application where it is easier to modify either the visual appearance of the application or the underlying business rules without affecting the other. I
-
n MVC, the model represents the information (the data) of the application and the business rules used to manipulate the data, the view corresponds to elements of the user interface such as text, checkbox items, and so forth, and the controller manages details involving the communication to the model of user actions such as keystrokes and mouse movements.
-
It is common to split an application into separate layers that run on different computers: presentation (UI), domain logic, and data access. In MVC the presentation layer is further separated into view and controller.
-
MVC is often seen in web applications, where the view is the actual HTML page, and the controller is the code that gathers dynamic data and generates the content within the HTML. Finally, the model is represented by the actual content, usually stored in a database or in XML nodes, and the business rules that transform that content based on user actions.
-
-
24 Jul 08
-
11 Jul 08
-
19 Jun 08
-
24 May 08
-
13 May 08
Andre MalheiroThe model is commonly represented by entity beans. The view may be represented by a Java Server Page. Alternatively, the code to generate the view may be part of a servlet. The controller in a Java EE application may be represented by a servlet.
model view controller architecture application design pattern jee reference
-
09 May 08
-
08 May 08
-
17 Apr 08
-
04 Apr 08
-
28 Mar 08
-
15 Feb 08
-
09 Feb 08
-
06 Feb 08
Mike KossExplanation of the Model-View-Controller architectural pattern. Some intereresting links from here to different frameworks that implement MVC - including a couple of JavaScript frameworkI have not heard of: Archetype (French?), and JavaScript MVC. I tho
-
02 Feb 08
-
01 Feb 08
-
- Web Client Software Factory
- Maverick.NET
- Microsoft UIP
- Monorail An ActionPack inspired MVC framework from the Castle Project
- Igloo software (Experimental) MVC Framework for .Net 2.0
- ASP.NET 3.5 Extensions Community Technology Preview
- Scott Guthrie about the new MVC features in Asp.net 3.5
.NET
-
-
17 Dec 07
-
08 Dec 07
-
01 Dec 07
-
27 Nov 07
Chris JoblingArticle on Wikipedia, the free encyclopedia
-
26 Nov 07
-
19 Nov 07
-
In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface will not affect data handling, and that the data can be reorganized without changing the user interface.
-
It is common to split an application into separate layers: presentation (UI), domain logic, and data access. In MVC the presentation layer is further separated into view and controller. MVC encompasses more of the architecture of an application than is typical for a design pattern.
-
- The domain-specific representation of the information that the application operates. Domain logic adds meaning to raw data (e.g., calculating whether today is the user's birthday, or the totals, taxes, and shipping charges for shopping cart items).
- Many applications use a persistent storage mechanism (such as a database) to store data. MVC does not specifically mention the data access layer because it is understood to be underneath or encapsulated by the Model.
-
MVC is often seen in web applications, where the view is the actual HTML page, and the controller is the code that gathers dynamic data and generates the content within the HTML. Finally, the model is represented by the actual content, usually stored in a database or XML files.
-
-
17 Nov 07
-
08 Nov 07
konstantinidouConcept of Model-view-controller programming pattern
-
02 Nov 07
-
17 Oct 07
-
It is common to split an application into separate layers: presentation (UI), domain logic, and data access.
-
In MVC the presentation layer is further separated into view and controller. MVC encompasses more of the architecture of an application than is typical for a design pattern.
-
-
27 Sep 07
-
25 Sep 07
-
23 Sep 07
-
20 Aug 07
-
13 Jul 07
-
12 Jul 07
-
21 Jun 07
Andrew WhiteModel-view-controller (MVC) is an architectural pattern used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, s
-
08 Jun 07
-
07 May 07
-
25 Apr 07
-
begins
-
-
10 Apr 07
-
30 Mar 07
-
21 Mar 07
-
02 Mar 07
-
21 Feb 07
-
08 Feb 07
rabidgadflyIt is common to split an application into separate layers: presentation (UI), domain, and data access. In MVC the presentation layer is further separated into View and Controller. MVC encompasses more of the architecture of an application than is typical
-
02 Feb 07
-
25 Jan 07
-
20 Nov 06
-
18 Nov 06
-
13 Nov 06
-
24 Oct 06
-
28 Sep 06
-
16 Aug 06
-
07 Aug 06
Page Comments
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.