[Kde-print-devel] [Bug 134782] [KDE4] Make CUPS printer detection stoppable! Integrate progress indication with main window?
Maciej Pilichowski
bluedzins at wp.pl
Wed Jan 10 19:40:55 CET 2007
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=134782
------- Additional Comments From bluedzins wp pl 2007-01-10 19:40 -------
> did you try my advice to switch your print subsystem plugin away from CUPS?
No, but thank you for that, I will use it to help other people. Between the post (original) and our discussion here I bought a printer :-)
> @ a) This is the first time you talked about "Print Preview".
Look at layout of the item -- Print preview is near Print (or could be). So, for somebody with hands disorder (movement) it is easy to "overclick".
> @ b) I didn't say it's an error if you have no printer. But if you click
> "Print", it can be assumed that you also have a printer,
I still do not agree. When I click "print" in "print dialog" -- yes. Or if I click "direct printing" (or immediate printing).
> Clients are able to discover any
> new printers that might be added by the CUPS server admin; servers are
> able to promote their newly acquired queues within seconds to all
> clients which need no additional configuration steps; that's why there
> is what you
> call "autodiscovery" in kprinter.
First -- it should be only Kcontrol task.
Second -- if I understand correctly, with each "print" click (in menu) the program scans the network? It means there is a waste if no printer is changed, right?
I am still convinced that Kcontrol could do automatic scan, and print dialog only on demand scan (or run Kcontrol).
> @ e) Sorry, I didn't at all understand what you are trying to say.
Ok, I simplify. Have you ever read an article on e-newspaper. Full of ads, banners, flashing images, splitted into parts? Ugly, right? But there is easy way to READ user-friendly version -- by clicking on "print version". Pure, beautiful article. But there is a catch -- the print-page could call JS print dialog, and now I wanted to read a page but in the result I got print dialog with auto-detection window.
It is effect of not very good design -- too many, untrue, assumptions. KISS, right? :-D
> I hope you noted that we accepted a few of your suggestions
> nevertheless. :-)
Yes, yes :-)) Thank you for that. I am bit scaried with this "KDE4" but... :-)
More information about the Kde-print-devel
mailing list