Replies: 1 comment 6 replies
-
|
@Waxhaw So PAPPL provides the IPP printer semantics/wrapper, plus some basic job processing/raster printing functionality. If you have your own file processing code, you can probably integrate it fairly easily - the only thing you'll need to do is support the raster printing interface for clients that send PWG/Apple Raster. |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What if I wanted to build an AirPrint product and I already had my own custom print engine?
For example...
I just want to advertise a generic printer to do photo printing for an AirPrint interface for iOS and Android.
Would this be difficult?
So currently I'm doing this via a generic ppd file and a custom filter to move the image to a 'hot folder' for printing.
Based on the C API code examples, this looks like a single solution that doesn't make it easy to open that part up.
Curious what other think. I would love to get away from legacy ppd files.
TIA!
Beta Was this translation helpful? Give feedback.
All reactions