c# - Should a Presenter in the Model-View-Presenter pattern handle multiple 'UI' elements on a View? -


i implementing diagram/flow-chart type designer using model-view-presenter (mvp) pattern in wpf.

i have though of pattern (and of others such passive view , mvvm) high level architectures fail address of complexity involved in rich uis (here come trolls).

in particular instance, have ui resembles following mockup:

enter image description here

i have made choice use presenter objects each element requires presentation logic on designer. has left me following designers far.

designerpresenter controlpresenter controloverlaypresenter connectionpresenter connectionpointpresenter overlaypresenter

the reason have implemented each of these because each of them needs handle presentation logic , communicate actions business/domain tier separately in order avoid bloat (imo).

the other way see doing if there 1 presenter handles presentation logic seems out of control quickly.

my question(s) follows:

  1. is common see presenter provided each ui element on screen such doing in order allow separation of presentation logic?
  2. some of presenters created logically child presenters (the controlpresenter child presenter of designerpresenter) normal?
  3. is in alignment pattern makes more sense?

i never used mvp i'm comfortable mvvm pattern , if replace word presenter viewmodel design fits do.

it normal designerpresenter has observablecollection of controlpresenter , controlpresenter contains observablecollection of connectionpresenter. connectionpresenter have 2 connectionpointpresenter well.

the overall design seems ok there other similar architectures fit too. imho maybe there separation. makes sense separate connection , connection points?


Comments

Popular posts from this blog

php - Submit Form Data without Reloading page -

linux - Rails running on virtual machine in Windows -

php - $params->set Array between square bracket -