Refreshing the page shouldn't delete current work.

[simonv3]

If you refresh the page for whatever reason, you shouldn't lose the current work. Can it be stored in localstorage or in the user's cache?

[jdittrich]

I sympathize with the idea but as I currently see it, it would mean one would need to implement a "files"-in-localstorage-management-part of the app (or a save-to-url etc), which would sort of double the saving-as-files-part (which I deliberatly choose as means of storing data)

You get the warning, when you reload, don't you? (I know this is not ideal, but that best for now)

[simonv3]

Yeah, totally get the warning, and also get the complexity factor. If we switch to an MVC then an abstraction of the objects, as a nested json data object or something similar, which would be used to generate the relevant DOM would also work?

[paulproteus]

FWIW, if quickMockup is ported to Sandstorm, I imagine that people are going to randomly reload it frequently for any of a number of reasons, like their Internet connection breaking and them wondering if Sandstorm is stuck and so they reload the page. I know I do that frequently. Having said that, if quickMockup on Sandstorm autosaves to disk on the server side, then that addresses this problem.

[simonv3]

I think a higher level question of saving to disk is - is this a webapp or a standalone app that just happens to run in the browser?

[jdittrich]

webapp or a standalone app....

It is a standalone app that happens to run in the browser. Or, to be more specific, it is an unhosted app. Which means it still can get save-to-localstorage.

their Internet connection breaking and them wondering if Sandstorm is stuck

Interesting – it should not be possible that quickMockup is slow due to the connection, since everything is on the client side. (But naturally, they may still reload)