Re: [protocol PATCH v2 1/2] add parameters for set_fullscreen

2012-01-12 Thread Pekka Paalanen
On Wed, 11 Jan 2012 23:52:44 +0800 Juan Zhao wrote: > > On Wed, 2012-01-11 at 10:10 +0200, Pekka Paalanen wrote: > > The scaling modes apply only to the case, where the client decides to > > attach a buffer of different size than what the compositor suggests > > (which is the size of the assign

Re: [protocol PATCH v2 1/2] add parameters for set_fullscreen

2012-01-11 Thread Juan Zhao
On Wed, 2012-01-11 at 10:10 +0200, Pekka Paalanen wrote: > "None" means no need for the compositor to do any work here, it is > useful > > in case that client want to re-layout his UI components to > fullscreen. > > Re-layout means rearrange the contents of that client other than > scaling. >

Re: [protocol PATCH v2 1/2] add parameters for set_fullscreen

2012-01-11 Thread Juan Zhao
On Wed, 2012-01-11 at 10:10 +0200, Pekka Paalanen wrote: > > > > > The position of the surface on an output is not defined here, > > > possibly allowing the video driver to scan out a surface smaller than > > > the video mode. > > I'm not sure I catch your idea here. I would like to make it on

Re: [protocol PATCH v2 1/2] add parameters for set_fullscreen

2012-01-11 Thread Pekka Paalanen
On Tue, 10 Jan 2012 13:26:13 -0800 Bill Spitzak wrote: > Pekka Paalanen wrote: > > > "none" means the application does not care what method a compositor > > uses, so the compositor would probably choose either the cheapest > > (fill? no-fill?) or the best desktop-integrated user experience (scal

Re: [protocol PATCH v2 1/2] add parameters for set_fullscreen

2012-01-11 Thread Pekka Paalanen
On Wed, 11 Jan 2012 15:07:05 +0800 Juan Zhao wrote: > Thank you very much for your review. :) > > On Tue, 2012-01-10 at 13:42 +0200, Pekka Paalanen wrote: > > > These could also use commentary on what they mean. My suggestion of them > > is the following. > > > > "none" means the application d

Re: [protocol PATCH v2 1/2] add parameters for set_fullscreen

2012-01-10 Thread Juan Zhao
Thank you very much for your input. On Tue, 2012-01-10 at 13:26 -0800, Bill Spitzak wrote: > > "scale" is for preferring scaling in the compositor, the application > > really would like to fill the whole screen, even if it renders a buffer > > that is too small. The compositor might (be configure

Re: [protocol PATCH v2 1/2] add parameters for set_fullscreen

2012-01-10 Thread Juan Zhao
Thank you very much for your review. :) On Tue, 2012-01-10 at 13:42 +0200, Pekka Paalanen wrote: > These could also use commentary on what they mean. My suggestion of them > is the following. > > "none" means the application does not care what method a compositor > uses, so the compositor would

Re: [protocol PATCH v2 1/2] add parameters for set_fullscreen

2012-01-10 Thread Bill Spitzak
Pekka Paalanen wrote: "none" means the application does not care what method a compositor uses, so the compositor would probably choose either the cheapest (fill? no-fill?) or the best desktop-integrated user experience (scale?) method. I think the default will have to be "fill". My guess is t

Re: [protocol PATCH v2 1/2] add parameters for set_fullscreen

2012-01-10 Thread Pekka Paalanen
On Mon, 9 Jan 2012 22:50:20 +0800 juan.j.z...@linux.intel.com wrote: > From: Alex Wu > > framerate: the expected framerate which will be used as refresh value to > choose display mode. > flags: indicate how to deal with resolution dismatch. > support three methods: > "SCALE" means the

[protocol PATCH v2 1/2] add parameters for set_fullscreen

2012-01-09 Thread juan . j . zhao
From: Alex Wu framerate: the expected framerate which will be used as refresh value to choose display mode. flags: indicate how to deal with resolution dismatch. support three methods: "SCALE" means the compositor will scale the surface to the fullscreen. "FORCE" means changing the scr