Re: Widget Names (was: State, Attributes and Some basic widgets)
If you want code to work on all toolkits, you have to provide it. It would also be necessary if we wanted to implement some of Xt's features (e.g. customisation through external files, e.g. for I18N) for other toolkits.
Hmm... Could you point me to an overview of what that X resource stuff really does and how it really works?
This also simplifies coding. The UI creation code doesn't need to store lots of handles for later reference; code can obtain the run-time handle using the widget's pathname.
I like storing my handles because I want compile-time safety.... but it wouldn't hurt if that feature was there. One more question: what about platform-specific interface definitions (e.g. nib files on Mac OS) that don't contain textual widget names? Cheers, Wolfgang
Wolfgang Thaller wrote:
If you want code to work on all toolkits, you have to provide it. It would also be necessary if we wanted to implement some of Xt's features (e.g. customisation through external files, e.g. for I18N) for other toolkits.
Hmm... Could you point me to an overview of what that X resource stuff really does and how it really works?
I don't have a specific URL handy; however, some useful URLs are:
Xlib documentation (PostScript):
ftp://ftp.x.org/pub/R6.6/xc/doc/hardcopy/X11/xlib.PS.gz
Xt documentation (PostScript):
ftp://ftp.x.org/pub/R6.6/xc/doc/hardcopy/Xt/intrinsics.PS.gz
Overview of X resources at the Xlib layer:
http://www.tronche.com/gui/x/xlib/resource-manager/
End-user customization of Xt applications:
http://koala.ilog.fr/jml/xres/xres.html
X11 manual pages:
http://www.xfree86.org/current/manindex3.html
Various X-related links:
http://www.rahul.net/kenton/xsites.html
Regarding the Xlib layer, all of the relevant functions begin with
"Xrm". However, you don't really need to use those functions unless
you're writing your own toolkit (i.e. Xt itself uses them, but
Xt-based widget sets and Xt-based applications generally don't).
Looking at some resource files (/usr/lib/X11/app-defaults or
/etc/X11/app-defaults) might help, as might playing with the "editres"
program.
--
Glynn Clements
participants (2)
-
Glynn Clements -
Wolfgang Thaller