Path: utzoo!mnetor!uunet!husc6!think!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: The Resource Problem
Message-ID: <47684@sun.uucp>
Date: 31 Mar 88 07:26:12 GMT
References: <4595@garfield.UUCP> <2442@unicus.UUCP> <25973@amdahl.uts.amdahl.com>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 17

Another part of the 'resource' problem isn't a problem at all. And that's the
pointers that are imbedded into the code. Because when the *user* edits the
'resource' file (I like to call them tool files) they are only interested in
changing things like the fonts, text, borders, and menu shortcuts. The other
stuff is fixed by the application at compile time. Take my ezmenus package 
for instance, it uses a link list of structures to build up a menu list. 
The structure can be reordered at will in the code and the menu will change
appropriately. It is a very simple modification to have the runtime code
read these structures from a file. Things like the 'routine to execute' 
when a menu is selected appear in the file as 32 bit hex constants but
the user doesn't care because those fields are 'unmodifiable'.

--Chuck

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.