Design rules - Model View Presenter [ MVP ]

Vsebina je povzeta iz Blog-a { http://kjellsj.blogspot.com/search/label/CAB }
Točke so zelo konkretne/uporabne.
Sem mnenja, da se jih moramo do neke mere držati in upoštevati pri našem delu.


1. All views should have a XxxView suffix: TaskView/ITaskView

2. All presenters should have a XxxPresenter suffix: TaskViewPresenter

3. Let the presenter do all use-case processing, but keep GUI control details in the view

4. All presenter methods called by the view must start with OnXxx() as they are events by design (MVP)

5. Calls from the view to the presenter should be kept at an absolute minimum, and used for "event" type calls only: _presenter.OnViewReady();

6. It is FORBIDDEN to use the presenter reference to access the model or services directly, no return values from presenter methods

7. Calls from the presenter to the view MUST go via the interface only

8. No methods in the view shall be public unless they are defined in the interface

9. It is FORBIDDEN to access the view from anywhere but the presenter, except for loading and showing the view from the CAB ModuleController

10. The interface methods shall have long meaningful names (not "SetDataSource") based on the domain language of the use-case

11. The interface should contain methods only, no properties - afterall the presenter drives the use-case by calling methods, not by setting data

12. All data in the MVP component should be kept in the model, no data should exist only as properties of UI controls

13. The methods of the view interface should not contain UI control name references (e.g. AddExplorerBarGroup) as this makes the presenter know too much about the implementation technology of the view

14. Stick with domain naming in the view methods (e.g. AddTaskGroupHeader), this makes the code easier to understand and the tests self-describing