Re: [ui-best-practices-working-group] UX topics at ECE Platform Summit

[Stefan Xenos <sxenos@xxxxxxxxxx>]

We also had a discussed:

- JDT hovers. Those present in the room who voiced an opinion all preferred the option of disabling them by default. I followed up on this with Dani and he wants to keep the hovers on by default unless we can gather evidence that the majority of users dislike them. However, he seemed amenable to adding a "Don't show me this again" checkbox to the hovers which, when selected, would inform you of the keybinding for the unified hover and turn off all the hovers.

- Merging the various platform projects into a single project. The majority are in favor of merging, due to the small number of committers in a number of projects and the long review queues (JDT UI and SWT are bad for long review queues, and platform debug and platform resources suffer from small committer pools). One participant voiced concerns that some of the projects - like SWT - require special skill sets and that inexperienced new committers may cause problems by writing poorly-informed patches. It was observed that this has never happened in practice and that the CDT project is currently running very effectively with a unified committer pool.

Lars:

- There are a number of PDE templates that use deprecated API. General agreement that they should either be updated or deleted.

Oliver (I think):

- We have poor guidance about the criteria for including menu items in each top-level menu. We need to write up and start enforcing a specification for this.

On Tue, Oct 25, 2016 at 11:45 AM Doug Schaefer <dschaefer@xxxxxxxxxxxxxx> wrote:

Thanks Mickael! Sounds like a good discussion. Unfortunately I was tied up in the CDT summit all day.

We should add this to the agenda for the face-to-face Arch Council meeting this week.

Doug.

From: <ui-best-practices-working-group-bounces@xxxxxxxxxxx> on behalf of Mickael Istria <mistria@xxxxxxxxxx>
Reply-To: UX Group <ui-best-practices-working-group@xxxxxxxxxxx>
Date: Monday, October 24, 2016 at 6:11 PM
To: UX Group <ui-best-practices-working-group@xxxxxxxxxxx>
Subject: [ui-best-practices-working-group] UX topics at ECE Platform Summit

 Hi all,

I'd like to share a few topics that were discussed during the Platform Summit at EclipseCon Europe ( https://wiki.eclipse.org/Platform/summitece2016 ) and that were related to UX and worth discussing here too.

I drop the list here and we can turn it into individual threads, and maybe guidelines.

# Finding actions

Many actions are in menu and can be found using the `Verb > Noun` logic (such as `Export > Preferences`). However, there are many users who have a more object/artifact oriented logic, usually in the form of `Noun > Verb`, such as `Preferences > Export`. A good UX should support both logic, but presenting actions in menu, but also on the artifacts they manipulate.
Here are some occurences:
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=500051
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=500049
* On Hover `Disable` additionally to Preferences > Editor > Hover...
* marker resolution allowing to also control the marker (additionally to quick fixes)


# Gerrit flag for UX review

By Sopot Cela.
It would be interesting to have a custom flag on Gerrit, like the "Code Review" one, that allows to vote +1 about conformance to the project to UX guidelines.
This flag shouldn't be mandatory +1 for a merge (it could be 0), but it would at least allow reviewers to consider the UX part if they're interested.


# Document UX "cost" of installing a project page

By Andrey Loskutov.
Projects metadata (such as https://projects.eclipse.org/projects/eclipse.platform.ui/ ) could show the "cost" of a project in term of UX: what top-level menus, context menus, views, perspectives, toolbars... they're adding. So once could easily how intrusive, or not, a project is in the IDE.
Additionally or as an alternative, the UX Guildelines violation could be listed on project metadata.


# Report bugs with "usability" keyword to report UX Guidelines violations

By Andrey Loskutov, Lars Vogel & Stefan Xenos.
Instead of additional metadata, project with UX violations (according to guidelines) should receive bugs with the "usability" keyword. Such bugs should mention which guideline is violated. Then listing UX violations for a project is only about listing open bugs with "usability" keyword.

# UX Certification as Marketplace "priority" marker

By Mikael Barbero.
If we manage to revive "UI/UX reviews" (that would report "usability" bugs), we could have review committee providing an "examplary UX" label that could be highlighted on Marketplace. Solutions with such label would be made a bit more visible and receive a medal or trophy icon to drive more users to them, and also to motivate other competing solutions to get this label too by improving their UX.
If we manage to set up such reviews, they'd probably have to be constrained to Eclipse.org projects (not the whole Marketplace)

# p2 and MPC dialog to be made non-modal

By Lars Vogel
MPC in Neon.1 seems OK, for p2, https://bugs.eclipse.org/bugs/show_bug.cgi?id=506432

--

Mickael Istria
Eclipse developer for Red Hat Developers
My blog - My Tweets

_______________________________________________
ui-best-practices-working-group mailing list
ui-best-practices-working-group@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group