I would like to point to a somewhat official resource, the Eclipse UI
guidelines at https://wiki.eclipse.org/User_Interface_Guidelines. Those
don't give a definitive answer, but they tell this:
https://wiki.eclipse.org/User_Interface_Guidelines#The_Spirit_of_Eclipse
is all about consistency.
htt
Hi,
Thanks for the clarification.
With regards to buttons for actions on trees or tables, the consistency
is my biggest problem. Some buttons have icons, some don't. That would
look odd IMO.
Dialogs vs editors/views:
As an example, I've looked at the dependencies tab in the pom.xml editor
provid
> On Sep 25, 2019, at 16:44, Becker, Matthias wrote:
> suboptimal UX
I think this statement needs backing by a UX research/study.
To me, a growing use of icons (especially in addition to text) comes with a lot
of drawbacks, eg., waste of screen space, make dialogs look way too busy, hard
to r
Thank you for the input.
To make my point clear once again:
I do *NOT* propose to put icons on *any* buttons (like "OK", "Cancel", etc.)
I really talk about buttons that perform actions on a tree or table. Typical
action are "Add", "Remove", "Up" and "Down".
And I would like to know if you have
