This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author taleinat
Recipients cheryl.sabella, taleinat, terry.reedy
Date 2020-10-12.19:39:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1602531571.69.0.744322619916.issue34976@roundup.psfhosted.org>
In-reply-to
Content
The version in the PR is modeled after similar features in IDEs, not browsers. I mentioned browsers since they are very commonly used, and to the best of my knowledge all modern browsers use search bars. Therefore, as a UI element, search bars are now commonplace, unsurprising, and require no training to use.

As for replace, while many IDEs use a bar, many word processors do indeed still use a dialog for search/replace, and I've seen text editors use a bar for search but a dialog for replace.

I first implemented this for my personal use, since I much prefer bars to dialogs. But I can see the argument that they can be harder to use for novice users.

If we decide not to go with this path, I'll try to extract some of the improvements made to the search engine, such as highlighting all matches, into a PR improving the existing search and replace dialogs.
History
Date User Action Args
2020-10-12 19:39:31taleinatsetrecipients: + taleinat, terry.reedy, cheryl.sabella
2020-10-12 19:39:31taleinatsetmessageid: <1602531571.69.0.744322619916.issue34976@roundup.psfhosted.org>
2020-10-12 19:39:31taleinatlinkissue34976 messages
2020-10-12 19:39:31taleinatcreate