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

List:       kde-devel
Subject:    Re: Thoughts on the systray II.
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2005-04-16 17:44:45
Message-ID: 200504161144.59629.aseigo () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Saturday 16 April 2005 08:00, LiuCougar wrote:
> Because it requires a lot of other logic/codes, and skim has its own
> plugin system.

you wouldn't have to put the application into the applet; it's just a question 
of what the interface to skim is.

> "reparent it (in-process even) to another
> window": is the "another window" in a separate process or in the same
> one?

it could be either. you could launch a new process or create a window in the 
same process. 

> kicker applets can be achieved in a
> standalone application (another process, like skim) just like
> implementing a system tray icon: what required is to only sub-class a
> special class

this would be highly limited in capability unless we use XEmbed which is not 
something i'm interested in doing.

> What's more, if user does not have kicker running, he 
> can still use skim as a standalone app.

you can run applets outside of kicker as standalone applications using 
appletproxy

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

[Attachment #5 (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


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