Summary: | [KDE4] Use message balloons to keep user informed | ||
---|---|---|---|
Product: | [Unmaintained] printer-applet | Reporter: | Dik Takken <kde> |
Component: | general | Assignee: | KDEPrint Devel Mailinglist <kde-print-devel> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | wishlist | CC: | bluedzins, jlayt |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Dik Takken
2004-06-12 13:56:19 UTC
Just a few comments about your suggestions: 1) This is a nice idea and I'll think about it 2) This doesn't depend completely on KDEPrint because it requires communications possibilities at the driver-level. Currently, there's no real implementation of a bi-di driver under UNIX, but this should change in the future as some work is being done by the OpenSource community and printer manufacturers. For now, the communication is only PC->printer and not the other way around; there's no (standard) way to get this kind of notification from the printer. 3) Notification system (either about spooling events, or about driver events) is something that is under development in projects like CUPS or even in printing workgroups. Once something will be available, you should see a front-end in KDEPrint. If you do this, please include a possiblity to disable it. I am very sure that it will be totally annoying to me. What do I care if KJobViewer received a print job normally? If I print a document I expect it to be printed. I hardly ever want to mess with the print jobs. So KJobViewer should be as silent as possible. I don't even need a tray icon. If it is implemented using the normal KNotify framework, it will be a normal notification like any other. All Notifications are configurable from the same central config module in KControl. This will hardly ever make it into a KDE 3.5.x release. Set to Version 4.0. I hope we get this done and in. CUPS 1.2.x does provide a much better notificiation framework, which we should take advantage of in KDEPrint 4.0. duplicate of bug 117040 -- keeping both open for now (may get a JJ: implementation) Reassigning to printer-applet. KDEPrint in KDE3 is unmaintained and will have no more new features implemented. This request will never be implemented in KDEPrint as a result. In KDE4 kjobviewer has been replaced by printer-applet which uses system-config-printer as a backend. This is still a valid request, supporting the IPP/CUPS Notifications framework (CUPS 1.2 onwards) for job, printer and server status updates via the KDE notifications framework should be added to printer-applet. How printer hardware status relates to Solid is an interesting question :-) SVN commit 917147 by jriddell: update a lot of code to re-sync with GTK version BUG:167699 BUG:178820 CCBUG:83257 M +5 -1 CMakeLists.txt M +2 -2 README A authconn.py A debug.py A monitor.py M +5 -0 printer-applet.notifyrc M +635 -321 printer-applet.py M +13 -14 printer-applet.ui M +2 -0 statereason.py WebSVN link: http://websvn.kde.org/?view=rev&revision=917147 "Printer Applet" is no longer maintained and has been replaced with "Print Manager" since KDE 4.10. If this issue still needs to be addressed in KDE 4.10 or newer, please add a comment, or report it for "Print Manager". |