Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!Firewall!uunet!tnc!m0154
From: m0154@tnc.UUCP (GUY GARNETT)
Newsgroups: comp.sys.amiga.programmer
Subject: Re:  ResEdit for the Amiga? It's not impossible... and it's desirable
Message-ID: <837@tnc.UUCP>
Date: 14 Jun 91 12:49:09 GMT
References: <14224@dog.ee.lbl.gov>
Reply-To: m0154@tnc.UUCP (GUY GARNETT)
Distribution: comp.sys.amiga.programmer
Organization: The Next Challenge, Fairfax, Va.
Lines: 20


Perhaps I sould clarify my idea about  resource files.  What I
intended was that the resources be in a separate file during program
development (to make it easier to manipulate the resources separately
from the program) and be accessed through a set of functions in a
(possible language or compiler dependent) link library.  When you are
ready to release the program, link a different resource library (one
that knows how to locate resources installed in the executable), and
bind the resource file to the program executable.  That way, the thing
won't get lost, and it will be in a separate, independent hunk (or
hunks) so that it will be relatively easy to modify in place.

One additional benefit of a resource editor like this one is that
appropriate structures can be placed in a hunk and marked for storage
in CHIP RAM (even if the compiler in question does not provide a
facility for it).  This can happen "automatically" in the resource
editor (with a way to over-ride the default behavior, of course).

Wildstar
"... I'll see you on the dark side of the Moon!" -- Pink Floyd