openframeworks / openframeworks/openFrameworks
Replacing GLSurfaceView with TextureView
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
Hi everyone,
I was wondering if it's a good idea to replace Android GLSurfaceView with GLTextureView. The advantages of replacing this is that multiple views can be combined. after this modification we can create a mapKit for Android and combine it with a native GUI.
Here's an example link:
https://github.com/eaglesakura/gltextureview/tree/issue/1/master
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names Android GLSurfaceView and the proposed GLTextureView, but no repository files, tests, or entry points. First determine where the Android rendering view is implemented and assess the linked GLTextureView example; done would require a decided replacement approach that supports combining the rendering view with native GUI elements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp
- Domain
- computer-graphics, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100