Mar 6, 2008 at 7:05 PM
Edited Mar 7, 2008 at 9:19 AM
Currently use CAB+SCSFContrib WPF port as a basis for a WPF composite application.
The paradigm we use: (an altered version of SCSF MVP)
A) AbstractPresenter<TView> inherits from DependencyObject
B) Services are exposed as DependencyProperties of the Presenter (They are offcourse injected to the presenter by CAB)
C) Abstract presenter sets itself as the datacontext of its view
D) View widgets bind to properties exposed by the services exposed by the presenter (the presenter is the data context...)
We found that because our view binds to data this way and use ICommand.CanExecute there is almost nothing in most of our IViews (i.e the interfaces which hide the view implementation from the presenter).
What is the paradigm for Prism?