🚀 go-pugleaf

In article <1948@elrond.CalComp.COM> anson@elrond.UUCP (Ed Anson) writes:

.>I have this same suggestion for 'SIZE' resources; it should be possible to
.>put a SIZE resource in a document, which would override the SIZE in the
.>application (which would be used as a default)...

>  I second the motion.  This problem (together with the lack of print 
>  spooling) is the main reason I find myself flipping back and forth between
>  Finder and MF...

I have a similar problem, but from the other side.  I am writing a print
driver that wants to build a pixel image of the page in the MAC, then send
it to the device.  I think it is unfriendly to ask applications to include
an additional 1 or 2 Megabytes in the SIZE resource, just so I can lay
out the page (high resolution pages, in color).  Since the MAC is nominally
a "single user" machine, why not allow an application to request a non-
contiguous memory allocation.  I know that there are potential fragmentation
problems, but we are probably not launching arbitrary user tasks while this
extra memory is in use, and in any event the process can request just what
it needs -- which is more efficient than guessing at 'SIZE' time.

Marc Kaufman (kaufman@Shasta.stanford.edu)