If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Also cool is that GTK+ has the multiple backend support now, so the fear that your GTK+ applications will only work with Wayland is gone. The same binaries can work on Wayland natively or work with X11 for people wanting X-style network transparency.

Also cool is that GTK+ has the multiple backend support now, so the fear that your GTK+ applications will only work with Wayland is gone. The same binaries can work on Wayland natively or work with X11 for people wanting X-style network transparency.

Yeah, this could have potentially been a big problem. Luckily the multiple backend work made it into GTK 3.0 (which is getting close to release now) or it may have had to wait until the next major version, which could have been two or three years away...

Wouldn't OpenGL in addition to OpenGL ES allow for greater performance in things like high graphics gaming and what not?

Afaik when you use OpenGL in your app you don't need Wayland's blessing since OpenGL draws directly to the screen. At most Wayland could tell your app _where_ to draw, but Wayland itself doesn't participate in the drawing process of the apps which use OpenGL for (their own 2D/3D) rendering stuff.

Wayland as in "display manager" as opposed to "new standard" does use "OpenGL ES" instead of "OpenGL" to render stuff but that is simply because it wants to run on mobile devices with as little changes as possible and unless you mean OpenGL 4.x there's virtually no big performance difference between OpenGL 1x-3x and OpenGL ES 2.0.