loosely assimilated events wpf but controlling prism


i'm operative wpf concentration controlling model-view-viewmodel pattern.



the concentration consists twin modules during moment:




  • left quarrel crop tree name node

  • main quarrel arrangement calm comparison tree node.



i wish keep twin modules seperated, nonetheless i name node left quarrel i need glow an eventuality sure quarrel allow to. i don't wish integrate left sure panel, i don't wish share instances viewmodel classes.



optimally i adore prism (wpf multiple concentration guidance), nonetheless i'm now fluctuating an existent concentration can't broach some-more dependencies. digest also .net 3.0 (not 3.5), i have modify prism behind .net 3.0 combined .net 3.5.



in prism i solve controlling loosely assimilated eventing infrastructure. allows glow an eventuality any category any layer, listen any eventuality any category any layer. fundamentally publisher subscriber eventuality decoupled.



i commands grasp messy coupling between perspective viewmodel, nonetheless i'm certain repremand cross-view communication.



any tips suggestions severely appreciated.



i'm personally looking really light import pub/sub eventuality denote .net 2.0/3.0 (no linq stuff), thing else exercise querulous perspective (module) communication but coupling twin modules.



update: i finished adult clarify identical feeling glen suggests. i have removed eventservice (i commandproxy), pass each viewmodel by constructors use locator (at impulse i'm controlling use locator instead ioc-container). commandproxy exposes set multidelegatecommants, an progression delegatecommand prism (composite wpf guidance). fundamentally allows commands decoupled visible tree, supports churned subscribers.



Comments

Popular posts from this blog

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?

grails record upload problems

how i emanate permitted url asp.net mvc?