Newsgroups: comp.windows.x.motif Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!ispd-newsserver!ism.isc.com!b1!ico!auto-trol!marbru From: marbru@auto-trol.com (Martin Brunecky) Subject: Re: UIL -> C converter Message-ID: <1991Jun17.171453.5775@auto-trol.com> Sender: news@auto-trol.com Nntp-Posting-Host: server_1-gw Organization: Auto-trol Technology Corporation References: <7061@bwdls58.bnr.ca> <1991Jun14.150955.25245@auto-trol.com> Date: Mon, 17 Jun 1991 17:14:53 GMT In article connolly@convex.com (Dan Connolly) writes: >In <1991Jun14.150955.25245@auto-trol.com> marbru@auto-trol.com (Martin Brunecky) writes: > >Not necessarily: I use the normal run-time reading of resource files for >prototyping and development, but when I'm ready to build the production >version, I translate the resource file into a C array (we love Perl :), >and use it as the fallback_resources argument when I initialize Xt. > Mhmm. It can get fairly lengthy. What I occasionally do, is specify an application defined resource in my resource file - kind of "key". If after XtAppInitialize (or similar) I can't retrieve this resource, I assume my resource file was not found - so I print out a message to that extent and gracefully exit. Not that I mind the fallback resources - but havingh too much there could make your life miserable if you want to make on-site changes to the UI, as you ed up fighting your own "fallback" resources. Some other people explicitly load their Xrm files. The extremists can read encrypted resource files, so that the user is completely out of any luck. -- Martin -- =*= Opinions presented here are solely of my own and not those of Auto-trol =*= Martin Brunecky marbru%auto-trol@sunpeaks.central.sun.com (303) 252-2499 (better avoid: marbru@auto-trol.COM ) Auto-trol Technology Corp. 12500 North Washington St., Denver, CO 80241-2404