Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!ucbvax!ics.com!david
From: david@ics.com (David B. Lewis)
Newsgroups: comp.windows.x.motif
Subject: re: optimization / speedups
Message-ID: <9008160059.AA04861@BU.EDU>
Date: 16 Aug 90 00:37:29 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 27

In article <1990Aug15.221852.5493@ics.com>, nazgul@alphalpha.com (Kee
Hinckley) writes:
|> In article <9007@uhccux.uhcc.Hawaii.Edu>
|> john@quonset.cfht.hawaii.edu (John Kerr) writes:
|> > 
|> >Are there any general hints for speeding up a Motif application? 
For
|> >instance, does eliminating the resource file and hard-coding the 
|> >resources make for faster startup and execution?  
|> 
|> I have heard that Frame ended up putting resources for each
|> dialog box and window in a separate file and loading them on
|> demand.  I'm not sure why they didn't just hard code them, but
|> my impression is that yes, resources can be costly for large
|> applications.

Most are wild-carded (e.g. all shadowThickness of all XmDialogShell is
1), 
so the total set of resources is not large.

Note that this wins for them when porting to other platforms.

--
David B. Lewis  david@ics.com  david%ics.UUCP@bu.edu 
...!uunet!ics.com!david

	"Then again, it could have been the little purple feet." -- Sun