Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!van-bc!jtc
From: jtc@van-bc.UUCP (J.T. Conklin)
Newsgroups: comp.windows.x
Subject: Re: Using the X Resource Manager in Non-X Applications
Keywords: resource manager
Message-ID: <229@van-bc.UUCP>
Date: 6 Mar 90 16:23:24 GMT
References: <207@van-bc.UUCP< <6337@orca.wv.tek.com<
Reply-To: jtc@van-bc.UUCP (J.T. Conklin)
Organization: Wimsey Associates
Lines: 26

In article <6337@orca.wv.tek.com< glennw@crevasse.WV.TEK.COM (Glenn Widener) writes:
|> My thoughts are that I could write a set of wrapper functions that
|> clean up the interface to the RM (perhaps like is done in Xt?) and
|> use that.
|
|> Should I do that, or should I be looking at a different approach?
|
|I take it that you are asking for a simple XGetDefault-like interface to
|the Xlib Xrm facility, that uses Xt-like database initialization, for
|non-Xt Xlib clients.

You have the right idea, but in my case the only reason the application
is linking Xlib is for the resource manager routines.

|My belief is that such a facility in Xlib is long
|overdue, and I will be proposing it for R5.  In the meantime, I'd
|recommend that you steal the Xt XtInitialize code and remove all the
|widget-isms (which is basically what I will propose for Xlib.)

I have started to do this.  When I'm done, I should have a "resource
manager" library totally separate from X.

	--jtc
-- 
J.T. Conklin
	...!{uunet,ubc-cs}!van-bc!jtc, jtc@wimsey.bc.ca