Hi
Influenced by earlier rounds of this discussion, I have been moving my contributions to the global UI from e.g. "Load Complete OCL Resource" to "OCL->Load Document" so that the OCL added value in non-OCL-specific contexts is clearly identifiable as an OCL add-on.
This reduces menu growth by grouping all OCL add-ons under one heading
This enables users to look for extra OCL functionality when they want it
This reduces the OCL impact when not wanted
This increases the perception of OCL bugs as OCL bugs rather than Eclipse bugs
This seems like a relatively easy policy to enforce once there is general agreement that it is a good idea.
Contributions to your own UI may use top level menu entries.
Contributions to someone else's UI should have a top level scoping of sub-level entries unless the relevant someone else endorses the top level usage.
So no one should contribute
Add XXX Nature
rather they could contribute
XXX->Add Nature
but since there is a dedicated top level entry they should contribute
Configure->Add XXX Nature
Regards
Ed Willink
On 15/03/2014 22:55, Doug Schaefer wrote:
These are all solutions that are hard to pull off and I'm not sure they really address the root of the problem. We are at the mercy of the plug-in developers and how well they implement
their solutions. I love Eclipse and want to bring it to my customers because of the feature richness of the ecosystem. No one else has a great C++ IDE that also does Python and HTML5 and Java and ...
But at the same time we don't really have guidelines or an API that enforces consistency in the user experience. It's almost a crime that we let any plug-in contribute anything to the UI. And they do. Does that PyDev and V8 Debugging menu really make sense
on my Eclipse plug-in project? How do we get all these plug-ins to play nice when installed with each other and all at the same time? That's the hard question.
Doug.
On 15/03/2014 3:45 PM, Pascal Rapicault wrote:
Sadly the outcome of the process back then was rather protective.
Ya, I know. We are incredibly cautious about data privacy and the like.
_______________________________________________
ide-dev mailing list
ide-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ide-dev
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4336 / Virus Database: 3722/7199 - Release Date: 03/15/14