> {quote:title=John Treder wrote:}{quote}
>
> Well, I decided to bellyflop into that ocean, and I'm dog-paddling around, and I seem to get that the general idea is to separate UI elements, storage elements, and "business" elements.
I don't think there is any storage concerns in MVC. Here's a good article to read:
http://en.wikipedia.org/wiki/Model-view-controller
> But there does seem to be a lot of "glue" code involved in getting standard Dephi Ui components, home-brewed "business" classes, and a mixture of SQL database components and .INI files to chat comfortably with one another.
Yep, stacks of glue bottles on your workspace.
> {quote:title=Joanna Carter (Team OOAD) wrote:}{quote}
>
> If I can create an MVP framework that works at both design-time and
> run-time, using C#, I see no reason why it would not work in Delphi.
I was thinking more of doing MVC visually with Delphi. Are you viewing MVP as being closer to the Delphi approach?
> {quote:title=Joanna Carter (Team OOAD) wrote:}{quote}
>
> Both are equally possible in Delphi: given that you would have to create
> any necessary components and their designers.
I'm liking the idea. It sounds fun.
> {quote:title=Gilbert Padilla wrote:}{quote}
> > Both are equally possible in Delphi: given that you would have to create
> > any necessary components and their designers.
> >
>
> Could livebinding be part of a Visual MVC?
Yes. I already do a half-baked MVC visually with Delphi. I've labeled it Delphi-MVC.
Joanna is an xtreme typist so she's good for an MVC/MVP discussion.
> {quote:title=Joanna Carter (Team OOAD) wrote:}{quote}
>
> In theory, MVC would not use bindings since the Controller encompasses
> mediating a UI to a whole object rather than separating out the
> interaction of individual properties to controls, as in MVP.
So, you're saying a live binding to a whole object wouldn't be allowed under MVC?