Skip to content
This repository has been archived by the owner on Apr 25, 2018. It is now read-only.

Batch property updates together on animation frame #73

Open
garbles opened this issue Apr 12, 2016 · 4 comments
Open

Batch property updates together on animation frame #73

garbles opened this issue Apr 12, 2016 · 4 comments

Comments

@garbles
Copy link
Owner

garbles commented Apr 12, 2016

Context:

Currently all properties are added/changed/removed from their respective nodes immediately. It can be better optimized by batching these changes together on animation frame.

Ideally the strategy should account for scenarios where multiple changes to single prop happen between animation frames. (e.g. if prop A was added and then removed, no action would be taken).

@jadbox
Copy link
Contributor

jadbox commented Apr 14, 2016

Where do you recommend that functionality to exist? If you point me to the right critical point where vtree is redrawn, I'll look into making a throttle-by-frame behavior.

@garbles
Copy link
Owner Author

garbles commented Apr 15, 2016

I'm pretty sure that this needs to have some batching mechanism. Not exactly sure how that looks right now.

@garbles
Copy link
Owner Author

garbles commented Apr 15, 2016

To be clear, there is no point where the vtree is completely redrawn. There is no notion of a virtual tree anymore.

@geekytime
Copy link
Contributor

geekytime commented Apr 26, 2016

Would this help to improve performance (or at least the perception of performance) for large numbers of DOM elements?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants