Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!shlump.nac.dec.com!shodha.dec.com!elvira!ridder
From: ridder@elvira.enet.dec.com (Hans Ridder)
Newsgroups: comp.sys.amiga
Subject: Re: Request for X11 info
Message-ID: <677@shodha.dec.com>
Date: 1 Feb 90 14:50:38 GMT
References: <9737@baldrick.udel.EDU>
Sender: news@shodha.dec.com
Organization: Digital Equipment Corporation, Customer Support Center
Lines: 21

In article <9737@baldrick.udel.EDU> leightonr%scivx1.decnet@afal-edwards.af.mil (SCIVX1::LEIGHTONR) writes:
>The local clients are huge. For example Xlogo is 260K (and all this
>program does is display an 'X' on the X-Windows display).  Can anyone
>explain why this is the case????  I find it very distressing when a
>clock program (Xclock 271K) is bigger than DPaint III.

I'm not really up to speed on X, and I don't know how the Amiga
implementation is put together.  My understanding of the problem is
that all X applications wind up loading all or most of the X library
during linking.  I understand that this is because the highly
configurable user interface doen't know which routines it will need
until *run time*.  Thus, all "widget" routines are needed in each
executable, making them quite large.
Perhaps it would be possible to turn most or of the X library
(toolkit, whatever) into an Amiga sharable Exec library??!!??

-hans
========================================================================
  Hans-Gabriel Ridder			Digital Equipment Corporation
  ridder@elvira.enet.dec.com		Customer Support Center
  ...decwrl!elvira.enet!ridder		Colorado Springs, CO