Value based search in preference dialog
- [x] I verified latest Integration Build of Eclipse SDK doesn't provide the feature.
Suggestion
From a fresh installation and clean workspace:
- I want to view / modify a specific preference entity.
- I don't remember the key but know the value
And would like to be able to
- Enhance the filter text to respond to value based search as well.
Community
- [x] I understand suggesting an enhancement doesn't mandate anyone to implement it. Other contributors may consider this suggestion, or not, at their own convenience. The most efficient way to get it fixed is that I implement it myself and contribute it back as a good quality patch to the project.
That is quite tricky, because Eclipse Preferences UI frankly misses a mapping of a preference to a particular page or widget that allows to control that preferences. There is not even a non-UI preference registry, there is no way to list all possible preferences used programatically. The only thing we have are the preference store which allow to access some preferences (the ones that were set in those stores), but the preference store may miss some preferences, or contain entries that are not used anywhere. And again, if we know 1 particular preference, we don't know what to show in the preference UI.
On the long run, it may make sense to have a "raw" view of preferences, and let power users play with it; similarly to how web browsers have about:preferences vs ``about:config`
FYI, Oomph provides a raw view of all preferences.
It can be opened in an editor and that editor support find:
It can be installed from this:
@merks that seems like a very good feature, which we can easily rely on to provide search as requested in this issue. Is there anything that would make it hard or not worth trying to move into Platform UI directly?
@merks that seems like a very good feature, which we can easily rely on to provide search as requested in this issue. Is there anything that would make it hard or not worth trying to move into Platform UI directly?
Yes, unfortunately the dependency stack makes it hard to move: