Skip to content
This repository has been archived by the owner on Jan 6, 2022. It is now read-only.

Investigate UI element caching #250

Closed
2 tasks
yoshuawuyts opened this issue Feb 20, 2017 · 2 comments
Closed
2 tasks

Investigate UI element caching #250

yoshuawuyts opened this issue Feb 20, 2017 · 2 comments
Assignees
@yoshuawuyts
Labels
Priority: Medium Status: Available Type: Enhancement

Comments

@yoshuawuyts
Copy link
Contributor

As per #152, the app sometimes spins when lots of updates happen (e.g. network events). We should probably investigate caching elements.
@yoshuawuyts yoshuawuyts added this to the Release 2017-02-28 milestone Feb 20, 2017
@yoshuawuyts yoshuawuyts self-assigned this Feb 20, 2017
@yoshuawuyts yoshuawuyts mentioned this issue Feb 20, 2017
Closed
2 tasks
@yoshuawuyts
Copy link
Contributor Author

We fixed a lot of the perf issues here; moving to priority medium. Gonna build a component system first and move to less files before digging into this again.

@yoshuawuyts yoshuawuyts removed this from the 2017-02-28 milestone Feb 27, 2017
@yoshuawuyts yoshuawuyts mentioned this issue Feb 27, 2017
Closed
5 tasks
@yoshuawuyts
Copy link
Contributor Author

I think we can close this; we don't have any pressing perf issues right now and I'm sure there's always room to improve. New choo should make it v. easy to debug perf also, sooooo closing ✨

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@yoshuawuyts yoshuawuyts

Labels
Priority: Medium Status: Available Type: Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yoshuawuyts