-
Notifications
You must be signed in to change notification settings - Fork 472
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
Improve Search box UI and UX #683
Comments
Hi @jpkrohling , Can I work on this issue? |
It's yours! |
Hi @meenal06, here is the file with the detailed UI design for this issue - |
Hi @jpkrohling , I have edited the layout according to the sigma designs however there are several complication with using dragNdrop inscribed under the SearchForm of which one major is that with every click in the search form antd would perform two tasks one of taking input and other of opening the file-upload which is the default method added into the dragger widget. Let me know what do you think on this! |
Click to upload sounds fine to me, but perhaps @rubenvp8510 has a different idea? |
Due the limitations I see, I think click to upload sounds like a good approach, or may be delimit the area of dragNdrop to no overlap with the form could work for this case? |
Yes the later is achievable I hope so! |
For now it's ok with the click approach, we might want to think about the dragNdrop region later :) |
Requirement - what kind of business use case are you trying to solve?
Improving the usability of the search in Jaeger, by unifying between the two tabs - saving the user an extra click and updating the UI.
Problem - what in Jaeger blocks you from solving the requirement?
Currently, there are several issues in the Search box UI:
Proposal - what do you suggest to solve the problem or improve the existing situation?
See attached proposal for the redesign - unifying between the search and upload functionalities, whilst keeping the drag and drop functionality - all in the same view. Also, a cleaner UI and a more prominent search button.
Before:
![Screen Shot 2021-01-24 at 17 05 06](https://user-images.githubusercontent.com/75564311/105634556-3643fd80-5e67-11eb-826b-f3351dccc849.png)
Suggested:
Screen.Recording.2021-01-24.at.13.17.47.mov
Would appreciate your thoughts on the proposal.
The text was updated successfully, but these errors were encountered: