unity-design team mailing list archive
Mailing list archive
Re: Getting rolling for 9.10
> Scott Kitterman wrote:
>> On Thu, 23 Apr 2009 09:46:17 +0100 David Barth
>>> ... Could you coordinate with your "masked" developer friend to
>> him at the Summit. ...
>> You are being too subtle for me here perhaps, unless perhaps you think
>> acting as a sock puppet for Aaron Seigo (since I referenced his mail in
>> previous message). Let me assure you I am nobody's sock puppet and
>> for no one.
> Hey, sorry, I think I misread you when you said:
>> another community developer (I'll thank him by name
>> after it works) is working on getting KDE trunk
OK. No problem. Sorry for not getting where you were headed with that.
I just didn't name him because if it doesn't work out I don't want any
blame. It's not up and working yet.
The relationship of that effort is to this one is to make it easy for the
Ayatana developers working on the KDE aspects of the projects to run KDE
trunk on top of a stable Ubuntu foundation. I hope that this community
initiative is an aid for your development work.
>> I do hope we can have a positive discussion here about how best to serve
>> Kubuntu users that use applications that drive notify-osd notifications.
>> Given the absolute dependence of notify-osd on the indicator (I see it
>> a number of names and I'm not sure which is the current, correct term),
>> seemed reasonable to start the discussion with that.
> Right. The indicator is actually made of 3 parts:
> * indicator-applet, which is a gnome-panel compatible shell hosting...
> * ... the indicator-applet, which is the actual indicator
> * and libindicate which is the client side library made to simplify the
> application developers life (well, provided you're a Gnome application
> developer for the moment that is...)
> What we need to discuss is which part we need to develop for the KDE
> desktop, which one we can re-use on KDE, which one we can share between
> Gnome and KDE.
Of course. Part of why I bring up the new systray protocol now is that
because it offers a different set of capabilities and a different way to
integrate into the systray, I suspect that which protocol you choose to
use will affect some of the decomposition you need to do to get to a well
engineered cross-DE system.