Community
Participate
Working Groups
Main thread: https://bugs.eclipse.org/bugs/show_bug.cgi?id=185052 As agreed on in reference bug 185052, opening one bug per europa project, to track progress individually. (This more an enhancement request than a bug) Version: 3.3.0 Build id: I20070323-1616 (3.3 M6) - installed all currently Europa installable features on top my fresh M6 install - instrumented core.runtime to track plugin activation - found that for base 3.3 M6, 36 plugins were activated, whereas 92 were activated for europa - wonder how I could activate / de-activate some feature base on the work I intend to do (ex: work on Database or develop some C/C++) I'm aware that plugin activation is a subject that has been already discussed, but my experience as a RAD, WID or Message Broker Toolkit user makes me believe this is really something we should try to improve. - start base Eclipse (Java perspective), - start europa (same perspective, same workspace), - start RAD (same perspective, same workspace). Observe how Eclipse can be fast, and how startup times (and overall performance) is slowing, as soon as you begin to pile up plugins / features. Based on what is already done in Eclipse based toolkits such as WID/RAD, we could improve / optimize the number of features / plugins loaded at startup based on corresponding capability. Each feature could contribute the Capabilities preference page: - capability enabled: feature / plugins loaded at startup - capability disabled: feature / plugins not loaded at startup I went to the Capabilities preference page and found that, currently, only the BIRT feature was contributing to this page (compared to base Eclipse). This work might be conducted in parallel with the resolution of bug 136397, along with a (new) investigation on plugin activation (plugin owners should check whether activation is really necessary or could be deferred e.g. by declarative contribution to the UI rather than programmatic contribution), so that we come up with a way to limit to the strict necessary/minimum (based on the enabled capabilities) the number of plugins loaded at startup. When such feature will have been integrated, the trick will consist in verifying that - a disabled capability does not "wake-up" / load corresponding feature/plugin - an enabled capability will only "wake-up" / load the expected necessary plugins Contributing to the General / Capabilities preference would enable end-user to be able to activate/deactivate desired plugin(s) based on intended usage of the workbench. As suggested by Ed Merks in thread http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg01042.html, in the new Capabilities Preference page, we may come up with a capabilities hierarch that matches the categories displayed in the update wizard, when installing europa. Grouping might be similar as what can already be found in 3.3 M6. Doing this way would prevent us from having too many items in the General Capabilities pref page confusing the end-user. Refer to screen shots in bug 185052 (Europa install and Eclipse Advanced Preference Page) (any other suggestion that could help minimize the number of plugins loaded at startup will be welcome)
(In reply to comment #0) this bug should be in a stand-by status until clear expected and agreed on behavior will have been found and detailed in bug 185052. Thanks.
