Re: Should a GUI be separated from the application?

[Stephen Leake <stephen_leake@stephe-leake.org>]

"Lucretia" <lucretia9@lycos.co.uk> writes:

> When developing an application it is *mostly* combined with the GUI, a
> lot of toolkits do this. You would extend a UI tagged-type (or class,
> or whatever your language uses) and include the code inside the new
> tagged-type, an example would be a toolkit which provides event handler
> callbacks via primitive types (a la CLAW) thus forcing you to include
> your application code into the new derived type.
>
> Is this the best thing to do? 

The users have the option of making the "application code" in the GUI
framework just communicate with the real application, via rendezvous,
sockets or whatever.

> Should I give the users the option?

What other design would you offer?

-- 
-- Stephe