[opensuse-kde] Idea: using print-manager / plasmoid for 12.2
Hello, (please CC me, I'm not subscribed) first of all a small introduction: a few of you know me as "einar77" on IRC, and I'm a member of the KDE community (random patches, official forum administration, some small promo work) upstream. Here and there I have contributed a few fixes also to openSUSE packages (mainly related to PyKDE4). I'm writing this to suggest using print-manager instead of printer-applet to keep track of printing jobs on KDE. For those who don't know, print-manager is a series of programs written by Daniel Nicoletti, of apper fame (which is used as updater applet for KDE oS). print-manager consists of a library to talk to CUPS, a KCM to manage printers (perhaps overlapping with YaST on that regard) and a plasmoid for print jobs / queues. Its main advantage over the default upstream provided by KDE are: - maintained (after a hiatus, dantti resumed working on it) - an actually sane code base (believe me... I looked through system-config- printer-kde and I even managed to fix a bug) - smaller footprint (doesn't require PyKDE4) I have been using it for a while and it's definitely nice: on the negative side there are a few layout bugs in the plasmoid when embedded in the system tray that might need fixing. Some references: - http://dantti.wordpress.com/2012/04/11/print-manager-is-now-low-latency-and- low-cpu-demanding/ - http://dantti.wordpress.com/2012/02/28/print-manager-improvements/ - http://dantti.wordpress.com/2012/02/22/say-hello-to-our-must-have-new- plasmoid/ I personally think it's much better to have this solution rather than system- config-printer-kde, which is bitrotting and hardly maintainable. Opinions?
Hello,
(please CC me, I'm not subscribed)
first of all a small introduction: a few of you know me as "einar77" on IRC, and I'm a member of the KDE community (random patches, official forum administration, some small promo work) upstream. Here and there I have contributed a few fixes also to openSUSE packages (mainly related to PyKDE4).
I'm writing this to suggest using print-manager instead of printer-applet to keep track of printing jobs on KDE. For those who don't know, print-manager is a series of programs written by Daniel Nicoletti, of apper fame (which is used as updater applet for KDE oS).
print-manager consists of a library to talk to CUPS, a KCM to manage printers (perhaps overlapping with YaST on that regard) and a plasmoid for print jobs / queues.
Its main advantage over the default upstream provided by KDE are:
- maintained (after a hiatus, dantti resumed working on it) - an actually sane code base (believe me... I looked through system-config- printer-kde and I even managed to fix a bug) - smaller footprint (doesn't require PyKDE4)
I have been using it for a while and it's definitely nice: on the negative side there are a few layout bugs in the plasmoid when embedded in the system tray that might need fixing.
Some references:
- http://dantti.wordpress.com/2012/04/11/print-manager-is-now-low-latency-and- low-cpu-demanding/ - http://dantti.wordpress.com/2012/02/28/print-manager-improvements/ - http://dantti.wordpress.com/2012/02/22/say-hello-to-our-must-have-new- plasmoid/
I personally think it's much better to have this solution rather than system- config-printer-kde, which is bitrotting and hardly maintainable. Opinions? Sounds nice. Considering its made by the guy that made Apper makes me
On Mon, 2012-04-16 at 12:12 +0200, Luca Beltrame wrote: think we would have to be insane to include it. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 16 Apr 2012 09:29:44 Roger Luedecke wrote:
On Mon, 2012-04-16 at 12:12 +0200, Luca Beltrame wrote: Sounds nice. Considering its made by the guy that made Apper makes me think we would have to be insane to include it.
So glib, not so helpful. Most of the problems see 'in Apper' are in fact in the PackageKit-zypp backend (written by SUSE) and also present if you use the native GNOME packagekit UIs, or are in the PackageKit Qt bindings (not by the Apper author). Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Mon, 16 Apr 2012 22:23, Will Stephenson
On Monday 16 Apr 2012 09:29:44 Roger Luedecke wrote:
On Mon, 2012-04-16 at 12:12 +0200, Luca Beltrame wrote: Sounds nice. Considering its made by the guy that made Apper makes me think we would have to be insane to include it.
So glib, not so helpful.
Most of the problems see 'in Apper' are in fact in the PackageKit-zypp backend (written by SUSE) and also present if you use the native GNOME packagekit UIs, or are in the PackageKit Qt bindings (not by the Apper author).
Will
Agreed. This is the wrong horn to blow, the wrong horse to blame. Non the less the Points made by the OP are true. Esp. regarding the high memory consumption. 60 MB res for what? I'd say let's give it a try in the distro. It would have to be really bad to be worse than system-config-printer-kde. {rant on system-config-printer-kde} I've looked at it, shuddered, and removed it from my system, and no, it has not gotten better since OSS 11.2 The big chunk of memory it claims? The browser is already open and http://localhost:631/ does the same job for me. {/rant} - Yamaban. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Mon, 2012-04-16 at 22:23 +0200, Will Stephenson wrote:
On Monday 16 Apr 2012 09:29:44 Roger Luedecke wrote:
On Mon, 2012-04-16 at 12:12 +0200, Luca Beltrame wrote: Sounds nice. Considering its made by the guy that made Apper makes me think we would have to be insane to include it.
So glib, not so helpful.
Most of the problems see 'in Apper' are in fact in the PackageKit-zypp backend (written by SUSE) and also present if you use the native GNOME packagekit UIs, or are in the PackageKit Qt bindings (not by the Apper author).
Will Ok. Nonetheless, I have far fewer issues with the Gnome packagekit bits. In any event then, if its not exactly appers fault then this idea gets a +1.
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (4)
-
Luca Beltrame -
Roger Luedecke -
Will Stephenson -
Yamaban