Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here's my opinion, for what it's worth :</p> <p>I don't really agree with the approach you suggest (except for the dumb view). In real life, you will often have to use an existing model : it could be legacy code that you don't have the time (or will) to change, or even a library for which you don't have the code. In my opinion, the model should be completely unaware of the way it will be displayed, and should be easily usable in a non-WPF application. So it doesn't have to implement any specific interface like <code>INotifyPropertyChanged</code> of <code>INotifyCollectionChanged</code> to make it usable in MVVM. I think that all the logic related to UI should reside in the ViewModel.</p> <p>Regarding <code>RoutedEvents</code> and <code>RoutedCommands</code>, they are not really suitable for use with the MVVM pattern. I usually try to use as little <code>RoutedEvents</code> as possible, and no <code>RoutedCommands</code> at all. Instead, my ViewModels expose <code>RelayCommand</code> properties that I bind to the UI in XAML (see <a href="http://msdn.microsoft.com/en-us/magazine/dd419663.aspx" rel="noreferrer">this article</a> by Josh Smith for details on <code>RelayCommand</code>). When I really need to handle events for some control, I use attached behaviors to map the events to ViewModel commands (have a look at <a href="http://marlongrech.wordpress.com/2008/12/13/attachedcommandbehavior-v2-aka-acb/" rel="noreferrer">Marlon Grech's implementation</a>)</p> <p>So, in summary :</p> <ul> <li>Dumb View</li> <li>Big and smart ViewModel</li> <li>Any model you want or have to use</li> </ul> <p>Of course it's just my approach, and it may not be the best, but I feel quite comfortable with it ;)</p>
    singulars
    1. This table or related slice is empty.
    1. POFat Models, skinny ViewModels and dumb Views, the best MVVM approach?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USNaser Asadi
    1. USThomas Levesque
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POFat Models, skinny ViewModels and dumb Views, the best MVVM approach?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COVery insightful, especially regarding the model, that you should be able to use the MVVM pattern to hook up to data classes from old projects which have no knowledge of WPF. Interesting the you think RoutedEvents and RoutedCommands are not really suitable for MVVM, I thought they were made to be used in decoupling patterns such as MVVM. Thanks for the feedback.
      singulars
      1. PO
      1. USEdward Tanguay
    2. COI refactored this example based on this feedback, put the logic up into the ViewModel: http://stackoverflow.com/questions/857820/big-smart-viewmodels-dumb-views-and-any-model-the-best-mvvm-approach
      singulars
      1. PO
      1. USEdward Tanguay
    3. COYou hit the point...
      singulars
      1. PO
      1. USMarc
 

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