About Presenter's Patterns

[Guest]

I'm starting a new project based on webservices as mediator for the clients
and the servers.
I must develop two presentation layers, one in winforms performing a smart
client application and another in webforms with much of the functionality in
the Winform version, incluinding a hardcopy of many forms design.
I'm looking for a pattern to develop this project and avoid (almost whole)
duplicated code between the two front-ends.
The popular MVP, in my point of view, is much more complex and "time loss"
than useful, especially in a two front-end project.
However, I don't know anothers patters to help in this situation.
I'm open to ideias.

 

[Guest]

Max,

I'll be interested in what shows up in this thread. Here are my $.02.

First, an assumption that I am making is the by "Smart Client" you mean
application that is based off of the .NET Compact Framework as opposed to
Microsoft's network aware "Smart Client." Second, I think it may be
beneficial to step back and look at the project from a higher level.

I've developed a similar application in the past and found that using a Test
Driven Development model helped me by allowing the Tests to become the first
presentation layer. The GUIs for the Compact Framework and Desktop Framework
were simple stubs without much code in them. Yes, there was a little bit of
work duplication in drawing the forms. However, this was offset by the fact
that I didn't want the desktop application limited by the size of the PDA
screen or the lack of some functionality in the limited Compact Framework
controls.

The next organizational item that helped was to share common source code
between the two projects. This was done by using Link File when adding the
file to the second project instead of copying it local. There were of course
problems with this in that I had to limit the functionality to the smallest
subset, but for my project it wasn't an issue. Conditional Statements can be
used to specify different functionality for the different platforms.

I think by making a few organizational changes you should be able to limit
the amount of duplication that happens.

Michael