Wayland protocols

[Martin Gräßlin]

On Tuesday 19 August 2014 17:00:48 you wrote:
> 2014-08-18 9:37 GMT+02:00 Ivan Čukić <ivan.cukic at kde.org>:
> > On Monday 18 August 2014 09:22:03 Martin Gräßlin wrote:
> >> On Monday 18 August 2014 09:02:07 Pier Luigi wrote:
> >> > > Activities should probably be also exposed to the kf5_window
> >> > > interface?
> >> > 
> >> > What do you need for activities?
> >> 
> >> @Ivan: that falls into your domain - what do you want?
> > 
> > Apart from a list of activities (like we currently have), we need some way
> > to keep SLC alive.
> 
> Can you elaborate, please?
> 
> > Somehow, a window (through libkactivities) needs to be able to tell that
> > it
> > contains a document (or more than one, and which one is the currently
> > focused one). Currently, this is done using the window ids that are
> > reported back to the activity manager daemon which keeps track of them.
> 
> I'm not familiar with kactivities but a grep for winId reveals that it
> is used by ResourceInstancePrivate::registerResourceEvent, but I don't
> understand what does it need to communicate to the compositor.
> Windows still has winId() on Wayland, right @Martin?

at least KWin internal they will still have a winId - at least as long as 
Toplevel has not been refactored. I don't know how it looks on the outside 
world, or what Qt provides when accessing QWindow::winId() on platform 
wayland.

Cheers
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20140820/af6ad471/attachment.sig>