[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ui-best-practices-working-group] [ide-dev] concrete action item - menu contribution
- From: Stefan Xenos <sxenos@xxxxxxxxxx>
- Date: Wed, 14 Sep 2016 15:49:25 +0000
- Delivered-to: firstname.lastname@example.org
IMO, the first step to having consistent menus is having a consistent and well-documented set of criteria for inclusion in each menu. Right now, no such set of criteria has been published.
I tried to start the process of documenting the function of menu on the main menubar here:
...perhaps if we could ratify this (or something like it) as an official set of UI guidelines, it would then be possible to police plugins for conformance to those guidelines.
Â - Stefan
I doubt youÂd find someone who disagrees. Question, what can we do if the
third party isnÂt responsive? Is there a mechanism we can put in place
that we can use to filter stray menu contributions?
On 2016-09-14, 11:32 AM, "ide-dev-bounces@xxxxxxxxxxx on behalf of Pascal
Rapicault" <ide-dev-bounces@xxxxxxxxxxx on behalf of pascal@xxxxxxxxxxxx>
>STOP SHITTING IN MY CONTEXT MENU!!!!
>Sure Eclipse is all about integration but we often found ourselves with
>ridiculous menu entries because one is not carefully selecting where its
>menu entries should be placed.
>In the attached screenshot, I'm adding a new context menu to the EGerrit
>dashboard to find my menu polluted with not 1, not 2 but *3* random
>entries from Team and PDE projects. Come on guys, you can do better.
>And you know what, here I just have the Eclipse SDK, EGerrit and Egit
>installed. Imagine a user who has everythign installed.
>I think this sort of things make us look bad, could we agree to fix this?
ui-best-practices-working-group mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit