Linked by Thom Holwerda on Thu 10th Mar 2011 12:59 UTC
Talk, Rumors, X Versus Y If you were, you know, living your lives, you've probably missed it, but old fires are burning brightly once again: there's somewhat of a falling-out going on between KDE and GNOME, with Canonical siding squarely with... KDE. The issue seems to revolve around GNOME's lack of collaboration, as explained by KDE's Aaron Seigo.
Thread beginning with comment 465948
To read all comments associated with this story, please click here.
The other side of the issue
by Mirek2 on Sun 13th Mar 2011 00:37 UTC
Mirek2
Member since:
2011-03-12

This article seems a bit one-sided to me. Gnome has accepted and incorporated various projects into their core product, and its community is open for everyone to join.

There is a number of reasons why libappindicator is not included in the Shell, but perhaps the most essential one is that app indicators simply don't fit into the Gnome Shell interface, where all the system-related components are presented in the top panel and all the application-related components are in the message tray.

For a well-documented, yet wonderfully readable development of the libappindicator issue, read this: http://bethesignal.org/blog/2011/03/12/the-libappindicator-story/

Reply Score: 0

Richard Dale Member since:
2005-07-22

There is a number of reasons why libappindicator is not included in the Shell, but perhaps the most essential one is that app indicators simply don't fit into the Gnome Shell interface, where all the system-related components are presented in the top panel and all the application-related components are in the message tray.


My understanding of the spec is that it is up to the desktop shell to provide the visualization of the data sent over dbus. So it the desktop shell wants to show system related components in in a top panel and application related things in the message tray that is fine. The spec doesn't mandate that everything should be shown in a single panel.

Reply Parent Score: 4