I think something IO like is very wanted, but should be able to handle complex use cases like parallax too
-
-
I think you’re talking about Compositor Worklets and possibly Paint Worklets, too.
1 reply 0 retweets 1 like -
perhaps. I've not investigated either yet. Does compositor have a reference implementation?
2 replies 0 retweets 0 likes -
paging
@DasSurma, since he’s made demos, talks and that.1 reply 0 retweets 1 like -
Replying to @aerotwist @Runspired and
It’s due to land in Canary, soon. For now, there’s only a polyfill:https://github.com/GoogleChrome/houdini-samples …
1 reply 0 retweets 3 likes -
Replying to @DasSurma @aerotwist and
timing / restricted purpose means this is good for parallax, still bad for occlusion/recycling.
1 reply 0 retweets 0 likes -
Replying to @Runspired @DasSurma and
the "is this HIFI" debate is interesting. There are competing needs here & this is grey middle /1
1 reply 0 retweets 1 like -
Replying to @Runspired @DasSurma and
needs to be frame aware, doesnt need every frame: however, how often depends on content size /2
1 reply 0 retweets 0 likes -
Replying to @Runspired @DasSurma and
also needs to be able to track items outside the viewport, but can do so with lower fidelity /3
2 replies 0 retweets 0 likes -
: IO let's you track outside viewport. Not my first API design rodeo ;-)
2 replies 0 retweets 0 likes
sounds like you want to be able to express multiple "thresholds" at diff priority levels
-
-
-
: what's cheap/expensive in engines is non-obvious. Make sure IO doesn't do what you need first
0 replies 0 retweets 0 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.