Re: Thoughts on getting surfaces to appear on the right output

2014-05-02 Thread Bill Spitzak
On 05/02/2014 03:49 PM, Neil Roberts wrote: 1. It would seem more useful for the desktop shell to send some info about how the client was launched in environment variables. Yes, maybe it would be cleaner to agree on some protocol for the parent process to send the information directly to the ch

Re: Thoughts on getting surfaces to appear on the right output

2014-05-02 Thread Neil Roberts
Bill Spitzak writes: > 1. It would seem more useful for the desktop shell to send some info > about how the client was launched in environment variables. Yes, maybe it would be cleaner to agree on some protocol for the parent process to send the information directly to the child. I'm not sure ab

Re: Thoughts on getting surfaces to appear on the right output

2014-05-02 Thread Bill Spitzak
Two comments on the proposal: 1. It would seem more useful for the desktop shell to send some info about how the client was launched in environment variables. The client may want to do other reactions besides just placing it's window, and this will work for clients that do not want to use the

Thoughts on getting surfaces to appear on the right output

2014-05-02 Thread Neil Roberts
Hi, Currently Weston has a problem that it always puts new surfaces on the same output as the one the first pointer is in. I guess the idea is that most of the time surfaces are created as a result of mouse events and there is usually only one pointer so it works most of the time. However of cours

Re: [PATCH] protocol: Change wl_surface.damage to be in buffer coordinates.

2014-05-02 Thread Jason Ekstrand
Bump. I also just added this to the bug-tracker: https://bugs.freedesktop.org/show_bug.cgi?id=78190 --Jason Ekstrand On Thu, Feb 27, 2014 at 12:37 AM, Pekka Paalanen wrote: > On Wed, 26 Feb 2014 21:13:16 -0600 > Jason Ekstrand wrote: > > > Technically, wl_surface.damage is supposed to be cal

Re: New to Wayland, Need suggestion on a starting point

2014-05-02 Thread Jason Ekstrand
You could also go after this one: https://bugs.freedesktop.org/show_bug.cgi?id=77769 It shouldn't be too bad if you just follow along with what's done for mouse support. --Jason Ekstrand On Fri, May 2, 2014 at 7:08 AM, Pekka Paalanen wrote: > On Fri, 02 May 2014 17:11:34 +0530 > Srivardhan w

Re: [PATCH weston v2] screen-share: Allow fullscreen shell command to be configured

2014-05-02 Thread Jason Ekstrand
Yeah, this looks better. Reviewed-by: Jason Ekstrand On Fri, May 2, 2014 at 4:01 AM, Andrew Wedgbury wrote: > I've updated this based on comments, simplifying the command handling. > > Currently the screen-share module uses a hard-coded command to start the > fullscreen shell server. This pat

Re: New to Wayland, Need suggestion on a starting point

2014-05-02 Thread Pekka Paalanen
On Fri, 02 May 2014 17:11:34 +0530 Srivardhan wrote: > Hi All, > > > > My name is Srivardhan Hebbar, and I'm active developer since 2008, working > for Samsung now. > > > > I am newbie FOSS developer and new to the world of Wayland. I want to > contribute to this project and want to star

New to Wayland, Need suggestion on a starting point

2014-05-02 Thread Srivardhan
Hi All, My name is Srivardhan Hebbar, and I'm active developer since 2008, working for Samsung now. I am newbie FOSS developer and new to the world of Wayland. I want to contribute to this project and want to start with few simpler contributions to understand the code better. I have lo

[PATCH weston v2] screen-share: Allow fullscreen shell command to be configured

2014-05-02 Thread Andrew Wedgbury
I've updated this based on comments, simplifying the command handling. Currently the screen-share module uses a hard-coded command to start the fullscreen shell server. This patch causes the module to read the command from the weston config file (from the "command" key in the "screen-share" secti

Re: [PATCH weston] screen-share: Allow fullscreen shell command to be configured

2014-05-02 Thread Andrew Wedgbury
Hi Jason, On Thu, 1 May 2014, Jason Ekstrand wrote: On Thu, May 1, 2014 at 9:00 AM, Andrew Wedgbury wrote: Currently the screen-share module uses a hard-coded command to start the fullscreen shell server. This patch causes the module to read the command from the weston conf