Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Remove rarely used GLConnection stuff in flow. #3440

Merged
merged 1 commit into from
Feb 24, 2017

Conversation

chinmaygarde
Copy link
Member

I had added this initially as a means of making it easier to deal with OpenGL directly in Flow. However, we are moving away from dealing with the client rendering APIs directly. Instead, delegating everything to Skia. Besides, we only ever used this to log the GPU description in case of context setup failures. This has not proved to be useful so far. Also, having this in place is making it difficult to remove all dependencies on GL in Shell.

I had added this initially as a means of making it easier to deal with OpenGL directly in Flow. However, we are moving away from dealing with the client rendering APIs directly. Instead, delegating everything to Skia. Besides, we only ever used this to log the GPU description in case of context setup failures. This has not proved to be useful so far. Also, having this in place is making it difficult to remove all dependencies on GL in Shell.
@jason-simmons
Copy link
Member

LGTM

@chinmaygarde chinmaygarde merged commit 2868251 into flutter:master Feb 24, 2017
@chinmaygarde chinmaygarde deleted the gl_conn_remove branch February 24, 2017 00:02
goderbauer pushed a commit to goderbauer/engine that referenced this pull request Mar 9, 2017
I had added this initially as a means of making it easier to deal with OpenGL directly in Flow. However, we are moving away from dealing with the client rendering APIs directly. Instead, delegating everything to Skia. Besides, we only ever used this to log the GPU description in case of context setup failures. This has not proved to be useful so far. Also, having this in place is making it difficult to remove all dependencies on GL in Shell.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants