Mike,
> On Jul 28, 2016, at 1:55 AM, Mike Crawford <[email protected]> wrote:
>
> Greetings, I just subscribed.
>
> I may get a contract to write a macOS driver for a USB printer. Is there any
> documentation or sample code for this?
There is some sample code buried in the developer.apple.com archives - look for
"Sample Raster".
The current, most up-to-date documentation on writing drivers can be found on
CUPS.org:
http://www.cups.org/documentation.php/doc-2.1/raster-driver.html
> I plan to buy Michael Sweet's "CUPS: Common UNIX Printing System" but I need
> to find a bookstore that has it in stock or could order it, and that accepts
> PayPal. (Powells in Portland, Oregon accepts PayPal but is unable to order
> it.)
Sadly, this book hasn't been updated since the 1.2 beta days and has become
quite out-of-date... :/
> Alternatively, perhaps one of you right chaps could sell me your copy and I
> would pay you with PayPal.
>
> My plan is to write a prototype on Linux then port it to macOS. I need to
> know what is different or special about macOS printer drivers.
The main difference is that macOS printer drivers support Print dialog
extensions and a printer utility application to provide additional UI.
> Somewhere I found the advice that one should contact Apple Developer
> Technical Support before starting work. Would I need to use a Support
> Incident to do so? Or do I really need their help? I'm quite an experienced
> Mac developer.
If your USB printer requires special handling at the USB level (i.e. it won't
work with the standard USB print class backend or the IPP-USB interface) then
you'll want to contact DTS for the USB class driver sample code.
_________________________________________________________
Michael Sweet, Senior Printing System Engineer
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Printing mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/printing/archive%40mail-archive.com
This email sent to [email protected]
