[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Thoughts on the systray II.
From:       Lubos Lunak <l.lunak () suse ! cz>
Date:       2005-04-18 14:30:43
Message-ID: 200504181630.43617.l.lunak () suse ! cz
[Download RAW message or body]

On Friday 15 of April 2005 23:40, LiuCougar wrote:
> On 4/15/05, Aaron Seigo <aseigo@kde.org> wrote:
> > On April 15, 2005 21:18, LiuCougar wrote:
> > > What if I have an app which does not have task bar entry, but requires
> > > a system tray icon and another kicker panel applet to ahieve more
> > > advanced features (docking the main window of my app to the kicker,
> > > which is an existing feature in windows XP).
> > >
> > > It seems to me that this is not possible in the new model. Or am I
> > > wrong?

 If "docking the main window of my app to the kicker" means making the actual 
window part of kicker, i.e. embedding it, then no. And it's also not possible 
to do it the current way the systray, because this has nothing to do with the 
systray. Unless I misunderstood what you mean, because that description above 
doesn't make much sense to me.

> >
> > no, this will still be possible. you don't need a GUI or a visible
> > window. you will create a KSomeOtherTray ;) object and give it an icon
> > and connect to some signals. it will then communicate via X atoms (or
> > perhaps at some point an IPC mechanism like DCOP/DBUS) to the consumer
> > (in this case kicker) which will then show the icon.

 Hmm. Clearly at least one of us misunderstood your description, I'm just not 
sure who. But even if this is about turning a mainwindow into an applet then 
it doesn't make much sense to me either.

> >
> > your application will recieve events like "show your context menu now,
> > please" and "ok, show your main window!"

 No, it preferably shouldn't. Aaron, I thought one of your problems with the 
old systray was the apps do a lot of stuff themselves. The "show your context 
menu" part in the plan is only because I don't know how to transfer the popup 
to kicker without somebody complaining that their <insert some weird widget> 
doesn't work in the popup.

>
> Thanks for the explanation. I do like the idea
>
> > > I really do not like QXEmbed class: it requires a lot of hack to work
> > > as expected; but I have to use it in my app to implement the applet I
> > > mentioned above...
> >
> > yep. i too dislike XEmbed for these tasks. which is the whole reason for
> > the push away from it here ;)
>
> Can I use the new mechanism in kicker applet? I'd like to be able to
> replace QXEmbed class with a more friendly one.

 It's simple. If you want to show something as a part of another application, 
then it either has to be transfered to that application, or it has to be 
XEmbed. There's no other way. XEmbed may have bugs, but what doesn't.

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak@suse.cz , l.lunak@kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]