Community
Participate
Working Groups
The Find/Replace dialog is currently only shared for Text editors. However, it should be shared for all editors which need this function. The benefits would be: 1) User's placement on the screen would be consistent/shared across editors. 2) Seamless use across heterogeneous editors. To achieve this, it could behave similar to the outline or properties view. It would contain a PageBook, and would retreive a find/replace page contribution from the active (Editor)Part. If there is no contribution, it would hide until the user went back to one of the editors for which it was active (note that it would not just reappear once some random editor decided to contribute to Find/Replace). Ideally there would be a way to store a memento of the current type of find/replace, and share it across similar find/replace pages. If Find/Replace were a detached floating view, it could reuse PageBookView implementation.
Since this covers not just text-based editors bud all workbench editors this is for Platform UI. Note: one item on the 3.1 text plan is to investigate # [investigate] find/replace * provide a find/replace view part The idea to extend the Outline view sounds interesting.
To support "provide a find/replace view", it should be possible to place the view on the menubar's "Edit" menu as if it were an action (of course an action which opens the view is equivalent, but clumsy).
Susan, please note that Platform Text plans to improve/change Find/Replace for 3.2. If this is also on your list for 3.2 we should coordinate our plans and goals before starting the work.
This message is part of a mass update on bugs that have been reviewed for several releases, but not fixed. The bug is legitimate, but not a priority. Marking P5. Patches would be entertained.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
