Xref: utzoo comp.graphics:2862 comp.windows.misc:616
Path: utzoo!attcan!uunet!husc6!rutgers!mcnc!rti!gjc
From: gjc@rti.UUCP (Greg Clary)
Newsgroups: comp.graphics,comp.windows.misc
Subject: Re: windowing system independent -- user interface toolkit
Message-ID: <2384@rti.UUCP>
Date: 26 Jul 88 13:58:21 GMT
References: <677@mv06.ecf.toronto.edu>
Reply-To: gjc@rti.UUCP (Greg Clary)
Organization: Research Triangle Institute, RTP, NC
Lines: 34

From: Greg Clary <gjc>
Message-Id: <8807252129.AA11897@rti.rti.org>
To: apollo@ecf.toronto.edu
Subject: Re: windowing system independent -- user interface toolkit
Newsgroups: comp.graphics,comp.windows.misc
In-Reply-To: <677@mv06.ecf.toronto.edu>
Organization: Research Triangle Institute, RTP, NC
Cc: 

In article <677@mv06.ecf.toronto.edu> you write:
>
>for those looking for a user-interface toolkit that
>is more or less independent of windowing system though
>X will be needed have a look at openDialogue from Apollo.
>hope this is of some help.
>                             vince pugliese
>                             apollo@ecf.toronto.edu
>.


Is openDialogue the same as Domain Dialogue?  

I am working on a project, and attempting to use Domain Dialogue, but I 
am finding it a bit inflexible.  I am attempting to write a more friendly
user-interface to the Display Manager and various tools on the system.
My initial goal is to implement a menu-system similar to the X Window
System's uwm.  (The menuing portion of uwm, that is).  In other words,
I want to have menus which are defined at run-time.  This is possible
with domain dialogue, but a bit messy.  I believe I need a set of routines
which are a lower level than domain dialogue, but a higher level than
the GPR routines.
) do you have any suggestions?
Thanks,
gjc@rti.rti.org