RandR 1.3 additions?

[Keith Packard]

On Tue, 2008-01-22 at 09:54 -0500, Alex Deucher wrote:

> For one, most users don't even
> seem to know that output properties exist.

That's a UI issue; the xrandr CLI app isn't supposed to be the end-state
of design in this space...

>   Then the setup is
> different across all drivers, and finally a lot more common state that
> should be in the server (which actually has the full view) gets pushed
> into the drivers which have to figure out what exactly the user wants
> based on verious separate calls.

Standardizing the properties and providing better DIX-level support
should fix this.

> We could initially expose it as an output
> property, but then add some sort of "official" protocol for it once we
> sort it out.

Let's keep the protocol and implementation ideas separate; we can put
abstractions into the server which are exposed as properties in the
protocol.

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg/attachments/20080122/4478cad2/attachment.pgp>