offline stuff is p
, so I thought I'd write a fun lil wrapper for IndexedDB 
http://github.com/lrlna/nanoidb
-
-
Replying to @_lrlna
Hey! Nice lib, wanted to ask, how it connects to choo (


)1 reply 0 retweets 0 likes -
Replying to @victor_suzdalev
Hi!
choo handles your rendering, and this would just work as a module to do your offline stuff. In other words -- totally compatible!1 reply 0 retweets 0 likes -
Replying to @_lrlna @victor_suzdalev
I was considering it making it work with app.use(), but that would have been a bit choo specific
1 reply 0 retweets 0 likes -
Replying to @_lrlna
I think there's no need to, if choo has way to subscribe to state changes (I believe it does)
1 reply 0 retweets 0 likes -
Replying to @victor_suzdalev
You probs won't be able to keep a true sync between a choo state and IndexedDB, but a partial state is def possible.
1 reply 0 retweets 0 likes -
Replying to @_lrlna
And why not the full state? I understand, that I'd rather not save viewstate for some things, but don't get why it isn't possible
1 reply 0 retweets 1 like -
Replying to @victor_suzdalev
i'd think the state would be tied to something like an xhr request / input field for example and only updated with idb when necessary
1 reply 0 retweets 1 like -
Replying to @_lrlna @victor_suzdalev
tbh, i also don't know choo internals that well; i think
@yoshuawuyts probably knows about that state obj a lot more than i
1 reply 0 retweets 1 like
Yeah so while def possible to sync it all, you'll be dealing with state in 3 places, and schema changes. Could def try tho, but it's tricky
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.