by mark
11. September 2010 08:50
I have the need to pick up the MVP pattern for my job, so that means a lot of the new HardwawreArmory features are going to be designed using that pattern.
I can only think of one task, currently, that will be "Hello World" easy and that will be the creation of new computers (and accessories) since it is mostly data->form->data and doesn't require too much fanciness.
The only challenge I see is that the IHardware interface that all of the Hardware components use as a contract are going not going to be easy to integrate as they don't really work as a View the way they are designed.
There are a few benefits to this pattern:
- Test Driven Development makes more sense. No code is written until I have created my tests. I could do this now, but it doesn't fit my current development flow.
- Seriously separated concerns. UI is nothing but UI (Model). View is nothing but functionality (View). And the Presenter is the object handed between the two (Presenter).
- I will learn this pattern which should be a good feeder into MCV (or just upgrading to a framework designed to assist MVP like Castle).
I think that I am going to start to put code snippets in here.
0f5cd6b3-0b09-4cad-be66-666272f926c1|0|.0
Tags:
code | General
Subscribe