Re: [OT] Best way to isolate a GUI?

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

You could get it down to one task if you basically go to some kind of
message protocol. Build a wrapper around something like GtkAda that deals
with the callbacks, etc. That builds up messages that are queued for the
app. The app pulls them out of the queue as it is ready for them and queues
up responses for the GUI. That doesn't fix Motif & GtkAda from being a C-ish
thing, but it hides all the C-ishness in the wrapper. You'd also get a means
by which you could have a portable GUI interface by building a similar
wrapper around Claw or anything else that gets dreampt up.

In the perfect world where there is an ongoing Ada Operating System project,
this might be a great design for the interface to the GUI. Asynchronous
message traffic via any number of communication mechanisms.

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:3E5121BD.4010200@cogeco.ca...
>
> This sounds conceptually nice, but it could prove to have practical
> problems (I need to think about this more, myself). Thinking in terms
> of an X11/MOTIF application, where there can be hundreds of windows within
> windows to implement widgets on a form, this translates to hundreds
> (if not more) of tasks. This smells a lot like overkill upon first
> blush at least.
>