|Re: [cross-project-issues-dev] Eierlegende Wollmilchsau|
I think this is a great experiment. For reference I added a screenshot of how the "eierlegende Wollmilchsau"
looks like on a mac:
And the find dialog is so wide, that it does not fit on my screen (note some tabs are cut off at the right side):
Running an empty instance takes about 15-20% cpu, but id did not cause the initial
resource consumption you have seen...
The eclipse capability explorer
For years I wonder how much effort it would be to create a meta plugin
that reads all the UI extension points and creates a representation of
what different features add to the UI.
I mean: often I install a feature and I have no idea what it actually
contributes to the UI. So, imagine there would be a tool that allows
you to explore all the extensions a specific feature adds to the IDE. Imagine
you could just select a feature and see what it contributes. It could
be some tree ore a rich text representation. Or (the luxury version),
it could highlight the additions in the UI directly.
Of if I could click (with some magic modifier keys) on some UI component
and it would tell me which feature contributed that element.
What I am talking about is a tool to explore the UI and to understand
how things are wired together and who contributes what.
If we spin this idea further: what if I could just interactively add/remove
extensions to the UI? If we would have a tool that allows the user to
experiment with all 'Capabilities' (not only the ones provided by some
extensions) (Note: capabilities are set in the org.eclipse.ui.activities extension
point using activityPatternBinding):
Wouldn't an 'eclipse capability explorer' be a great meta tool?
On 2015-12-09 7:54, Ed Merks wrote: