Refreshing the page shouldn't delete current work. about quickmockup HOT 5 OPEN

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)

from quickmockup.

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?

from quickmockup.

from quickmockup.

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?

from quickmockup.

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)

from quickmockup.