🚀 go-pugleaf

In article <9207221426.AA15901@public.BTR.COM>, eeh@btr.com (Eduardo E. Horvath  eeh@btr.com) writes:
|> 
|> 
|> 	Are InterViews 3.1 and Unidraw compatible?
|> 
|> 	I have been trying to create a small application that uses
|> Session and Kits along with an Editor and unidraw objects I build one
|> piece at a time, but all I get are core dumps.
|> 
|> 	What needs to be done to use Unidraw under 3.1?  Do you create
|> a Unidraw object or a Session?  Can a Catalog survive without Unidraw?
|> Is it necessary to create your own set of primitive glyphs ("Figures") ?
|> 

I have done this. I create a Unidraw object and use the Unidraw event
loop to drive the application.  You can quit using unidraw::quit or
Session::quit.  You can create an Editor and pop it up using unidraw::open.
I have defined the appearance of one editor using widgets from WidgetKit,
and another using unidraw (2.6-based) objects like Viewer.  I have not yet
tried combining 3.1 and 2.6 objects in the same editor -- but as long as
you stick to one or the other I know it works. You can, though, have an
editor that is defined by a composition of unidraw (2.6) objects pop up
a dialog that is made of widgets (a subclass of Dialog, like that of
DialogKit::file_chooser).

===========================================================================
Doron Shalmon                 Internet    doron@yogi.leis.bellcore.com
444 Hoes Lane (RRC 4B-1125)   CompuServe  72330,3307
Piscataway, NJ 08854          VOICE       (908) 699-8133
                              FAX         (908) 336-2982
 _   _        _  _   _   _    
|_> |_ |  |  |  | | |_> |_    "All opinions expressed are mine, and do not
|_> |_ |_ |_ |_ |_| | \ |_     necessarily represent those of my employer,
                                Bell Communications Research (Bellcore)"
Bell Communications Research