Drew DeVault

Bump, expressing support for `a, b: c`

This is deliberately left vauge. The compositor can decide what values to use in any manner it chooses.

When I put this in, I figured that new clients would look around at anything which does something similar and use the same namespace.

Honestly, in retrospect I regret adding the namespace. The original intention was to allow the compositor to resolve z-ordering issues with clients by magically knowing which one should go on...

What are some of those use-cases? I suppose it's useful in the same way app-id is useful, but there's little value in standardizing that.

z-indexing only works if the person assigning the indicies already knows about everything being ordered.

I think I'm still -1 on this protocol tbh.

>I'd just like to add my support for this as a user. I constantly switch between three languages that require distinct layouts, and it's super helpful to have my status...

Send patch?

My gut reaction to this protocol is to be cautiously optimistic, emphasis on cautiously. I think a good protocol for this may be hard to write. >Workspaces on multiple outputs...