David Hovey wrote:
how to relate it to my program is difficult
In the beginning it is, but don't worry. When you get over the 'new concepts' and 'ideology that changes everything' part you actually discover that it's no rocket sience. Just a new three (or four) letter abbreviation to a very simple and logical thing. I think there are several good articles about MVC at this site, have a look at them, for example: Building an MVP Framework for .NET. Part 1: The Basics of MVC and MVP[^]
David Hovey wrote:
each View should have one Controller
That's the basic idea but in some implementations one controller can have several views.
David Hovey wrote:
This sure does require alot more planning that the way I was going about it
It does, but you don't have to use Visual Studio or Rational Rose etc. In the simplest form it's basic OOP principles and what code do you write and where. So actually what I typically use is pencil and paper. Well, lots of paper because the first versions always go to the garbage pin :)
David Hovey wrote:
It will take more time
It will in this project, but you also learn a lot. That's an investment!
The need to optimize rises from a bad design.My articles[^]