offline state about remotestorage.js HOT 15 CLOSED

there is, there are now 14 distinct states in the widget, and one of
them is 'offline'.

just because we haven't had time yet to make them look different,
there are only 5 visually distinguishable states. See

https://github.com/unhosted/remoteStorage.js/blob/v0.7/src/lib/widget.js#L59

and

https://github.com/unhosted/remoteStorage.js/blob/v0.7/src/lib/widget.js#L84

once i have more time, i'll make the visual design changes we
discussed, and will do user testing to see if it's clear to users
which state means what. in any case, in the event we switch to
webintents, it could all look different again.

For now, i think it's good enough.

On Wed, Jun 27, 2012 at 12:41 AM, Jan-Christoph Borchardt
[email protected]
wrote:

There needs to be a state in the syncer signifying offline state. It should be like the small popout on the left like when you hover over it for logout, except that it is permanent and states »offline« or something similar.

Additionally, we probably need to explain or somehow fix that if you sign out while offline, your changes will not be synced up.

---

Reply to this email directly or view it on GitHub:
https://github.com/unhosted/remoteStorage.js/issues/48

from remotestorage.js.

We did not not have time to make them look different – there should just not be »14« different states made visible to users.

The important states are:

1. not connected → the connect widget
2. everything fine → just the icon
3. loading (connecting, syncing) → spinning icon
4. offline/error → red icon, with message to the left

Everything else is technological details.

from remotestorage.js.

@jancborchardt do you have a red version of the cube somewhere?

from remotestorage.js.

Offline is not an error, but a standard state. Please don't make it red.

What's done in a lot of UIs is grey out when offline for example. We could do that as well.

from remotestorage.js.

Offline is not an error, but nonetheless should have a warning character. When you end up in offline-state, for whatever reason, it is possible to lose data (e.g. if your browser clears localStorage when you end the session).
"Greying out" the cube in my opinion would instead remove awareness of it's presence.
There should be some distinction though, between "error" and "offline". The only error that currently is displayed, is when we see a 401, in which case the widget lets you re-request a token.

So, @jancborchardt, I'm rephrasing my request:

• Do you have a red version of the cube somewhere? (for the error state)
• Do you have a version of the cube to indicate "offline" state somewhere?

Maybe we could "split" the cube somehow (show two halfs with a space in between), to indicate "offline"? Any other suggestions?

from remotestorage.js.

Again: it is a standard state. It only justifies warnings if there are sync problems, not just if it can't sync now.

from remotestorage.js.

lightblue? :)

On Mon, Oct 22, 2012 at 3:04 PM, Sebastian Kippe
[email protected]:

Again: it is a standard state. It only justifies warnings if there are
sync problems, not just if it can't sync now.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/48#issuecomment-9662802.

from remotestorage.js.

Yeah, I agree with @skddc – offline is a standard state, the Dropbox syncer for instance just displays the box in that case without icon. I think greying out makes sense as a beginning. We can still change it if it feels weird, but it’s a good start.

@nilclass here are the icons: remotestorage/remotestorage.io@9183714
The warning character in offline state should come from the permanently visible bubble which says »Offline«. And then when local changes are present on the line below »changes will be synced when online«.

from remotestorage.js.

The offline icon looks a bit weird, as it has the same color as the bubble. See here.

from remotestorage.js.

@nilclass updated the icon with a darker version: remotestorage/remotestorage.io@0a2b1e4

from remotestorage.js.

Everybody content with the currently implemented solution?

from remotestorage.js.

@xMartin so the decision was not to allow "disconnect" in offline state?

from remotestorage.js.

For 0.7.0, yes. Definitely needs improvement but is not a blocker.

from remotestorage.js.

moving this to "next version", as no more will happen in 0.7 scope

from remotestorage.js.

I’d say this is superseded by #195, where we discussed lowering the retry timeout. Maybe we need more feedback or info still, but it’s a nice start.

from remotestorage.js.