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 465691
To view parent comment, click here.
To read all comments associated with this story, please click here.
jamboarder
Member since:
2009-02-16

It may well require a slight touch of paranoia to suggest that GNOME Shell folks were afraid of competition so they deliberately implemented an incompatible systray/notification area. They may simply have been so caught up in getting things done they forgot or ignored the fact that there were other folks trying to implement a cross-desktop systray/notification spec. It was, at minimum, careless.

The hope now is that the community can start working together to fix this particular issue and fix/prevent other issues.

Reply Parent Score: 2

Delgarde Member since:
2008-08-19

They may simply have been so caught up in getting things done they forgot or ignored the fact that there were other folks trying to implement a cross-desktop systray/notification spec. It was, at minimum, careless.


Oh, I think it's deliberate enough - there's not much doubt of that if you read the mailing list posts. It seems pretty clear that the Gnome people simply weren't happy with cross-desktop spec that was being put together, concluded they couldn't change it enough to be workable for them, and opted not to use it.

So yeah, for better or worse, it was certainly a deliberate design decision, not a case of forgetting or not knowing about other efforts.

I'm personally inclined to agree with them - Ubuntu have produced decent docs for their AppIndicators implementation of the spec, but the spec itself is extremely vague in terms of what an app that uses the interface can expect to happen. I appreciate Aaron's point that this should be determined by the implementation, but the spec still should provide some guidelines.

Reply Parent Score: 2