I've finally built my converter for Observable not...
# two-minute-week
t
I've finally built my converter for Observable notebooks to Lopecode aka Jumpgate. Feels good (blusky post). Its 2:45 sorry, but it gives a full project overview. • Github repository • Observable collection
m
Looks awesome. Since it's a single file and can be worked on offline, I assume it's also using the same file for storing the updated state. Is that correct? If so then I'm wondering how have you solved the windows write lock that prevents opened files from being written to.
t
no to save state you have to reserialize, so its a new file (the timestamp is appended to the filename). If I added a proper history feature I would use indexdb so then you could replay edits on startup, but thats not really a priority ATM. Next priority will be making the authoring experience actually good and converting all my notebooks over.