Community
Participate
Working Groups
There should be no need for that. Almost all users will muss that feature unless they read the N&N.
Would be nice to have a user-friendly solution for 4.15.
We'd need to activate the quicksearch bundle automtically, either at startup or when loading the Quick Access. Would that be acceptable?
(In reply to Mickael Istria from comment #2) > We'd need to activate the quicksearch bundle automtically, either at startup > or when loading the Quick Access. Would that be acceptable? When Quick Search is opened it's fine with me to load the contributions.
(In reply to Dani Megert from comment #3) > When Quick Search is opened it's fine with me to load the contributions. I interpret (maybe erroneously) that in bug 546187 comment 17 and bug 546187 comment 28 you had a different opinion about when to load contributions. It's fine if you changed your mind, I'd be glad to enable all the contributors when users hits Ctrl+3 and get rid of the "Activate" entry and impression of missing content when some bundles are not active. Please confirm you're OK to change the behavior to more "greedy" plugin activation, and I'll apply that. If so, the test in bug 547001 would also need to be reworked (but nothing difficult here I believe).
(In reply to Mickael Istria from comment #4) > (In reply to Dani Megert from comment #3) > > When Quick Search is opened it's fine with me to load the contributions. > > I interpret (maybe erroneously) that in bug 546187 comment 17 and bug 546187 > comment 28 you had a different opinion about when to load contributions. > It's fine if you changed your mind, I'd be glad to enable all the > contributors when users hits Ctrl+3 and get rid of the "Activate" entry and > impression of missing content when some bundles are not active. > Please confirm you're OK to change the behavior to more "greedy" plugin > activation, and I'll apply that. If so, the test in bug 547001 would also > need to be reworked (but nothing difficult here I believe). Sorry for the late response. What's the footprint of those extensions? Where is e.g. the File Content code located? Independent of that, auto-loading will have the problem that users can't disable it at the moment. There would have to be a preference where I can disable e.g. File Content proposals.
(In reply to Dani Megert from comment #5) > the File Content > code located? in org.eclipse.text.quicksearch. > Independent of that, auto-loading will have the problem that users can't > disable it at the moment. There would have to be a preference where I can > disable e.g. File Content proposals. Ok, can you please open the ticket about disabling and preferences and mark it as a requirement?
I looked at this again and auto-starting would be bad for e.g. a new workspace. There we would for example load the Debug plug-ins. Closing for now until we have a better solution.
