OK, guys thanks for the help so far. I've played a bit.
The subclassing of PDFDocument and PDFPage was quite straight forward.
(Although unexpected as usually everyone tells you "usually you don't
subclass in Cocoa land") Just out of curiosity I've just compiled it
with the 10.4 SDK and it compiled just fine. So I guess it will just
not work on 10.4 although it has compiled successfully?
(I am on Leopard still targeting Tiger. That's why)
Well, in a very crude fashion you can still accomplish what it is I
think you;re trying to accomplish. You're subclassed PDFPage's
could, on Tiger, render a regular PDFPage. It's gross but what I'm
describing is basically having two parallel PDFDocuments — one
created from a file or data ([PDFDocument initWithURL:] or
[PDFDocument initWithData:]) and the other empty PDFDocument you
create with -[init]. For each page in the former document you
create a new PDFPageSubclass object and add it to the empty
document. Your subclass does the various scaling/filtering in it's
draw method and calls it's doppleganger PDFPage to render.
So I said it was gross....
Hm ...indeed
So should rather look into the CGPDFDocumentRefs (/Developer/Examples/
Quartz/PDF/CGPDFViewer) way of doing it?
cheers
--
Torsten_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
