-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
Filepicker design improvements #11522
Conversation
Signed-off-by: Jan-Christoph Borchardt <hey@jancborchardt.net>
Signed-off-by: Jan-Christoph Borchardt <hey@jancborchardt.net>
Signed-off-by: Jan-Christoph Borchardt <hey@jancborchardt.net>
Signed-off-by: Jan-Christoph Borchardt <hey@jancborchardt.net>
Signed-off-by: Jan-Christoph Borchardt <hey@jancborchardt.net>
@jancborchardt very nice! Info: #11315 is about the broken button layout in version 13. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@weeman1337 ah cool, only saw #11315 now! :) Then I guess this fixes #11315
Yeah, it’s not really intentional, but fixing is something for a different pull request. :) There is white border on the primary button mainly for when it’s on background (like on the log in page and error pages etc.).
Yep – also something for a different pull request. Actually here we should also use the ellipsis that is used in Files (but does not work at the moment): #11520 → different pull request too. :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Teste and works 👍
codecov upload failed -> merge |
Common folks, not even 1h opened. I know we want things to get in, but regarding design, don't ask input of the designer team if this is to merge 1h after ^^ I really find the round border out of place. They feel like an old design and are too different from our current design. Please revert. |
@@ -662,7 +662,7 @@ | |||
if (permissions & OC.PERMISSION_UPDATE) { | |||
actions = OC.dialogs.FILEPICKER_TYPE_COPY_MOVE; | |||
} | |||
OC.dialogs.filepicker(t('files', 'Target folder'), function(targetPath, type) { | |||
OC.dialogs.filepicker(t('files', 'Choose target folder'), function(targetPath, type) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't it be "Select" instead of "Choose"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Choose" seems a tad less technical, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jancborchardt Select
looks to be much more standard. The only place I found "Choose" was in OneDrive and even they seem to be interchanging the 2 terms:
https://support.office.com/en-us/article/Choose-which-OneDrive-folders-to-sync-to-your-computer-98b8b011-8b94-419b-aa95-a14ff2415e85
@@ -34,6 +34,7 @@ | |||
--color-border: $color-border; | |||
--color-border-dark: $color-border-dark; | |||
--border-radius: $border-radius; | |||
--border-radius-large: $border-radius-large; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should go with these extremely rounded borders. That would in fact mean that we would have to make the same changes to other (much smaller) popovers where it would look totally out of place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pixelipo see comment – no, the border-radius large is only for the big modal dialogs (welcome screen, this move/copy etc.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jancborchardt but what if a popover has a button?
|
||
// light border like file table or app-content list | ||
$color-border: nc-darken($color-main-background, 7%) !default; | ||
// darker border like inputs or very visible elements | ||
$color-border-dark: nc-darken($color-main-background, 14%) !default; | ||
$border-radius: 3px !default; | ||
$border-radius-large: 20px; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👎
We should then not revert the whole thing, but only the border radius change. |
Of course :) |
@pixelipo @skjnldsv for reference, the border-radius-large is only intended for the modal dialogs (like this move/copy, first run wizard, etc.). Not for other popovers. But feel free to make a pull request to adjust the border-radius with before/after screenshots. And regarding feeling like an old design, it was inspired by the current macOS/iOS modals – which do have a little less border-radius though, yes. |
@jancborchardt NC design seems more closely related to the Material design, where border-radius is similar to what we had (3px): |
A follow-up with adjustment and reasoning here: #11536 @pixelipo we’re not really following Material Design, and it’s good that we’re not just doing it dogmatically but pick and choose what is best. There’s this (quite old and possibly not correct) article about rounded rectangels: http://uiandus.squarespace.com/blog/2009/7/27/realizations-of-rounded-rectangles.html Just because "iOS did it first", of course Android and especially Windows Phone (R.I.P. ☠) had to do it slightly different to have different branding – it isn’t particularly rooted in actual ergonomics. |
Lots of improvements, check it out @nextcloud/designers:
Before & after, mobile:
Before, desktop:
After, desktop:
(And no, somehow it didn’t work to ellipsize long filenames in the list on mobile … tables.)