Refactor reactivity - Githubissues

zaviermiller / zephyr

WIP framework

MIT License

2 stars 0 forks source link

Refactor reactivity #1

Open zaviermiller opened 3 years ago

zaviermiller commented 3 years ago

Currently, there is neither an efficient tree diffing algorithm nor any dep tracking. Dep tracking may remove need for fast diffing.

TODO:

[x] props work w new system
[x] track which part of node is in use?
[x] mutators and calculators

zaviermiller commented 3 years ago

basics and props work w zaviermiller@2444fa7c390f759253ba22b9638fed8b69783065. need to figure out state mutators and calculators. ideally theyre cached somehow, but the structs are getting pretty big already. well see.

zaviermiller commented 3 years ago

i dont LOVE the api, but i think it is clear while still being pretty simple to use, which is very hard to do lol

zaviermiller commented 3 years ago

pretty sure mutators and calculators work!! will test further. need to do:

[x] reactive int
[x] reactive bool
[ ] reactive byte/rune?
[x] reactive arrays
[ ] reactive maps
[ ] "queue smooshing" or whatever

zaviermiller commented 3 years ago

Been working a lot on the reactivity so that it works well with all the stuff. not sure how methods will work tho, unfortunately. it looks like maybe mutators wont be reactive? so they just update data, and then calculators are reactive and that's how you access data.