Hi Timofonic, I may help answer some points.
> What OpenGL version is KiCad using currently? I fail to see it 2.1 is required https://github.com/KiCad/kicad-source-mirror/blob/2928cb741961d5529cb2e57a9917922d80366c93/common/gal/opengl/opengl_gal.cpp#L1529 > Can newer OpenGL features provide performance improvements too? > Would using a OGL->D3D wrapper be an issue? As far as I understand from the GAL implementation, on relation to performance, I believe it is already very well optimized, special with the latest bitmap text optimization. I believe if there are speed optimization may be on a more hi level layer, not on the low openGL implementation. What are the performance issues you experience? I worked with kicad for some time without a GPU, so the openGL (shaders) were implemented by MESA on CPU. It was workable if the CPU is good. On relation to the GPU and drivers, I believe the most problematic will be on Linux (for old GPUs that dont have driver support, eg: ATI) But on Windows, GPU manufacturers usually have a basic support of the driver for each GPU product. On other case, if there is any situation that doing the same thing with D3D will have a great improve over OGL, that may be too specific for some GPU and that situation should be a wast of time for kicad development IMO. Cheers, Mario Luzeiro ________________________________________ From: Kicad-developers [[email protected]] on behalf of Timofonic [[email protected]] Sent: 09 June 2016 19:52 To: [email protected] Subject: Re: [Kicad-developers] [PATCH] Legacy: delete and force middle button pan for GAL consistency I'm just a bad user but... Why isn't Legacy canvas ditched in the development branch and focus efforts in the GAL one exclusively? What about OpenGL and slow in certain platforms? What OpenGL version is KiCad using currently? I fail to see it. Damn, even MESA is getting OpenGL 4.3+ too. Can newer OpenGL features provide performance improvements too? Windows Intel graphics are known to have an awful OpenGL implementation. Would using a OGL->D3D wrapper be an issue? Would using a library like BGFX be an issue? Can the switch traits lots of coding and rewriting? What are the issues to massively remove all the cruft in KiCad code and develop by thinking in the future? What's going to happen with KiCad 5.0? Personally, I would prefer a new one with massive usability, performance and feature improvements than another small one if that slows the progress to make KiCad a lot better EDA tool for the future. _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
