UX additions for external storage

[PVince81]

• better detection of unavailable storages (Properly handle unavailable external storages #11792)
• unavailable storages must show an overlay icon on the mount points (see Sharepoint/WND) (Show external storage status in file list + prompt credentials if different #20569)
• provide facilities for plugins to handle credential changes (if the storage is unavailable due to credential changes, provide a dialog for the user to provide the new credentials)

@MTRichards @craigpg @karlitschek anything else ?

@icewind1991

[MTRichards]

In addition to the config options for external storage, the list of config options might make sense to be here too. How is this different than #12216 ?

[MTRichards]

I see, this is the UX parts. But lots of the config options are also UX related on setup.

Unavailable storage: we need a mechanism, such as the red bar in WND and SharePoint, that shows that the storage is unavailable. When the red bar is clicked on, a credential entry window pops up if it is a credential problem. A network connection warning pops up otherwise. Depending on the storage, we have different ability to detect the type of error, but if we can detect the type this is the desired behavior.

[PVince81]

@MTRichards yes, the list of requirements is quite big and I'm trying to split everything in smaller manageable logical units.

The goal of the config options is more an admin thing, to make storages more configurable, not to bring a nice positive emotional experience to admins or users (UX). If an admin cannot configure encryption for a storage it is not bad UX but just a missing feature.

Unavailable storage in contrary is more UX matters because users want to know what is going on with their unavailable storages and be able to fix it quickly instead of jumping through hoops. Not knowing why the storage is unavaiable would be bad UX.

[PVince81]

Implemented partly by @jmaciasportela here #20569 (comment)

[PVince81]

I think we're done here, closing.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.