home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!rutgers!cbmvax!jesup
- From: jesup@cbmvax.commodore.com (Randell Jesup)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: OS 3.0 Manuals
- Message-ID: <38165@cbmvax.commodore.com>
- Date: 28 Dec 92 20:42:20 GMT
- References: <37847@cbmvax.commodore.com> <1992Dec28.132343.22705@enea.se>
- Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
- Organization: Commodore, West Chester, PA
- Lines: 23
-
- tope@enea.se (Tommy Petersson) writes:
- >jesup@cbmvax.commodore.com (Randell Jesup) writes:
- >: Manuals are always later than the hardware/software, since often
- >: details aren't firm until release. Note that the 2.0 manuals came out shortly
- >: after 2.04 (if I remember correctly). This also gives us time to make sure
- >: bugs and workarounds are documented in the manuals. BTW, even if we were to
- >: do a hardware manual it probably wouldn't be available for quite a few months.
-
- >The only way to get good, actual manuals out shortly after program
- >release would be to relese them on CD (or floppys) in AmigaGuide format.
- >If this format is used during development, small corrections can be made when
- >the bugs are found, and the CD's/floppies then made.
-
- There is a CATS developer CD (I don't think it has the text to the
- manuals though). The biggest problem is not the publishing, however: it's
- actually writing them.
-
- --
- To be or not to be = 0xff
- -
- Randell Jesup, Jack-of-quite-a-few-trades, Commodore Engineering.
- {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com BIX: rjesup
- Disclaimer: Nothing I say is anything other than my personal opinion.
-