Skip to content
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

Add find all button #7559

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

yisibl
Copy link
Contributor

@yisibl yisibl commented Jun 11, 2016

Fixed #14836
demo

@mention-bot
Copy link

By analyzing the blame information on this pull request, we identified @Inori and @alexandrudima to be potential reviewers

@msftclas
Copy link

Hi @yisibl, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@msftclas
Copy link

@yisibl, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, MSBOT;

"label.nextMatchButton": "下一个匹配",
"label.noResults": "无结果",
"label.previousMatchButton": "上一个匹配",
"label".allMatchButton": "选中所有匹配",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we don't modify locaization files ourselves, only touch the English version.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rebornix Do you mean that do not modify the localization file? Should I submit a PR to increase localization translation?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yup, just leave it there, it will be handled by the localization team.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yup, just leave it there, it will be handled by the localization team.

Copy link
Contributor Author

@yisibl yisibl Jun 12, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!
By the way, how do I open a localized UI to vscode after the source code is compiled?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed the localized changes.

@yisibl
Copy link
Contributor Author

yisibl commented Jun 14, 2016

@alexandrudima This can be merge?

@alexdima alexdima added the ux User experience issues label Jun 26, 2016
@alexdima
Copy link
Member

I would like to bring in our UX folks on this, rather than just merging it in and get their advice on how we can add functionality to the find widget without overdoing it.

@stevencl @bgashler1 Can I please get your opinion on this proposal?

@yisibl
Copy link
Contributor Author

yisibl commented Jun 27, 2016

@alexandrudima Thanks!

@stevencl
Copy link
Member

I really like the idea. We might consider doing something similar to Visual Studio. Instead of three separate buttons for find next, find previous and find all, VS has a button with a drop down that allows you to select the specific action you want to use. So it would look something like this mockup (showing what the user sees when they click the drop down):

image
The idea would be that you click on the drop down next to the button to run and then change the command. So if you click Find Previous in the drop down, the button changes to the Find Previous button. If you click Find All, the button changes to the Find All button etc.

@bgashler1 might have some other, better ideas. I haven't spoken with him about this today.

@yisibl
Copy link
Contributor Author

yisibl commented Jun 28, 2016

@stevencl

I am more inclined to the 100% width of the search box, and the height is adaptive. Now the search box is too short, and the preparation of the code when you may often need to search for a relatively long code fragment. If it is a 100% width search box, then there is no need to fold(drop down) the buttons.

Sublime Text:

Sublime


By the way, usually the focus of our vision is on the left, especially when full screen writing code, usually we will set up more than 80 characters automatically wrap. So now the search box aligned to the right, I think the user experience is not good.

Anyway I expect the next version can be added to find all button.

Thanks!

@stevencl
Copy link
Member

Thanks @yisibl. I understand the points you are making about the current find experience.

As you've pointed out, Sublime has a very different user experience for find and find in files. We use the small box for find and a viewlet for find in files so that we minimise the extent to which we interfere with the code that the user is browsing.

In order to accommodate richer find interactions such as the one you are proposing here we need to ensure that we minimise the amount of code we obscure when we draw the find UI. Hence my suggestion above (and the reason why we align the find UI to the right).

So without any major modifications to the current find UI, I would recommend the drop down button to expose the Find All command. That way we incorporate the new functionality without requiring major changes to the overall find UX.

@alexdima alexdima added this to the Backlog milestone Jul 5, 2016
@alexdima alexdima added the editor-find Editor find operations label May 16, 2017
@rebornix
Copy link
Member

I'll review this PR in next iteration when I do full width find widget.

@rebornix rebornix modified the milestones: June 2017, Backlog May 26, 2017
@rebornix rebornix mentioned this pull request May 26, 2017
@yisibl
Copy link
Contributor Author

yisibl commented May 31, 2017

@rebornix Where's the plan for "full width find widget"?

@yisibl
Copy link
Contributor Author

yisibl commented Sep 4, 2019

I have re-updated this feature, please review.

@alexandrudima I'm not sure if the click button should call this.closeFindWidget() to close the FindWidget.I tend to close it, otherwise there will be a highlighting prompt to interfere with the user editing the text.

image

@rebornix rebornix added the feature-request Request for new features or functionality label Oct 8, 2020
@joaomoreno joaomoreno changed the base branch from master to main February 15, 2021 08:51
@ilixindri
Copy link

@stevencl use for all (∀) symbol.
Captura de tela_2021-04-15_22-25-37

@ghost
Copy link

ghost commented Sep 11, 2021

Best to design another codicon for it

@ghost
Copy link

ghost commented Sep 17, 2021

I have logged a issue for adding a bespoke icon specifically for this pull and other uses of "select all" in the UI

@rebornix rebornix removed their assignment Oct 22, 2021
@alexdima alexdima dismissed stale reviews from fosslinux, nzec, and ghost via 4f8b579 May 5, 2022 09:18
@ghost
Copy link

ghost commented Jun 30, 2022

It's embarrassing that this is 6 years old!

@miguelsolorio miguelsolorio removed their assignment Jul 19, 2022
@byehack
Copy link

byehack commented Oct 5, 2022

Find all button in other places is usually for show list of them, not select!
Btw I hope it will add by #158598 (comment)

image

Just an idea:
Change the color of number of founds and make it clickable.
Click on it should go to search panel with seed of current search and just include current file.
(It could have support CTRL+click to find in all files.)
Details can go under hovering.

Also, there is an extension currently do this but main problem there is no way to back previous state of search panel. (it could solve with using search editor)

@zm-cttae
Copy link

I personally think the caption should be "Select All Matches" like the exploration done in #14836.
The icon could just be expand-all or plus which is the best analog in the UI for "multi-target actions"

Copy link

@zm-cttae zm-cttae left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yisibl This conflicts with the new orthogonal "Find all" new window button implemented #128915 and the naming is internally inconsistent.

As some context, the #14836 issue split into two feature requests:
1. "Find all" `new-file` icon to launch a new search editor file
2. "Select all matches" `expand-all` icon

I'll try and make some suggestions ... this review should hopefully get us a working "select all" button.

@zm-cttae
Copy link

zm-cttae commented Feb 2, 2023

Nvm I will make a PR to your fork branch and see if I can reup this. yisibl#1

@zm-cttae
Copy link

zm-cttae commented Feb 8, 2023

@miguelsolorio your thoughts please on the UI/UX recommendation in #14836 (comment).
If core team is happy, reup PR is ready to go.

@zm-cttae
Copy link

zm-cttae commented Mar 2, 2023

@daviddossett @joyceerhl @bpasero @lszomoru @miguelsolorio could one of you take PR assignee targeting April iteration? We want to reup this - #14836 (comment)

@alexdima alexdima removed the feature-request Request for new features or functionality label Sep 25, 2023
@heartacker
Copy link
Contributor

hi, @rebornix , could you please take a look

Copy link

@ruru-m07 ruru-m07 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editor-find Editor find operations ux User experience issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add "find all occurences" in the current file feature