Fwd: [PATCH weston] xdg-shell: Make stable

[Bill Spitzak]

On 07/18/2014 09:55 AM, Jason Ekstrand wrote:

> I really like Jasper's "present" request solution to this problem. (It
> could probably also be called "attention").  If kwin wants to implement
> that as "move to the appropriate workspace and unminimize, then it can
> do that.  Otherwise, it could start flashing the task-bar icon or something.

I see no reason this can't be called "show" or "raise".

The *creation* of a surface does not mean that the compositor must show 
it. It could add a blinking "attention needed" task bar entry, just like 
this action. And the Kate editor is actually expecting "the same result 
as a new window", not "the window becomes visible". Therefore the 
request that is really wanted is "do something much like what happens 
when a window is first created".

I would add an event id to the request, so the compositor knows what 
event (if any) triggered it. This same request would be used in several 
situations, and the event and whether the window is visible can be used 
by the compositor to change the result:

1. It is implied when a surface is first created.

2. Clients use it to raise windows on clicks (note: the compositor 
CANNOT implement "raise on click" itself. If you think it can you are 
wrong).

3. Clients use it in response to other actions, as in the Kate editor above.

Compositors must cleanly and quickly ignore spurious requests, as some 
clients may send them in response to every click, or send extra ones 
after creating a surface.