Open HeikoKlare opened 1 year ago
I think an even 1st increment is just to ship a (floating and placed as best upon text viewer) Search Bar variant of the Find and Replace dialog that is used by text editors.
e.g., December 2023
FindReplaceDialog.java
This class mixes the functionality and the interface of Finding and replacing. To reuse this functionality, I want to extract the business logic into a separate FindReplacer
-module which will be reused by the new find-replace-bar.
This step will NOT include any logic for polling views for their search-providers
(subject for debate) I will implement the overlay-based Find/Replace as @mickaelistria suggested earlier. This will entail a different design that looks more like the one VScode currently uses and will incrementally approach a good solution that can be shipped with the December 2023 release.
e.g., March 2024
Using a new Composite inside of the View (like in the current solution), I will integrate the dialog into the Layout. This will happen as soon as possible, to give us a lot of time to find possible problems in integration.
Allow each view to give it's own search-providers to the FindReplacer
using a new common interface for FindReplace
Preparatory refactoring separating FindReplaceDialog UI from its business logic to be reused for new UI:
Contribution of the the new overlay UI:
Current Behavior
The current search dialog in Eclipse quite outdated / has a bad UX and not intuitive to use. Some of the most important issues are:
Expected Behavior
A lightweight, extensible in-view search functionality that is obviously bound to a specific view, does not hide important information and can be provided for other views than textual ones.
The more sophistacated proposal is given in https://github.com/eclipse-platform/eclipse.platform.ui/issues/1090.
Basic Increments