MVP pattern in AppraiserWorkbench reference app

Topics: CAB & Smart Client Software Factory
Oct 30, 2006 at 11:05 PM
originally posted by: dbalsdon

Please don't go for the jugular if this is a stupid question, as I am a newcomer to patterns and practices and running like hell to try and catch up with recent best practices.

In Appraiser workbench, why does the view have an instance of its presenter? I have been basing my recent projects implementation of MVP on the example here:
http://benreichelt.net/blog/2005/11/18/Learning-the-Model-View-Presenter-Pattern/

In that example the presenter drives the view completely, and I would have thought that made the presenter much more independent and re-usable with quite diverse views.

For my current project I need to create a standalone winform app, but then need to re-use much of the components in VSTO. I want as much code re-use as possible, and would appreciate a simple explanation of why the reference app is coded how it is.