<< HTML Help Attribute Extender | Printing and Previewing Web Page using Link Tag >>

My Model View Presenter Experience

by Rod 4/7/2008 12:50:00 AM

Currently I'm working with laser guidance system where we create a Desktop and Mobile version of the application. On the initial requirement the simulator module only required for desktop version. Lately, our client requires us to create a Mobile version of the simulator that way they can simulate using mobile device using different mobile supported ports like bluetooth and other available ports. since I design the simulator in Model View Presenter pattern this is just a piece of cake.

All I have to worry is the UI since mobile application don't have enough space for UI controls so I have to split the UI into pieces.

If I design the MVP layer that is tied up to UI say I added UI reference in my MVP layer I'll probably do a lot of recoding and redesigning. Though mobile application can reuse desktop code but there are several windows forms control that .NET CE does not support.

Cheers!

Rod

Currently rated 5.0 by 1 people

Currently 5/5 Stars.
1
2
3
4
5

Tags:

MVP | My Experience

Model View Presenter Part I – Building it from Scratch Model View Presenter from scratch. Mock testing. Model View Presenter Part II - Unit TestingPrinting and Previewing Web Page using Link TagLink tag and Print preview

Comments

3/23/2009 8:36:25 PM

thanks for sharing your wonderful idea.,,i learn something new

Gadgets in Future

5/28/2009 7:06:27 AM

Why is that you are very much worry is the UI?

thatcom

5/31/2009 10:52:16 AM

UI is the most variable part of the application and there are a lot ways to represent the user interface to the user - Web, Forms, Mobile, WPF, etc... If your business logic and codes is highly dependent to the UI any changes to UI will affect your application or worse domino effect.

Analogy:
If you have a form that saves employee information it can be represented by different interface (Web, mobile, windows forms, etc) but the underlying logic that saves the data to the database are all the same. In MVP your presenter acts as a controller and uses the view interface to communicate with the UI that abstracted the UI platform from the business logic.

Rod