Author here! Didn't see this coming - time to update all the documentation :)
Thanks for the comments, everyone, and feel free to ask questions here.
Some background: I started working on Vimflowy after a conversation with a friend. I'd seen many similar apps, but the vim part was important to me. I've tried the spacemacs org layer, but it didn't work out. My friend had a huge document on Workflowy which started getting laggy for him. Vimflowy lazy loads, and deleting and pasting large subtrees is efficient, which went well with the vim concept. So it started out being a tool mainly for me and my friend. At this point, I'd be happy if others found Vimflowy useful, though I don't have grand aspirations for it. I've tried to make it so that developers can customize it to their liking without much trouble. I would consider making a second set of non-vim bindings out of the box if enough people seem to like it - it'd be relatively easy to implement, but the space seems crowded enough as is.
This thing is amazing, and so close to something I've been wanting for a while now that it's like you've been eavesdropping! Thanks so much for making it available for others to use and learn from.
I'm looking forward to studying the code to learn how you built it. If you ever have time, I think a bit of architectural overview / design discussion would make a nice addition to the README.
Yeah, I'd add it if it helps other developers get started with the code base. Happy to chat with you about it, though, too! Feel free to email me.
That said, I'm not sure there's anything particularly interesting or good about the architecture though - in fact certain things I know are probably badly designed
Great job on this! It has a good amount of polish that you should be proud =)
Interesting that Workflowy has been laggy for your buddy. I've been using it since 2011 and only tend to have lag problems only when using it in IE (or Edge now) when at work, as well as Firefox for some reason. Safari and Chrome have virtually no problems with the size of my document.
The lag was for initial page load, and is just a historical footnote, probably. Here's what I dug up from past chats: In May 2015, for a 250k bullet document, it used to take more than 5 minutes. Apparently by July, it was down to 30s-60s. I'm sure it's much better now!
Thanks for the comments, everyone, and feel free to ask questions here.
Some background: I started working on Vimflowy after a conversation with a friend. I'd seen many similar apps, but the vim part was important to me. I've tried the spacemacs org layer, but it didn't work out. My friend had a huge document on Workflowy which started getting laggy for him. Vimflowy lazy loads, and deleting and pasting large subtrees is efficient, which went well with the vim concept. So it started out being a tool mainly for me and my friend. At this point, I'd be happy if others found Vimflowy useful, though I don't have grand aspirations for it. I've tried to make it so that developers can customize it to their liking without much trouble. I would consider making a second set of non-vim bindings out of the box if enough people seem to like it - it'd be relatively easy to implement, but the space seems crowded enough as is.