From: Tom Sawyer <transami@...>
Date: 2002-07-25T05:26:38+09:00
Subject: Re: GUI's and the Rouge, Part III (yes, finally) 1/2

On Wed, 2002-07-24 at 12:07, Massimiliano Mirra wrote:
> Tom is not talking about bolting a GUI onto an *application*, he's
> talking about bolting a GUI onto a *model*, i.e. a set of classes that
> describe program logic and are ignorant of user interfaces.

hi Massimiliano,

i've just finished reading up on MVC. but i'm little puzzeled about how
the paradigm i have created maps to this pattern. let me explain. i take
the Model to be the back-end application. In my example case that would
the Fruity Fun App. It is the application, indifferent to any user
interface. then the Viewer is the GUI engine? --that which renders the
GUI? In my example that dosen't really yet exist, and at best could be
said to be STDOUT. am i right about this? but then the Controller, it
would seem, is the same entity as the GUI engine which also handles the
user interaction. i'm a bit confused on that point. what i am calling a
model in my GUtopia API is the code to generate the UI, perhaps then it
is really a View? but my model/View is also fully absatracted and knows
nothing about the Model/application for which it will describe the UI.
the two only relate via an intermidiary description called the binding.
so how does that fit into the MVC picture? i hanker this guess: the
underlying engine is irrelevent, the Model is my application, the View
is what i am calling a model (its a model of the UI) and the bindings
are the Controller. would that be correct?

by the way, thanks for the support.

~transami


~transami