From: John <john_ludlow@...>
Date: 2006-04-08T00:04:29+09:00
Subject: Re: Separation of gui from "real work"

> The original post was a pretty general question.  MVC is certainly
> one approach
> but it still embeds the 'real work' in the GUI application albeit via
> a nice
> internal structure.

Yeah, my post was intended to suggest a way he could seperate the

> Another thought is that the 'real work' is done via some sort of a
> server
> application with an API that is accessed from clients via inter-process
> communication of some sort.  Think of the separation of functionality
> between a mail reader application and the back end mailbox server via
> IMAP or POP.

I disagree - a client may do some 'real work', and a server may have a 
certain level of GUI (such as config and administration stuff).  And 
even if it's not like that, client-server is not appropriate in every 
situation - often I want an app that just runs locally.

Take my music manager example - do I really need a server application to 
store my song data?  When I want to add a song, should I really need to 
start the server and then the client just to do that?  I don't think so.

So a lot of apps (the majority, IMHO) could just be simple little things 
that run on my PC whenever I need them.  In that case, how do I seperate 
the GUI from the server?  Well, you need an internal structure that does 
that.

Stephen, do you want to seperate your GUI into a completely seperate 
application, or just a different module in the same application?

-- 
Posted via http://www.ruby-forum.com/.