-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI improvements for external storage configuration #9663
Comments
@owncloud/designers |
@karlitschek @craigpg milestone set to OC 8 |
This issue blocks #12635. Raise to higher priority? @PVince81 @karlitschek |
I think @jancborchardt already agreed to this approach in a separate ticket. I'll add this one in #12216 as prerequisite. |
I'd keep this ticket here solely for introducing the new UI, but not directly solving the auth part. |
Mount options dropdown was added through #14925 |
The dropdown currently contains hard-coded options, so it's not possible yet to have backends add their own stuff there. |
I think this is mostly solved now. The configuration fields still make the page quite wide, but they are unavoidable. |
As noted in a few places (#9653, #7736) the UI for configuration of external storages is very limited. Some storages require many parameters, which causes problems with small screens; some parameter names are very long, and get truncated (especially in more 'verbose' languages); and some options can be considered 'advanced' and could be hidden in a submenu (#8167 for example).
One way to improve could be an icon at the far right of every storage, next to the 'delete' button, to allow access to advanced settings. This menu would hide options like "Use ownCloud credentials" (#7875), advanced settings for OpenStack storages (#8410), or SFTP asymmetric key configuration (#9198). These options will usually only be used in advanced cases, where the user is well aware of the settings required. This can help keep the base GUI clean and uncluttered for new users.
Please write any suggestions here (this is a discussion!) and when a consensus has been reached we can start working on the code
The text was updated successfully, but these errors were encountered: