
Thread beginning with comment 465674
To view parent comment, click here.
Member since:

Well, on the other hand if you read the last email from Aaron, he made it abundantly clear that no amount of use cases and other stuff could make him change his mind about fixing the vagueness of the spec, which is really what bothered Dan Winship and Mattias Clasen.

What he's arguing now is that the GNOME developers should just have eaten what they got served in the name of cross-desktop compatibility. And that's a fair point, no doubt about that.

They didn't have to "eat what they got served". They could have proposed something else. No, what happened is they stopped communicating, went off and implemented a different systray/notifier mechanism and barely even bothered mention it to the people on fd.o who were obviously interested. This isn't about egos. This is about not fragmenting the FOSS app/DE ecosystem even more than it already is. Collaboration requires communication. You don't like what was proposed? Fine. Propose something else or leave things as they are. Don't go off creating something entirely different and expect folks to not get upset when you didn't care enough to tell them about it. As an app developer, I now have to decide which systray/notification mechanism to support or just go back to using crappy XEmbed. That's not progress...

As far as the merits of the Status Notifier spec, what a pleasure it is to run KDE apps in Ubuntu and see consistent GTK menus and tooltips in the GNOME systray instead of an out-of-place Qt/KDE menu or tooltip. How nice to see Plasma tooltips for Rythmbox instead of some out-of-place GTK tooltip on my KDE desktop. You would never think there were *any* practical value to the specs just reading their objections and, unfortunately, their objections are all we have as a testament to their efforts at cross-desktop collaboration on this particular issue. Again, this is not progress...

Reply Parent Score: 7