Shared OSD Service for KDE

todd rme toddrme2178 at
Wed May 12 17:19:01 BST 2010

On Wed, May 12, 2010 at 11:49 AM, Aaron J. Seigo <aseigo at> wrote:
> On May 12, 2010, Lubos Lunak wrote:
>> On Wednesday 12 of May 2010, John Tapsell wrote:
>> > Whatever the solution for the OSD, please check how it works for
>> > things like full screen flash.  When watching a youtube video etc in
>> > fullscreen and then scrolling the mouse wheel, the OSD popup causes
>> > flash to quit fullscreen mode.
>>  It's going to work like everything else with Flash - poorly. The
>> fullscreen handling in Flash is lame, anything new showing up will cancel
>> it, and I doubt we can do anything about it.
> here's a craaaazy idea:
> what if we put the OSD display into kwin? then, at least when compositing is
> on, kwin could display the OSD without actually creating a new window, just be
> painting it directly using a composite plugin?
> in the non-compositing case, then it could fallback to a regular window?
> this would result in something like:
> * OSD as a notification type in KNotify
> * a "well known" OSD D-BUs interface
> * if the D-Bus interface is registered, KNotify would send OSD requests to it
> * if it doesn't exist, then it just pops up a regular notification (or
> whatever)
> * KWin would register this D-Bus interface when started if it isn't already
> taken and then provide the actual OSD painting
> would that work?

There is a kwin plugin on that shows a clock using
compositing in the same way you describe here.  I tried it a while
back and it seemed to work, although I don't really use it.


More information about the kde-core-devel mailing list