unity-design team mailing list archive
Mailing list archive
Re: How about developing a spec for all DE's and implement a common low-level API...
So basically all messages *would *be unified based on the fact that it is
using whatever means the DE already has in place? I like the idea of
passing off the display to the system. However, it still leaves the question
of which means on KDE to utilize though, correct? SysTray or Plasmoid?
If a Plasmoid notification is designed, it will be Karmic's baby...Do you
really see these additions making it upstream? I see it more of an add-on
for Kubuntu, since KDE is pushing their notifications system...which is
okay, but I don't know if that's a team goal to get this upstream, or if
it's more important for consistency across *buntu(s)...
On Fri, Apr 24, 2009 at 6:36 AM, Roderick B. Greening <
> Not sure how best to phrase this... however, here goes.
> If we develop a specification and present to f.d.o, which would allow all
> DE's to integrate this spec via a low level API, which would send D-BUS
> notifications and allow any "listener" to pick them up and decide what and
> how to display the notification?
> This allows Gnome's DE to decide how to present without precluding a KDE or
> XFCE implementation from choosing their own method of dealing with the
> If the bus is simply presenting the message, then it's DE agnostic and much
> easier to deal with. I think this is what we should be looking into.
> Roderick B. Greening, B.Sc.
> Paradise, NL Canada
> E-mail/MSN: roderick.greening@xxxxxxxxx
> LP: launchpad.net/~roderick-greening<http://launchpad.net/%7Eroderick-greening>
> Wiki: wiki.ubuntu.com/rgreening
> Blog: roderick-greening.blogspot.com
> Twitter: twitter.com/rgreening
> Mailing list: https://launchpad.net/~ayatana<https://launchpad.net/%7Eayatana>
> Post to : ayatana@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ayatana<https://launchpad.net/%7Eayatana>
> More help : https://help.launchpad.net/ListHelp