Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You could register a "lazy wrapper" instead. Such a wrapper implements the same interface and can be instantiated immediately, but will internally postpone the creation of the actual component that does the work. Take a look at ploeh's example of a <a href="http://blog.ploeh.dk/2010/01/20/RebuttalConstructorOverinjectionAntipattern.aspx" rel="nofollow">LazyOrderShipper</a> or <a href="http://blog.ploeh.dk/2010/01/20/EnablingDIForLazyComponents.aspx" rel="nofollow">LazyOrderShipper2</a>.</p> <p><strong>edit:</strong> If I understand correctly, you're just trying to connect your views to your viewmodels, MVVM-style. I prefer to let the container handle viewmodel construction, but to do the view construction and viewmodel wiring myself. My start-up code woul look like this:</p> <pre><code>var mainViewModel = container.Get&lt;MainViewModel&gt;(); var mainView = new MainView(mainViewModel); Application.Run(mainView); </code></pre> <p>And inside the <code>MainView</code> constructor I'd take care of child controls which require their own viewmodel:</p> <pre><code> public MainView(MainViewModel viewModel) { // link "subviews" to "subviewmodels" this.SomeChildControl.ViewModel = viewModel.SomeChildViewModel; // normal MVVM property wiring viewModel.TitleChanged += delegate { this.Text = viewModel.Title; }; ... } </code></pre> <p>If you strictly follow the MVVM approach, then you should not have to register any view with the container. Anything that "needs to talk to the view" really needs to talk to underlying viewmodel instead. (Things get more interesting when you want to allow for pluggable views in tabbed interface or docked window GUI, but that's another story.)</p>
    singulars
    1. This table or related slice is empty.
    1. PORegistration in IoC container after initial configuration
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USWim Coenen
    1. USWim Coenen
    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. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis is a very elegant solution. Yet my issue is not related to the cost of the component instantiation, but to the availability of some constructor arguments. Postponing the actual instantiation requires that at least the lazy wrapper knows how to retrieve the required arguments, when it finally comes the time of creating the instance. I should have explained my scenario in more details, maybe (which I'm going to do). Thanks for your help.
      singulars
      1. PO
      1. USMarco Amendola
    2. COSorry, but the question is not related to wiring between Views and VMs (which is is already in place). I just added the actual classes involved hoping to clarify the context. My will is to abstract the docking part and segregate its interface from ShellVM, for the exact purpose to allow dynamic addition. I would have liked to put the docking service in the container to simplify the dependency injection, but I can certainly access it from the ShellVM (which is already registered as a singleton in the container).
      singulars
      1. PO
      1. USMarco Amendola
 

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