Re: Should a GUI be separated from the application?

[tmoran@acm.org]

> 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.
   Agreed.  It depends on the complexity and the timing requirements.
If the response to a human-caused event can be done in a fraction of a
second, the code might be included in the GUI event handler, while
responses that take a long time should be separate to avoid blocking other
events.  If the complexity of communication is low - updating a percent
complete display for example - then it's easy to separate app and GUI code
and communicate with something simple like a protected object.  If the
communication is very complex, your user may find even rendezvous
difficult and want to put the app code inside the event handler. One
size doesn't fit all.