🚀 go-pugleaf

In article <13458@teknowledge-vaxc.ARPA> dplatt@teknowledge-vaxc.ARPA (Dave Platt) writes:
>It seems to me that another way to handle this might be to store the
>appropriate print record in the resource fork of the documents being
>formatted, rather than in the resource fork of the application.  This
>might be safer (the application wouldn't need to be self-modifying).

Storing the print record in the document file may take up some more disk
space, but I'd trade that to keep my application from being self-modifying.
Sounds like a good idea for me.

>This trick could be combined with the "style sheet" concept that I
>seem to recall floating by in a technote a couple of months ago.
>Different style-sheet documents could be created; each one would have
>an empty data fork and a single "XXXX" (or whatever) resource in the
>resource fork, containing the appropriate print record.  The "New..."
>dialog would probably want to pop up an SFGetFile to select the
>appropriate style sheet.

I don't really need all that power.  I need only one "style-sheet".  Although,
a reference to the tech-note in question might be enlightening.

Thanks a lot,