localstorage usage and reasons

[jayrox]

Hey there, trying to get and understanding of the localstorage usage and the reason behind it. Care to shed some light? Thanks!

[jhvst]

The localstrorage works as a backup for posts. So, if you have the edit or new page opened and type something in, you may close or refresh the page and the browser will preserve the writings. So if your browser happens to force shutdown or something similar, you wont have to start writing from the start.

Some similar software like Gmail and Medium use AJAX saving instead, but I dont think that is necessary with Vertigo.

Hope this answers your question.

[jhvst]

Did my explanation help at all? I can make a gif or short HTML5 video if you did not follow me trough.

[jayrox]

Yeah, it makes sense. I've been looking at a different mark-down editor
using polymer.

http://robdodson.me/mark-down/components/mark-down/

On Wed, Nov 26, 2014 at 4:48 AM, Juuso Haavisto notifications@github.com
wrote:

Did my explanation help at all? I can make a gif or short HTML5 video if
you did not follow me trough.

—
Reply to this email directly or view it on GitHub
#21 (comment).

[jhvst]

I admit that the current Markdown implementation is less than ideal. That being said, it would be great if you could one day convert from HTML to Markdown using Go, but implementing it doesn't seem simple.

Anyway, great to see that you've taken a different approach in utilizing Vertigo! I personally have only some experience in Ember.js, which I initially though I'd use to build an application on top of the current code. Ironically, I haven't had the time to make it happen, but I hope I can gather some time during the holidays. I'd be mainly interested to see if I could find something worth improving in the Go code.

If you have find anything worth of refining, I'd be happy to know more!

[jayrox]

you can see my install at nobatteries.net

On Sat, Nov 29, 2014 at 6:10 AM, Juuso Haavisto notifications@github.com
wrote:

I admit that the current Markdown implementation is less than ideal. That
being said, it would be great if you could one day convert from HTML to
Markdown using Go, but implementing it doesn't seem simple.

Anyway, great to see that you've taken a different approach in utilizing
Vertigo! I personally have only some experience in Ember.js, which I
initially though I'd use to build an application on top of the current
code. Ironically, I haven't had the time to make it happen, but I hope I
can gather some time during the holidays. I'd be mainly interested to see
if I could find something worth improving in the Go code.

If you have find anything worth of refining, I'd be happy to know more!

—
Reply to this email directly or view it on GitHub
#21 (comment).

[jhvst]

I guess this can now be considered resolved, so I'll close this issue. Feel free to re-open if you have additional questions related to the topic.