Yes, that's right. There isn't any way to have an OpenGL 2/3+ dual compatible codebase without putting if/else statements everywhere, and probably doubling the size of many modules! This would be a huge mess to support, and I don't think it's worth it. A smaller, cleaner, codebase is always best!
Currently, old versions of pyglet remain available for download from bitbucket. If/when we decide to migrate to OpenGL 3+, we would have to make note of this. The old version could be maintained as pyglet-legacy (or something like that) as long as someone wants to maintain it. OpenGL agnostic improvements could be backported if someone wants to do so. On Monday, June 5, 2017 at 6:24:02 AM UTC+9, [email protected] wrote: > > When you say losing support, are you referring to graphics cards that > support less than GL3.x? Not that I necessarily have a problem with that, > it would be nice to have a legacy backup of the current pyglet version > floating around if thats the case though. > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
