Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!ukc!dcl-cs!bath63!pes
From: pes@bath63.ux63.bath.ac.uk (Paul Smee)
Newsgroups: comp.sys.atari.st
Subject: Re: Resource files
Message-ID: <709@bath63.ux63.bath.ac.uk>
Date: Fri, 9-Jan-87 05:42:42 EST
Article-I.D.: bath63.709
Posted: Fri Jan  9 05:42:42 1987
Date-Received: Sat, 10-Jan-87 03:47:57 EST
References: <870108033423.00000616.AEDC.MA@UMass>
Reply-To: pes@ux63.bath.ac.uk (Paul Smee)
Organization: AUCC c/o University of Bath
Lines: 25


I've only played with K-Resource a bit, so if there are any obscure bugs I
won't have noticed them.  However, insofar as I have used it, my impression
is that the software is fine, and fairly easy to use once you've sussed it
out.  The documentation (I use the word loosely) is fairly patchy and
haphazard, so that some experimenting is required to work out how to do
things initially -- though there is a step-by-step 'example' provided which
covers the most common sort of cases.  Experimenting isn't too hard, because
the interface is primarily by windows, icons, and mouse, and so most things
you'd want to do are fairly obvious, especially once you've found them once.

It will make resource files and header/include files for your choice of 4
languages, which include FORTRAN and C -- I'm pretty sure the other two
are Pascal and Modula-2, but not positive, so if you need something other
than FORTRAN or C, check first before you buy.

It does *not* produce a source-level form of the resource file itself, so
that (for example) the 'rcsfix' technology posted some months ago for
incorporating your RSC file into your program won't work.  It produces
an 'object' RSC file, the required include file, and allegedly a third
file in a form such that it can be massaged by privately written tools, which
I haven't puzzled out.

(I have no connection with Kuma, other than wishing they'd buy themselves
a qualified tech writer.)