Just a quick reminder. I will be speaking on the North American Virtual ALT.NET again this Wednesday night on Presentation Patterns. This time around I’m doing a *very* informal talk around topics related to Separated Presentation patterns:
- What’s the problem?
- Let’s enumerate the responsibilities in a view
- How do the various Separated Presentation patterns assign these responsibilities, and what’s the fundamental differences? Passive View vs. Supervising Controller vs. Presentation Model with a quick comparison to the Model 2 style MVC in the web world
- Flow Synchronization vs. Observer Synchronization (I’m thinking more and more that this is a very big design issue that isn’t getting talked about very much)
- Patterns of View and Presenter/Presentation Model communication
- What’s the Model? Dumb codegen’d objects, ViewModel’s wrapping a rich Domain Model, mobile objects, bind directly to a UI specific Domain Model, or *gasp,* using DataSet’s
Just so we’re clear, this is in support of the Presentation Patterns book that I’m authoring and I’m doing this mostly as a research/feedback activity on my part. I’d really appreciate any and all questions and feedback.
And as a bonus, if you bait me a little bit I’ll happily rant away on:
- Why I think the “Zero Code Behind” movement is silly, short sighted, and/or potentially harmless
- Whether or not the “ViewModel should not know about the View at all!” standpoint adds the slightest value to development (hint: no)
- How INotifyPropertyChanged, IDataErrorInfo, ISillyInterfaceToSupportRADProgramming crap makes UI development in .Net totally foul up in the Essence v. Ceremony ratio — and what to start doing about it
- Why I seriously think data binding is overrated and somewhat problematic
- Why I think the WPF community’s approach to MVVM needs to be questioned
- It’s a mistake to dogmatically apply Presentation Model when other patterns may be more suitable in certain scenarios (see point 4 above)
- Questioning the importance of “Blendability” on a typical LOB app
and finally, I may muse on whether XAML is the worst thing MS has rammed down our throats since WebForms…
The previous VAN session on the “Screen Activation Lifecycle” was recorded and available here. Double click the row to get the recording.