Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't see a problem - user control is nothing but a view. And a presenter can interact with multiple views at a time. So in this case, your presenter can have reference of say 4 views (one for page, two for user controls and last one for sub-user control).</p> <p>Alternatively, you want to have single view per presenter and in such case, you can see user control as child view of the parent view(page) and so parent view need to bubble up and down view interactions meant for presenter. However, I would prefer the earlier approach where presenter handling interaction multiple views.</p> <p>See this related question on SO on how wiring is done: <a href="https://softwareengineering.stackexchange.com/questions/60774/model-view-presenter-implementation-thoughts">https://softwareengineering.stackexchange.com/questions/60774/model-view-presenter-implementation-thoughts</a></p> <p>Finally, you may want to look at MVVM pattern which I believe works great for compositional UI. Instead of presenter, you will have view model that will control the interaction between view and model - however, unlike presenter, view model does not know about view - rather view observes (and updates) view model to render itself. See this article here (View Model is referred as Presentation Model): <a href="http://www.codeproject.com/Articles/23340/Presentation-Model-in-Action" rel="nofollow noreferrer">http://www.codeproject.com/Articles/23340/Presentation-Model-in-Action</a></p> <p><strong>EDIT</strong>:</p> <p>To be honest, I don't prefer any of your approaches. I like MVP implementation where presenter holds reference to view via interface (no tight coupling) and view does the wiring i.e. creates presenter instance and inject the view references. The presenter listens to view events and call methods on view. View never calls directly on presenter's methods. (Other variations of MVP are possible - see the SO answer that I had sought). With this, I will explain two approaches that I had explained earlier.</p> <p><strong>Approach 1</strong>:</p> <p>Each user control is an independent view. There will be common presenter that will handle multiple views. For example,</p> <pre><code>public class Presenter1 { IView1 _view1; IView2 _view2; public Presenter1(IView1 view1, IView2 view2) { _view1 = view1; _view2 = view2; _view1.OnSave += OnSave; _view1.OnSomeEvent += OnSomeEvent; _view2.OnFoo += OnFoo; } public void OnSave() { var data1 = _view1.GetData(); var data2 = _view2.GetData(); // update model ... } public void OnSomeEvent() { // inform view2 about it _view2.DoOnSomeEvent(); } ... } public partial class MyPage : Page, IView1 { public void Page_Load(...) { //do wire up _presenter = new Presenter(this, usercontrol1); } ... } </code></pre> <p>Basic idea is that view does not do cross talk. If user control needs to inform page some thing, it would raise an event that is caught by presenter and it informs page about it. Views are passive and handles UI.</p> <p><strong>Approach 2:</strong></p> <p>Usercontrol and Page interacts. In such case, Page will act as a ultimate view and Presenter will hold reference to it. Control's events will be handled by page and page will bubble up the event if necessary. For example,</p> <pre><code>IView1 : IView2 { } public class Presenter1 { IView1 _view1; public Presenter1(IView1 view1) { _view1 = view1; _view1.OnSave += OnSave; _view1.OnSomeEvent += OnSomeEvent; _view1.OnFoo += OnFoo; } ... } public partial class MyPage : Page, IView1 { public void Page_Load(...) { //do wire up _presenter = new Presenter(this); // handle user control events UserControl1.Foo += UserControl1_OnFoo(); UserControl1.XyzEvent += UserControl1_XyzEvent(); } ... private void UserControl1_OnFoo(...) { // bubble up to presenter OnFoo(..) } private void UserControl1_XyzEvent(...) { // private interaction (purely about some UI manipulation), // will not be bubble up to presenter ... } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POASP.NET MVP Pattern
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USVinayC
    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
    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. COI know how MVVM works but I'm using MVP here. As said I also know how MVP works, I'm just abit confused about how to connect different usercontrols with each other. Thank you for your answer, but it does not realy answer what I am looking for. I'm not looking for how to set up MVP, but how to work with multiple user controls using MVP and their interaction. (events of child UserControls etc) If I would use 1 view/1presenter per usercontrol, how do I work with the child usercontrol? Do I initialize the child control his presenter inside the parent's presenter?
      singulars
      1. PO
      1. USFrederik Prijck
    2. COAnd then eventually, how do I communicate from the child back to the parent... Without MVP I'd do this using events in the CodeBehind file. But is this still the same when working with MVP? I'll change my post to be more clear
      singulars
      1. PO
      1. USFrederik Prijck
    3. CO@FrederikPrijck, see my edit to understand what I am suggesting.
      singulars
      1. PO
      1. USVinayC
 

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