Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!rutgers!banana!mips!smsc.sony.com!dce
From: dce@smsc.sony.com (David Elliott)
Newsgroups: comp.windows.x
Subject: Xt program resource files - How much is enough?
Message-ID: <1991Mar27.020710.22641@smsc.sony.com>
Date: 27 Mar 91 02:07:10 GMT
Sender: dce@smsc.sony.com (David Elliott)
Organization: Sony Microsystems Corp, San Jose, CA
Lines: 19

Somehow, I got this (strange?) idea that when one writes an Xt-based
application, one is supposed to put as much of the resource information
as possible in a resource file.

As a result, I write applications where the only calls to XtSetValues
are done when the resources have to be determined at run-time.  This
includes putting all of the Form and other constraint/composite widget
resources in an app-defaults file.

I believe that this gives my "customers" extra advantages.  For
example, if someone needs to find out the widget hierarchy, my
app-defaults file tells them this, and even shows them which resources
are being used to lay things out.  Within reason, they can even change
the layout of the program.  It also has the advantage that my
applications can be changed to support other (human) languages very
easily.

So, am I going overboard, or are application programmers that don't go
that extra mile just being lazy?