[09:34] <duflu> anpok: Hangout?
[09:35] <anpok> omw .. strange connection problems..
[10:04]  * duflu follows the shiny things
[10:23] <greyback> alf__: hey, I recall that you did the refactoring to separate the rendering api from the renderer - was there ever a plan to implement an OpenGL rendering backend?
[10:56] <alf__> greyback: you mean OpenGL and not OpenGL ES 2.0?
[10:58] <alf__> greyback: If so, no plans at this point, but if/when the separation is finished it should be relatively easy to do. However, the separation effort is not in progress at the moment.
[11:04] <greyback> alf__: yeah
[11:04] <greyback> alf__: separation did not complete?
[11:05] <alf__> greyback: no, other higher priority tasks got in the way
[11:05] <greyback> alf__: ok
[11:05] <alf__> greyback: and I have no idea when we will get back to it
[11:05] <greyback> alf__: fair enough
[11:06] <alf__> greyback: is this just about linking with libGL vs libGLESv2 or do you need different behavior based on Desktop vs ES2?
[11:07] <greyback> alf__: I suspect the fact that Mir asks for GLES context, but Qt does GL with that context, is bad for older chips: (see https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1549455 and note the comments about bad unity8 performance and mesa complaints in comment 63)
[11:07] <greyback> alf__: the client problem is a separate issue, that I know.
[12:38] <mariogrip> any news on proprietary nvidia drivers working with mir?
[12:52] <anpok> mariogrip: hm i believe nothing new to share yet..