Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>People get too hung up on initials and <a href="http://en.wikipedia.org/wiki/Three-letter_acronym" rel="nofollow noreferrer">TLA</a>'s sometimes.</p> <p>If what Phil Haack says in his article is true, I thought I was using MVC in ASP.NET MVC, but what I am really using is MVP (or a tweaked form of MVC).</p> <blockquote> <p>With MVC, it’s always the controller’s responsibility to handle mouse and keyboard events. With MVP, GUI components themselves initially handle the user’s input, but delegate to the interpretation of that input to the presenter.</p> </blockquote> <p>But that's not what ASP.NET MVC is really all about.</p> <p>If I handle mouse and keyboard events, I like to do it in the browser with jQuery. That <em>separates the user interaction from the controller</em>, and provides for better decoupling between the UI layer and the "business" layer.</p> <p>If I need to update part of my page using an AJAX call or JSON call, I am still going to need to do that anyway, whether I call it MVC or MVP. </p> <blockquote> <p>ASP.NET WebForms, for example, attempts to emulate the rich client development paradigm via the use of ViewState. This is why many attempts to apply patterns to ASP.NET focus on the MVP pattern because the MVP pattern is more appropriate for a rich client application with GUI components. </p> <p>However, many web platforms embrace the stateless nature of the web and forego attempting to simulate a state-full rich client development environment. In such systems, a tweaked MVC pattern is more applicable.</p> </blockquote> <p>It is clear that Phil views (a tweaked form of) MVC as a move to a more stateless, thinner client, whereas MVP places more responsibility on the UI layer for providing a rich user experience.</p> <p>Whether this is a good thing or not is subjective. If ASP.NET is MVP and ASP.NET MVC is MVC, I'll gladly accept the MVC initials to give up things like viewstate and obtuse logic.</p>
    singulars
    1. This table or related slice is empty.
    1. POBenefits of MVC over MVP
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRobert Harvey
    1. USRobert Harvey
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COWhat if the whole reason you are trying to decide is, you want to use the some business layer for a web version and a thick client version ;-) aaak
      singulars
      1. PO
      1. USFastAl
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload