From xemacs-m  Wed Mar 19 07:45:09 1997
Received: from ns1.eds.com (ns1.eds.com [192.85.154.78])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id HAA25615
	for <xemacs-beta@xemacs.org>; Wed, 19 Mar 1997 07:45:09 -0600 (CST)
Received: from nnsa.eds.com (nnsa.eds.com [130.174.31.78])
          by ns1.eds.com (8.8.5/8.8.4) with ESMTP
	  id IAA31890 for <xemacs-beta@xemacs.org>; Wed, 19 Mar 1997 08:45:09 -0500 (EST)
Received: from kocrsv04.delcoelect.com (kocrsv04.delcoelect.com [144.250.100.205])
	by nnsa.eds.com (8.8.5/8.8.5) with ESMTP id IAA26717
	for <xemacs-beta@xemacs.org>; Wed, 19 Mar 1997 08:44:38 -0500 (EST)
Received: from kocrsw12.delcoelect.com (kocrsw12.delcoelect.com [144.250.106.18]) by kocrsv04.delcoelect.com (8.7.5/8.7.3) with SMTP id IAA22567 for <xemacs-beta@xemacs.org>; Wed, 19 Mar 1997 08:44:37 -0500 (EST)
Received: from kocrsw12 by kocrsw12.delcoelect.com (SMI-8.6/SMI-SVR4)
	id IAA11160; Wed, 19 Mar 1997 08:44:36 -0500
X-Mailer: exmh version 2.0gamma 1/27/97
To: xemacs-beta@xemacs.org
Subject: Re: Subwindows 
X-Face: 4tk3bJx]I+QTZ|=]*1+Z){9+;5u_hK*NBeZK6[+B+iB%bVuOJ%^uK~fIG}O-}%WLX*D
 ^aW>Gv8E3Xtz0\N&fQl^:pj<K{xM`:d>pPt:9lF-YXB%O)?@rd?*/jE!s94`?]:jJ#C5RDP:;M
 r.3lwo`0{vIT+<{%IRwe]vLd]7>\X|*z{TUX_t;?TPcOLBMIv8_V92!Vk(*DJVU~0M[`5D^PAW
 LniO1?YYWArMU*j9o+>?1MWi.lO?F-?aVt:qQ8OaG?R}B:I!7S_+KuzxZ.f9M@$z#n\bG2$Q2{od
Date: Wed, 19 Mar 1997 08:44:35 -0500
Message-ID: <11158.858779075@kocrsw12>
From: Mike Scheidler <c23mts@eng.delcoelect.com>

"sb" == Steven L Baur <steve@miranova.com> writes:
 sb> 
 >> What is the intent of subwindows, and what is their status?
 sb> 
 sb> Maintainerless & broken.

Too bad.  After a little more nosing around, I found enough references and
comments to get a better idea of their purpose.  Here's a pretty concise
explanation of the subwindow object from internals.info-2:

     An object that encapsulate a "subwindow" resource, i.e. a
     window-system child window that is drawn into by an external
     process; this object should be integrated into the glyph system
     but isn't yet, and may change form when this is done.

This sounds like the perfect avenue for displaying in the Tk widgets,
either as an elisp-accessible library or running as a Tcl/Perl/Python/Scheme 
interpreter subprocess.

I also found reference to Chuck as the implementor of subwindows.  Chuck,
could you elaborate a little?  Looking at the glyph*.c code, it appears
that a lot of the rough-in work has been completed.  Did you run into
implementation problems, or did it just get put on the back burner?  Is it
time for this to be resurrected?

-- 
Mike Scheidler                     c23mts@eng.delcoelect.com
Corporate Software Technology
Delco Electronics Corporation      PHONE:  (765) 451-0319
Kokomo, IN 46904-9005              GMNET:  8-322-0319


