Type: Posts; User: Krejzi; Keyword(s):
VDPAU has been part of gst-plugins-bad for some time now. It's just that it still isn't good enough :)
What is this? No official release anouncement, no git tag, no release tarball ... It looks to me that it is indeed "Prepare for 1.3.0 release (in near future)" and not "Release 1.3.0" ...
This might be bad for Wayland. Current QtWayland implementation requires Qt to be built with OpenGL ES2 support even on desktops.
Upstream bug has been present for more than a month, but none seems to have noticed it untill RH bug was submitted.
It will, but the support for sub-surfaces needs to be implemented in clutter-gtk first. There is some initial implementation lying in wip/wayland branch, but it hasn't been touched in 2 months or so.
Not to mention that there is no Mir dependant code in these patches, ie no mir egl platform.
I took some time to look at VLC output code. VLC OpenGL is actually GLX implementation. You still need Wayland Surface to draw into it. And while it has EGL module too, you need Wayland specific...
Nah, but in this case it would be very odd. Imagine KDE moving away from the KDE Frameworks to something else ... I can't imagine any of mentioned.
Anyways, there seems to be active gtk3 branch...
According to , R600 is missing GL_ARB_texture_multisample, Geometry Shaders and GLSL 1.50 for GL 3.2 compliance, while for 3.3 all extensions seem to be implemented except maybe some GLSL 3.30...
Complete OpenGL 3.2/3.3 support is only for Ivy Bridge and Haswell (gen7+). Sandy Bridge is still stuck at 3.1. Geometry shaders aren't yet done for SNB. See...
Wouldn't it be ironic for GIMP to move away from GIMP Toolkit?
Is this official enough?
Clicking on "GTK stable" will take you to the very same page I linked to in previous post.
Also, if you look closely, you can...
You obviously didn't look very hard:
I think I need a degree in psychology to understand why do you do all this. Does it really matter if GNOME kills KDE or vice versa? As long as there's one last developer in there, it isn't dead.
It is. Only thing it broke was gstreamer-vaapi and clutter-gst hardware decoder support (which uses gstreamer-vaapi) since it used experimental library from gst-plugins-bad, which got removed in 1.2...
It's actually webkit2gtk, the GTK+ port of WebKit2. One of the differences is that it uses a seperate process for plugins, like Mozilla does with Gecko (plugin-container), so GTK+2 plugins can work...
So does WebKitGTK+ and Epiphany (minus few features that still need to be worked out).