Re: [OT] Best way to isolate a GUI? (The final concensous?)

["Marin David Condic" <mcondic.auntie.spam@acm.org>]

Well, if you use an existing GUI such as Windows or Motif, you are *going*
to have callbacks. I'd prefer to isolate them in some kind of wrapper layer
and have the "real" app receive messages of some sort. If you were building
a GUI from bottom dead center, you could build that sort of thing right in.
I'm just saying I think that callbacks are an ugly kludge that I'd prefer
were done a different way. You might be able to get there with existing GUIs
& glue or wrappers or skins or whatever you like to call it. Just expressing
a desire to see an interface to a GUI that doesn't have to know anything
about the code *I* write. :-)

MDC
--
======================================================================
Marin David Condic
I work for: http://www.belcan.com/
My project is: http://www.jsf.mil/

Send Replies To: m c o n d i c @ a c m . o r g

    "Going cold turkey isn't as delicious as it sounds."
        -- H. Simpson
======================================================================

Warren W. Gay VE3WWG <ve3wwg@cogeco.ca> wrote in message
news:3E55501D.9050006@cogeco.ca...
>
> I was thinking of the requirements of the OP query, about
> the isolation factor. Perhaps this has already been stated, but the
> task & entry idea is not a bad one if you use the callbacks do
> the rendezvous with the task. The callbacks handle the dynamic
> linkage between the GUI and the task (callbacks = glue or wiring).
> This is perhaps what you've been saying all along..
>