Re: Sending EGL headers updates to Khronos

2011-07-29 Thread Kristian Høgsberg
On Thu, Jul 28, 2011 at 8:42 AM, Daniel Nicoara dnico...@chromium.org wrote:
 Hello,
 Are there any plans in sending the EGL header changes (egl.h, eglplatform.h,
 ...) to Khronos? Or are the changes sent by mesa devs once the new stable
 release of mesa is out?

We're only using a couple of new EGL extensions: the
EGL_WL_bind_wayland_display and the surfaceless extensions.  We're not
ready to standardize the bind_wayland_display extension just yet, and
I think we'll stop relying on surfaceless and just make a dummy
pbuffer instead.  Most of the Wayland/EGL integration is in defining a
new native platform for EGL, which is how we create EGL displays for
Wayland displays and EGL surfaces for Wayland surfaces.  It's pretty
common for EGL vendors to have their own custom window systems, and
for now I'm not planning to push for Wayland to become an official
window system.

Kristian

 Thank you,
 Daniel Nicoara
 ___
 wayland-devel mailing list
 wayland-devel@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/wayland-devel


___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel


Re: client side decorations

2011-07-29 Thread Dana Jansens
Nothing has been said on this thread in some time, but I'd like to raise
another issue.

Clients have a menu or other means by which they access window manager
functions.  Things like move to desktop 2.  However this assumes a *lot*
about the desktop model being used by the compositor, and fixes it to
whatever the toolkits decide.  It would not be possible to cleanly make a
compositor which used any other way to manage windows.

Tiling is one good example, the tasks used in kde4 are another.

I was a strong believer in CSD until I realized I don't want to have to
change the toolkit to make a new compositor feature usable/visible.

On Mon, May 9, 2011 at 10:52 PM, andre.knis...@gmx.de
andre.knis...@gmx.dewrote:

 Actually, I think Iskren made a very important point. To take this one step
 further: with CSD, we can't force the client to stop drawing the decoration,
 we can only tell the client that it should. So we can assume Chrome having a
 decoration for example, what shouldn't be possible in a tiling WM.
 Together with the other things he said, it would be almost impossible to
 get a useable/useful tiling WM with CSD.
 To the shortcuts discussion: do you really want every user to remember
 shortcuts to use his desktop? This would be a huge step backwards for the
 process of getting Linux on the desktop. Everything the average user wants
 to do must be doable within the UI, and closing/moving dead windows out of
 the way belongs to this.

 André

 - Reply message -
 Von: Daniel danl...@terra.es
 Datum: Mo., Mai. 9, 2011 23:29
 Betreff: client side decorations
 An: Bill Spitzak spit...@gmail.com
 Cc: Høgsberg k...@bitplanet.net, Peng Huang shawn.p.hu...@gmail.com,
 Sam Spilsbury smspil...@gmail.com, Mike Paquette 
 paquette...@gmail.com, wayland wayland-devel@lists.freedesktop.org, 
 mal...@lavabit.com, krist...@freedesktop.org, microcai 
 micro...@fedoraproject.org


 El dg 08 de 05 de 2011 a les 09:47 -0700, en/na Bill Spitzak va
 escriure:
 
  Though it is possible, I don't like the idea of clients sending hints
  about what areas are the close box or window border, since it implies
  there are such concepts as title bar and close box. The compositor
  can just have clicks anywhere raise and move the non-responsive
  window, and lots of clicks (indicating user frustration) pop up a box
  offering to kill the program. On Linux, since it is standard,
  compositors can also have Alt+click always raise/move windows, and alt
  +right click pop up a menu of compositor-side window actions.
 

 This would be actually a good way to handle it. Use an special mode or
 tool, a la xkill, to deal with stuck applications. It can take the form
 of an special key/mouse combination, gestures, or as I said before, an
 external tool like xkill. Note that it needs not be limited to killing,
 but could do any other thing, like minimizing, sending to another
 virtual desktop, etc.



 ___
 wayland-devel mailing list
 wayland-devel@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/wayland-devel



 ___
 wayland-devel mailing list
 wayland-devel@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/wayland-devel


___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel