Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[idea] use a "copy" shader to solve some cases #47

Closed
gre opened this issue Jan 24, 2016 · 3 comments
Closed

[idea] use a "copy" shader to solve some cases #47

gre opened this issue Jan 24, 2016 · 3 comments

Comments

@gre
Copy link
Owner

gre commented Jan 24, 2016

Here are the cases:

we might be able to do this from gl-react. Also after this, the width and height of the root node should probably lead more the GL Surface (if it's not already the case).

such a "copy" shader is probably not the most efficient idea, but i'm not seeing another way in OpenGL/WebGL. we need to be sure to only enable it if it's required.

@gre gre changed the title [idea] use a "copy" copy to solve some cases [idea] use a "copy" shader to solve some cases Jan 24, 2016
@gre
Copy link
Owner Author

gre commented Feb 15, 2016

need to benchmark solving the resize with a copy shader VS solving it with UIView's transform

@gre
Copy link
Owner Author

gre commented Feb 15, 2016

(will still need copy shader for the second use-case though)

@gre
Copy link
Owner Author

gre commented Feb 16, 2016

just a reminder that later we will have to introduce the feature to set the interpolation of FBOs (so you can switch between linear and none)

@gre gre closed this as completed in 0253046 Feb 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant