Summary: | Better accessible printer driver settings | ||
---|---|---|---|
Product: | [Unmaintained] kdeprint | Reporter: | Dik Takken <kde> |
Component: | general | Assignee: | KDEPrint Devel Mailinglist <kde-print-devel> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | wishlist | CC: | jlayt |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Dik Takken
2005-09-25 00:50:16 UTC
I don't know this MS Word app you're describing here but most applications that are not KDE-related have some means of configuring the printing command. Find that configuration in your application and replace whatever is there with the word "kprinter". This will pop up the KDE printing dialog (the one you reached from KWord) and you will be able to configure your printer before printing. Alternatively, you can start kprinter by hand (<Alt+F2> kprinter <Enter>). Nevertheless, the different user-facing KDE printing system components will get a usability work up for KDE4. Printer configuration will perhaps become more readily available from outside applications then. Thanks for reporting. > I don't know this MS Word app you're describing here :) > replace whatever is there with the word "kprinter" Yes, I know that trick. But for all those poor people out there who don't, it might be desirable that their printer is KDE-configurable, even when the user is not using a KDE application. > components will get a usability work up for KDE4 Looking forward to that! > Thanks for reporting. Thanks for replying! Dik, printing is a very complicated matter -- on all platforms. You don't need to go into the scary KCM module to configure your printer setting defaults. Just start "kprinter" (or click on the "Print" icon of a KDE application) and driver settings are accessible immediately after clicking "Properties". (Yes, again some scary tabs...) I honestly can't think of a much better way (one reason, but not the only, is that new users very likely are already "used" to this, because it is similar to how Windows does it). "Better accessible printer driver settings" by putting them onto the front of the print dialog will very much overload and bloat that dialog (and we'll have more bug reports and complaints about that fact). And if *every* single application makes its own settings "better accessible" by putting them directly under users' noses, everyone will loose (and probably nothing will be left of the workspace). I can't think of a solution. What are your ideas? If you'd like to contribute to KDE4 print UI designs, please come forward soon. Mockups and detailed ideas written down are welcome. If I don't hear from you before Feb 1, 2007, we might close this report. (We won't forget about it -- we already know that we want to improve every aspect of KDEPrint in KDE4, but we also are short of people doing work.... so in the end, there may be not much change to KDE printing when KDE4 comes out). Cheers, Kurt The heart of the problem is that it is too difficult to change printer settings *outside of KDE applications*. Sure, you and I know you can type 'kprinter' and do your thing, but the average user would have no clue how to do it. The solution I see is allowing direct access to printer settings from the KDE desktop itself. Maybe an entry in the KDE Menu (like windows has) or a tray-icon. A simple menu hierarchy like this would be ideal (ASCII art): --------------------|--------------- Set Default Printer | -> Printer 1 | | -> Printer 2 | | -> Printer 3 | --------------------|------------------| Set Printing Mode |-> Black ink only | |-> Color | --------------------|------------------| Cancel Job |-> Job 1 | |-> Job 2 | --------------------|----------| Configure... | --------------------| Where "Configure" will allow access to the full set of configuration options. I don't know what the KDE-4 desktop will look like, but IMHO it should offer instant access to things you need often. KDEPrint is obsolete, unmaintained and will never be revived. Closing all open bugs. |