Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!bloom-beacon!usc!merlin.usc.edu!nunki.usc.edu!malczews
From: malczews@nunki.usc.edu (Frank Malczewski)
Newsgroups: comp.sys.mac.programmer
Subject: Re: A plea for revised mac programming
Message-ID: <3836@merlin.usc.edu>
Date: 20 May 89 22:43:45 GMT
References: <8500011@gistdev> <310@smsdpg.uu.net> <1966@internal.Apple.COM>
Sender: news@merlin.usc.edu
Reply-To: malczews@nunki.usc.edu (Frank Malczewski)
Organization: University of Southern California, Los Angeles, CA
Lines: 34

In article <1966@internal.Apple.COM> blob@apple.com (Brian Bechtel) writes:
>In article <310@smsdpg.uu.net> rht@smsdpg.uu.net (Randy Thompson) writes:
>> I would also ask 
>> that Apple consider a novel (???) approach... 
>> 
>>     loose leaf instead of bound documentation?
>
>Spring 89 APDAlog, page C-47:
>
>Inside Macintosh, Vols. I-V Plus X-Ref, Looseleaf Edition.  $129.00
>
>It's been available for several months.
>
>--Brian Bechtel     blob@apple.com     "My opinion, not Apple's"



I believe what was meant here would be:

A loose-leaf version of Inside Mac (fro example -- pick your favorite Apple
document), where:

  1)  All information pertaining to a particular manager is contained in the
      same location

  2)  Changes to particular pages (revised, new, etc) are part of a replacement
      set of pages that are a subset of the entire manual  (as opposed to the
      current approach of replacing entire manual sets with each new release).
      One either: removes obsolete pages, replaces revised pages with their
      updated versions, or adds new sets of pages for new material.

At least this would be a start...

  -- Frank Malczewski        (malczews@castor.usc.edu)