-
Notifications
You must be signed in to change notification settings - Fork 134
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
Search is not where expected #43
Comments
Hi @stefan-niedermann, We might discuss, if the glass icon is the best icon for this job (=field). I would prefer a funnel. And one could argue, that the input field is somewhat hidden thanks to the "flat" design. A really visible input field might be better/more helpful. But the place is correct (IMHO). |
@jancborchardt would love to have your feedback on this, as we talked about this a while ago. |
I would expect that most users would think of this as "Search" and thus look for it with the traditional search icon and UI location, as the original poster did on this issue. |
..and even if we provide full-text search later, the main use-case is finding the right note. |
So, thinking about this it seems that uniformity with the other apps is more important than the value of experimenting with a new position for the search. That’s a separate topic though still. With other considerations like accessibility on mobile – if it’s in the top of the sidebar, searching will be difficult to access and require a two-step process, if it’s discovered at all. Unlike the top right spot which people are used to from Android and also iOS to a certain extent. So @Henni if you agree then the sensible solution might be to use the normal search field position after all. |
@jancborchardt @camilasan and i discussed this topic again in a design review at the hackweek and we came to the conclusion that even if it is technically filtering and not searching (what i do not aggree), the input should be on the top right position. |
@stefan-niedermann I'll introduce a new standard for the search button soon :) |
@skjnldsv anything we could implement here already? :) Or could we fix it even without that new standard @nextcloud/notes? |
@jancborchardt Actually, there is already a standard for the search, so it might fit the needs of the notes app already :) The only work will be to make the standard 'standardized' enough so our new vue apps can work with it |
@skjnldsv as this app is still in Angular, it would be awesome to get some pointers on how to use the standard way of searching in the Notes app for the time being. :) |
Look at the JavaScript file that handle the search in server! |
Nextcloud 14 will introduce a complete new search, see nextcloud/server#9912. However, as far as I can see, this will not be backwards-compatible. How to proceed? The easiest way would be to
This means, however, that users on Nextcloud 13 or older can't use the search. How do other apps cope with this? |
@korelstar Apps will need to set their min-version of nextcloud to 14. |
I don't think that we should exclude Nextcloud 13 and older just due to the search. Isn't there a possibility to check the current version and execute the app's search code on Nextcloud 14 upwards, only?
|
Hi @Henni ,
i recently updated the app and was happy to see the search functionality.
Though i didn't expect it in the left sidebar but in the top right corner next to the user name where it is in the files, contacts and calendar app, too.
So this is a request to move it to the well-known place :)
PS.: Works great! :)
cc @nextcloud/designers
The text was updated successfully, but these errors were encountered: