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

let me paint a picture:

you have this super application you wrote --the underbelly of an
factastic hoogy-me-whatsy-do-it-all app and now you have to figure out
how to put a front-end on her. so you need a gui. hmmm...you think, i
want a gui thats flexible and fast nad highly functional, runs on just
about any platform, looks good, preferably just like the native
interface, and is easy as pie to code so as not to require much fussing
with the app you've alredy written. 

well, if you look around you're going to discover that everything out
there now has shortcomings. beleive me i've looked. so what do you do?
you either pick one that minimizes the shortcomings as suited to your
application, or you do what i'm trying to do: put an end to the problem.
how does that bode for what i'm trying to achieve?

as for plain old Model-View-Controller, honestly, i have no idea what
that even means. i just did what seemed natural. perhpas MVC is just the
right way to go?

~transasmi



On Tue, 2002-07-23 at 19:13, Albert Wagner wrote:
> Still looks like plain old Model-View-Controller to me.  You've split the 
> controller into client and server parts.  What is the purpose of separation 
> into different processes?  I don't mean to sound critical.  I really don't 
> understand what you are trying to achieve.
> 
-- 
~transami