The “Build your own CAB” series has enjoyed a very warm reception and I thank you all for the compliments I’ve received over the last couple weeks. Before I go on much farther with the series, I want to open the “story” prioritization up to you all to make sure we talk about the things you care most about before I run out of steam on this one. I’m finishing up the Passive View pattern right after this, but after that I’ll leave it up to you.
Here are the topics I have in mind:
- Assigning responsibilities to the Model View Presenter triad
- Patterns of View/Controller communication
- Presentation Model – a different take on Humble View’s
- Synchronization issues with the backend
- What are the options for the Model? (short)
- Using the Notification Pattern. Performing input validation in the Domain Model and connecting these errors to the screen elements
- Pluggability — tricks and examples for wiring together UI components with StructureMap
- Event Aggregator — coordinating events to disparate screen elements in a loosely coupled manner
- Subcutaneous Testing
- MicroController, a recipe for better screen element synchronization. I’ve written a partial replacement for data binding that bakes in declarative screen element behavior and testability
- Building an Application Shell — I’ve got 3-4 different examples of building an ApplicationShell/ApplicationController to handle navigation and screen coordination
- Driving WinForms through Fitnesse/StoryTeller tests. What’s worked for me, and what’s bombed.
- Applying NUnitForms (I’m an admin on NUnitForms, and it never gets the attention it deserves)
If you’ve got a preference, just let me know.