Databases
StackOverflow2013
Postsdbo
POLightweight View Models For WPF
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POLightweight View Models For WPF
    primarykey
    data
    text
    <p>I understand MVVM's usefulness in the context of a large team developing a shrink-wrapped application over a long period of time. But in the context of an internal LOB application, MVVM seems overkill and I'm having trouble swallowing the overhead of debugging declaritive databindings, jumping from layer to layer to layer, and extracting VM's that are barely more than the Model with a command or two. Even accepting that overhead, still leaves me with the holes in MVVM like dialogs. A few things I've considered is:</p> <ul> <li>Binding directly to the Model and do old-school event handlers for form interaction</li> <li>Binding a user control or window to itself, effectively using the code behind as the VM.</li> <li>Include a property in my VM to reference the related view.</li> <li>Make ViewModel's subclasses of a View.</li> </ul> <p>The above items and their combinations address some problems but not all. I do realize that I might sacrifice testability. What other technical (not conceptual like SOC) issues will I run into using one or more of these practices?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USb_levitt
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POLightweight View Models For WPF
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POLightweight View Models For WPF
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhile there are benefits like separation of concerns and code re-use that you get when using MVVM, keep in mind that MVVM is primarily about being able to test your business logic separate from the actual view. If unit testing of your application is important to the project, then MVVM is a good choice and probably worth the associated 'overhead'.
      singulars
      1. POLightweight View Models For WPF
      1. USOppositional
    2. COI disagree. View Models should not have business logic, they contain the logic associated to the ui. Our business logic/model layer IS unit tested. But the costs associated with publishing in a typical shrink wrapped or commercial product barely exist in an internal LOB application, so we beleive there is little point to unit test the UI, which puts us in this place of also wondering the usefullness of MVVM in it's purest form.
      singulars
      1. POLightweight View Models For WPF
      1. USb_levitt
    3. COI disagree, ViewModels should never contain UI logic. Anything related to the UI such as setting focus or running animations should be done in the code behind. The ViewModels should contain Business Logic such as Loading/Saving data, and they should control application flow such as changing what ViewModel is the currently active screen, or returning error messages. Your ViewModels ARE your application, while the Views are just a pretty UI that allows users to interact with the ViewModels easily.
      singulars
      1. POLightweight View Models For WPF
      1. USRachel
 

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