I have made some small modifications to my copy of qlprint to support sending the image data to stdout instead of to a USB connected printer. This allows network printers to be simply supported (Brother QL network printers do not return status information).
This was reasonably simple, first having some pre-defined configurations for the printers required. And then using those instead of querying the printer.
Second, using the stdout file descriptor when required.
Third, making any requests for status from the printer optional.
Example, send the three image pngs to stdout with auto-cut enabled, netcat used to send to printer:
qlprint -b QL-710W-62x100 -p - -a image1.png image2.png image3.png | netcat printername 9100
Currently the -b option points at pre-defined configurations that are compiled in (I just used the -i option to capture the status from a usb connected printer.) But that could easily be extended to allow for configuration files.
I can forward patches if you want to incorporate into this project.
I have made some small modifications to my copy of qlprint to support sending the image data to stdout instead of to a USB connected printer. This allows network printers to be simply supported (Brother QL network printers do not return status information).
This was reasonably simple, first having some pre-defined configurations for the printers required. And then using those instead of querying the printer.
Second, using the stdout file descriptor when required.
Third, making any requests for status from the printer optional.
Example, send the three image pngs to stdout with auto-cut enabled, netcat used to send to printer:
Currently the -b option points at pre-defined configurations that are compiled in (I just used the -i option to capture the status from a usb connected printer.) But that could easily be extended to allow for configuration files.
I can forward patches if you want to incorporate into this project.