Re: Ridiculously Enormous PDFs and Printing
Re: Ridiculously Enormous PDFs and Printing
- Subject: Re: Ridiculously Enormous PDFs and Printing
- From: Greg Titus <email@hidden>
- Date: Thu, 17 Jul 2003 08:46:57 -0700
On Thursday, July 17, 2003, at 07:07 AM, Robert Clair wrote:
I have an application that does a lot of instancing - essentially the
user can stamp little bits of hi-res bitmap around at various
positions,
scales and orientations. Of course I only keep one copy of each bitmap
and draw it where ever it is required. The problem comes when you
print -
the printing architecture makes 1 copy of the bitmap each time you
draw it.
It doesn't know from Form Xobjects or anything like that.
This can lead to absurd situations - I have one test file whose spool
file
was heading past 4 Gig when I killed it, three hours into the process.
From
previous experiments it would have taken days to print on my dumpy
little
HP 842C. This for a design that stores in about 5 Meg in the app's
file format
and draws on the screen in less than a second.
Hi Bob,
I haven't actually verified this myself, but I've been told that if you
do your drawing using CoreGraphics and use the same CGImage instance to
do all of your 'stamping' into a CG PDF context, that it will generate
PDF that contains the bitmap data only once. Apparently higher level
APIs (Cocoa and Carbon) tend to create new CGImage wrappers around the
bitmap data each time they draw, so CoreGraphics doesn't realize it is
the same image repeated.
Like I said, I haven't tested this myself, but it might be an approach
to try first, rather than jumping directly into generating PS or PDF
manually.
Hope this helps,
- Greg
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.