To read all comments associated with this story, please click here.
No, we will have a fully working OS, even without CUPS.
The Haiku kernel is not a port, it is a rewrite of the NewOS kernel (MIT licensed) that aims to be binary compatible with BeOS. All other parts of Haiku are written from scratch.
CUPS is an open source, GPL, cross platform printing system that supports 1000 printers. A port of CUPS to BeOS will bring choice of printing. Not of Kernel!!! If you don't want CUPS, don't install it... Just don't expect printer companies to write drivers for Haiku...
Edited 2007-08-01 13:17
See, my understanding of CUPS is that it uses PPD drivers (standard postscript printer definition file or whatever it stands for) and then for other printers, it converts them to postscript with an additional layer - and provides it's own custom CUPS-PPD files for those...
In the grand scheme of things, Haiku already supports PCL5/6, IPP, PS, and LIPS control languages - it seems like the right thing to do now is to write layers to translate the PPD and CUPS-PPD files into something Haiku can use natively.
Has anyone asked Michael Pfeiffer (the guy who did most of the printing kit for Haiku) what the right strategy would be from his perspective?
Actually I and others just continued what Ithamar R. Adema had started.
Here is just my opinion, not an official Haiku position: Let's see and wait for the completion of the port and how well it integrates into the BeOS/Haiku printing system. If it works well enough, why should we waste our time implementing and maintaining printer drivers.
"Best plan would be to create 1000 native drivers for 1000 printers in BeOS."
You dont need 1000 native drivers. As I said earlier I used PPD's with IPP just fine. Maybe I was the only one who bothered to figure this out?
You'd probably only need one driver for each printing protocol, ie IPP, SMB, lpr etc.
This is turning into another discussion about which is the best way for those that can write a few thousand lines of c++ code...!!! Simplicity in usage. Plain and simple.
The user doesn't care how it is done, as long as it is done. After giving the ability to print to 1000 printers, we can start redesigning to get simplicity on the developers side. And since CUPS already worked on Zeta as part of the system, I don't see why not on R5 and Haiku.
If there was some other reason, like too much memory, or a huge delay or something like that, it would have to be redesigned now. But there is no such reason. The only goal is to get Haiku and R5 to print on 1000 printers as fast as possible. Provided of course I can do the port!!!
Edited 2007-08-02 06:52
You'd probably only need one driver for each printing protocol, ie IPP, SMB, lpr etc.
That's fine if you're talking about network printers, but I would guess that most home users have an inkjet printer connected directly in which case a PPD isn't going to cut it.





Member since:
2005-07-22
CUPS is not a matter of best plan, but of choice. Best plan would be to create 1000 native drivers for 1000 printers in BeOS. However porting CUPS (if possible) will bring choice of those 1000 printers a 1000 times faster... don't you think?
And open source software is all about choice...
Edited 2007-08-01 12:13