[open-beos-printing] Re: Print Server Progress Report

Hi Michael,

> anybody interested=3F

Well, yes, but I'm already whrestling to produce something (anything!) 
for network team, so 
right now I'm mostly in lurking mode here.
However, I've opinions, still!
;-)
 
And, I may consider adding at least a Close button at the current Add 
Printer dialog, too. ;-)


> Done:
> - abort printing if printer is removed in Printers Prefs
> - abort printing when print=5Fserver quits
> - avoid resource conflicts (=3Dtransport add-ons) printing to multiple 
printers

Could you tell us (me=3F) some details here=3F
Do print=5Fserver run parallel jobs processing on any print spooler 
unless there is another one using the same 
transport add-on=3F By "using", I mean "another spooler configuring for 
using this transport".
Or do you go more deeper and test if the transport add-on allow 
multiple access (Print To File, for example)=3F

I'm fine with first one, BTW, just curious. 

> - print=5Fserver detects added or removed printer

> Todo:
> - restart canceled job
> - abort printing if printer add-on fails
> - allow Preview print jobs be printed asynchronous

As Preview don't require any transport add-on, I guess it should fall 
on the "no transport access conflict" case, no=3F

> - extension to R5: allow selection of printer per application, 
similar to Dano

Yeah, this fine BPrintPanel=3F I give a look at the new *print kit* in 
Dano, and it looks fine.
There is both raster and vector kind driver support there, plus some 
generic config views for page setup and 
job setup. We have UniversalPrint on BeBits we could help us here, 
maybe...

I think the "Add Printer" in Dano looks finer too. No more Network / 
Local printer separation.
In fact, the transport add-on let you connect to a remote printer, even 
if it's considered as a "local" printer 
by the BeOS R5.0.3- "Add Printer" setup dialog, go figure.

There also something cool to consider in the print=5Fserver design: 
having a pass-thru mode.
I mean no rendition required, the job file was already *rendered* by a 
third party driver, probably on another 
computer. Think about a IPP daemon or LPD daemon, accepting jobs, 
putting in the asked spooler.
The job file will be in *raw* format, print=5Fserver only need to send 
its content to the transport addon.

Or... if the printing client computer is under BeOS too, maybe the file 
received by IPP/LPD, etc, is really a 
classic job file and the server will have to use his driver: no driver 
to install on BeOS clients to be able to print 
on a BeOS printing server, woa!!!

Okay, I stop dreaming now.

-Philippe
 

--
Fortune Cookie Says:

If today is the first day of the rest of your life, what the hell was
yesterday?

Other related posts: