> pageSetup	- to get the page setup dialog, some platforms might 
> not support
> preProcessing	- to get the print dialog and or other tasks , some 
> platforms might not support
> postProcessing	- cleanup if required, some platforms might not support
> printForm: aForm - print a form
> printPostscript: aString - print that postscript, some platforms 
> might not support
> 

Hmm, maybe call it "printSetup" instead of pageSetup, to be nice and
generic?  Also, how about sessions, so that background threads can
print, too?

	createPrintSession   "returns printid.  does pageSetup stuff if
desired, as well as preprocessing"
	printForm: aFrom onSession: id  "can be called lots"
	closePrintSession: id   "finish up"


Alternatively, the simple printForm: and printPostscript: seem fine to
me.  How fancy is it profitable to get?  For complex stuff, I think
we'll want to leave users to use OS-specific tools.


-Lex