Bug 2921 - Why someone has the idea to remove the trayicon support?!?
Summary: Why someone has the idea to remove the trayicon support?!?
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Plugins/Trayicon (show other bugs)
Version: 3.9.1
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2013-05-11 13:25 UTC by Chris
Modified: 2013-05-11 18:36 UTC (History)
0 users

See Also:


Attachments

Description Chris 2013-05-11 13:25:30 UTC
Hello,

I have used claws-mail much time and it was the perfect tool to organize my mails and so on. It is really a nice program!

But after the last update I was shoked because the trayicon support was gone! Therefore the crappy libnotify support was added, which should be optionally in my opinion!

The most users who use claws are users who want a lightweight mail-client and no bloated software like evolution with to much software which is requiered to run it.

I am using Windowmaker (crm) and wmsystemtray for adding a dock to windowmaker. So I was really happy the whole time that because of this trayicon I have alsways seen if I have new mails or not. I and I think many other who use a lightweight windowmanager dont want to have running a daemon like notfication-daemon like the one from gnome which has so much depencies. But with removing the trayicon support this is needed or this users will change to a other software. I dont want to start my claws all the time a day to show if there are new mail :-(

With removing trayicon support and only support libnotify you support the Ubuntu crap philosophie and kick all the pro users who dont want to use a desktop enviroment in the ass :-/

I really love claws-mail but someone should really think about it and re-add it in the next release. I mean ok it is understandable that ghtkl2 and dillo support was removed because the same functionality is given by webkit but webkit need much more recourses as dillo. Therefore atleast dillo support should be given anymore because it is lightweight and perfectly for do simple tasks like displaying simple html content in mails without running a half chromium in the background...

Please think about it, with the decision to not support trayicon support anymore you support the gnome3/unity/noob crap and kick advanced users in the ass :-(

Would be really nice if someone could think about it.

Also you should wait with gtk3 port a long time. It is totally crap. Gnome3 developers are actually sick in his ideas of a desktop they only develvop gtk3 for gnome3 it is more and more not compatible to previous releases. Also there are no real themes like for gtk2. I and many other user avoid gtk3 apps who we can. gtk2 is a nice toolkit. Therefore firefox, libreoffice and much other GOOD apps dont care really about gtk3 support and mainly only support gtk2 versions. Please let gtk3 optionally for a long run and support gtk2. please let the users the choice. gtk1 support - ok, gtk1 is really old, that is a other topic, but gtk2 is a really good toolkit anymore and used by many good apps anymore.

Hope that I can change someones mind with this letter otherwise there will be no answere like many apps today which want only support the newest crap. But I hope you know what I mean. Otherwise we can change to evolution. It also needs gnome crap...

best regards
chris
Comment 1 Colin Leroy 2013-05-11 13:30:33 UTC
Hi,

The libnotify dependancy for the Notification plugin is actually optional.
Comment 2 Chris 2013-05-11 14:00:09 UTC
Yes, in gentoo linux it is optional over a use-flag. But I dont have a trayicon than. What is wrong with the simple trayicon plugin?!?
Comment 3 Chris 2013-05-11 14:03:48 UTC
http://gpo.zugaina.org/mail-client/claws-mail

Without "notification" and therefore notficication daemon from gnome and his friends this plugin is not provided. Furthermore I dont want the notification-plugin, I want the simple trayicon plugin which is not doing more than change the icon if there are unread mails or not. Nothing more and not less.
Comment 4 khazarian 2013-05-11 14:05:09 UTC
(In reply to comment #0)
> Also you should wait with gtk3 port a long time. It is totally crap. Gnome3
> developers are actually sick in his ideas of a desktop they only develvop
> gtk3 for gnome3 it is more and more not compatible to previous releases.
> Also there are no real themes like for gtk2. I and many other user avoid
> gtk3 apps who we can.

http://blogs.gnome.org/otte/2012/07/27/staring-into-the-abyss/ ;-)
Comment 5 Chris 2013-05-11 14:08:17 UTC
Therefore binary distributions like ubuntu/debian/other will pull in all the needed stuff for the whole claws-mail and therefore also notification-daemon is NOT optionally anymore... Especially as the plugins are now no extra package anymore and shipped with claws-mail ...
Comment 6 Chris 2013-05-11 14:14:17 UTC
(In reply to comment #4)
> (In reply to comment #0)
> > Also you should wait with gtk3 port a long time. It is totally crap. Gnome3
> > developers are actually sick in his ideas of a desktop they only develvop
> > gtk3 for gnome3 it is more and more not compatible to previous releases.
> > Also there are no real themes like for gtk2. I and many other user avoid
> > gtk3 apps who we can.
> 
> http://blogs.gnome.org/otte/2012/07/27/staring-into-the-abyss/ ;-)

Yes, that I have had in my mind with written this. But that redhat and gnome3 and ubuntu/window8 want to force the users HOW THEY HAVE TO USE A DESKTOP is a other topic. But a sad fact... Claws should not support this.
Comment 7 Holger Berndt 2013-05-11 18:36:27 UTC
Please take your GNOME ranting somewhere else.

Also, please reconsider your attitude. Your report is pretty offensive to FOSS volunteers (like myself, and many others).

It would also work if you got your facts straight. Not only is libnotify optional - even when its compiled in, that doesn't mean a notification daemon is necessary - neither at compile- nor at runtime.

And if Gentoo has packaging bugs, please report them at Gentoo.

Note You need to log in before you can comment on or make changes to this bug.