Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!ames!ncar!ico!auto-trol!marbru
From: marbru@auto-trol.UUCP (Martin Brunecky)
Newsgroups: comp.windows.x
Subject: Re: Xlib graphics within widgets
Message-ID: <339@auto-trol.UUCP>
Date: 28 Oct 89 01:45:11 GMT
References: <5666@shlump.nac.dec.com> <8910262037.AA16779@expo.lcs.mit.edu>
Reply-To: ncar!ico!auto-trol!marbru (Martin Brunecky)
Organization: Auto-trol Technology, Denver
Lines: 22

In article <8910262037.AA16779@expo.lcs.mit.edu> kit@EXPO.LCS.MIT.EDU (Chris D. Peterson) writes:
>
>>> A better, better solution is to write your own widget to do the job.
>
>> I aggree it is not difficult to create a widget, but since in most
>> widget toolkits exist allready
>> the drawing widget (DEC : window , MOTIF : drawing_area, ...) ... why
>> re-invent the wheel ?

Just an opinion... There are some other things you would like to do with
a "graphics" widget, such as input processing etc., which are not quite
supported by the widgets above. Or, to provide full symetry between windows
and pixelmaps. Or ... 
However, writing a "universal" graphics widget is close to impossible.
We have done the "minimum" job to satisfy our most obvious needs, and
eneded up with three widget classes plus two object classes. Not quite
what I'd call simple widget.
-- 
###############################################################################
Martin Brunecky, Auto-trol Technology Corporation,
12500 North Washington Street, Denver, CO-80241-2404
(303) 252-2499                                        ncar!ico!auto-trol!marbru