PMario wrote: > > ... > Losing data in a shopping app isn't a big deal. It's nice that my > online-shop web-app can identify me automatically, if I visit the site > again. .. BUT it doesn't really matter if it doesn't. If I really need > something, I'll log-in again. ... If I don't log in again, I probably > didn't really need that stuff. .. GOOD ... money saved ;) >
> But if I lose 2 or more hours of refactoring work in tiddlywiki, this is a > big problem. It really hurts users. > Right. My issue is for frequent use is simply having some local universal method that works "out-of-the-box". The case use is specifically transient TW that hold data to select from for a few days by students. These are not persistent wikis. I played around with "local storage" to deliver that. In theory, naively, I thought it would be a "doddle" (easy). In reality it proved fine for ME, but for end users (the target) it proved cumbersome and confusing. Regardless of other issues, IME, "local storage" is not a good universal way forward to simplicity. TT -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1eb108ac-49b2-415c-9717-339f186028cd%40googlegroups.com.
