Highlevel explanation

[instant-markdown]

Highlevel explanation

[suan]

The meat of the logic is in the backend code: http://github.com/suan/instant-markdown-d Do you want an explanation on that, this vim plugin, or both?

Also, if you're diving into the code cause of instability issues, I'm aware of those, and am working on a more stable and flexible backend which will also be in pure ruby (easier to install) You can follow the progress here: https://github.com/suan/instant-markdown-d/tree/rate_limiting

[oivvio]

I'm just curious about the communication between the three parts, vim, the browser and the node instance. How is that set up?

[suan]

It's roughly like this:

1. When you open a markdown file in vim, it starts the backend server
2. when the backend server starts, it opens a browser tab and a websocket connection
3. When the buffer for the markdown file is changed in vim, the plugin sends a PUT request to the server with the new markdown content
4. The server converts to to HTML and sends it over the websocket
5. The javascript in the browser tab replaces the old HTML content with the new one
6. When you close/leave the vim buffer, it sends a DELETE request to the server
7. The server sends a message over the websocket it to close the browser tab, and then shuts itself down

[oivvio]

Nice!