New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[wizard] Improve usability of Generic IDE Support option #119

Closed
kthoms opened this Issue Nov 10, 2016 · 12 comments

Comments

Projects
None yet
4 participants
@kthoms
Contributor

kthoms commented Nov 10, 2016

screenshot 96

The option "Generic IDE Support" is mandatory for the options "Eclipse Plugin", "IntelliJ IDEA Plugin" and "Web Support". It is not intuitive that this option is the last one. It should be the first option that a user could choose and dependend on the option, the other options should be made selectable.

An option could be to make the different IDE integration options part of a group, as it is with the "Eclipse Plugin" and "Create Feature/Update Site" options. This would also make the error message obsolete, since it is clear that without the Generic IDE option the other options are not valid.

@svenefftinge

This comment has been minimized.

Show comment
Hide comment
@svenefftinge

svenefftinge Nov 14, 2016

Contributor

There was a longer discussion about this somewhere in bugzilla if I recall correctly.

Contributor

svenefftinge commented Nov 14, 2016

There was a longer discussion about this somewhere in bugzilla if I recall correctly.

@kthoms

This comment has been minimized.

Show comment
Hide comment
@kthoms

kthoms Nov 14, 2016

Contributor

Could you link that please? If redundant, close this one.

Contributor

kthoms commented Nov 14, 2016

Could you link that please? If redundant, close this one.

@svenefftinge

This comment has been minimized.

Show comment
Hide comment
@svenefftinge

svenefftinge Nov 14, 2016

Contributor

I would have done that if I had found it.

Contributor

svenefftinge commented Nov 14, 2016

I would have done that if I had found it.

@kthoms

This comment has been minimized.

Show comment
Hide comment
@kthoms

kthoms Nov 14, 2016

Contributor

I will try to find it tomorrow.

Contributor

kthoms commented Nov 14, 2016

I will try to find it tomorrow.

@kthoms

This comment has been minimized.

Show comment
Hide comment
@kthoms

kthoms Nov 15, 2016

Contributor

I searched the wizard-related (also closed) bugs, but did not find it either. Thus I would like to discuss this issue here if that's OK.

As said, I suggest that we group specific IDE support options within a generic IDE group. What do you think?

Contributor

kthoms commented Nov 15, 2016

I searched the wizard-related (also closed) bugs, but did not find it either. Thus I would like to discuss this issue here if that's OK.

As said, I suggest that we group specific IDE support options within a generic IDE group. What do you think?

@dhuebner

This comment has been minimized.

Show comment
Hide comment
@dhuebner

dhuebner Nov 15, 2016

Contributor

The option "Generic IDE Support" is mandatory for the options "Eclipse Plugin", "IntelliJ IDEA Plugin" and "Web Support". It is not intuitive that this option is the last one. It should be the first option that a user could choose and dependend on the option, the other options should be made selectable.

"Generic IDE Support" is more a technical aspect for advance users. Keeping in mind, that wizards are mostly used by people who tries things out or are giving demos (except Xtext consultants), it's better to show the really important thing in top of the wizard page. This things are sorted by importance for a common eclipse user

  • I need an eclipse plugin (preselected for eclipse IDE)
  • I need an IDEA plugin too (probably not)
  • I need web support (probably not)

The two other option like Generic IDE support and tests are considered as 90% needs this and are technical aspects.

If we compare the default wizard settings with the screen shot above :
bildschirmfoto 2016-11-15 um 13 41 28

I looks like the user goes from top to bottom and tries out the checkboxes. He disables a pre-selected checkbox and gets a feedback message about why it will not work and he also gets a quick-fix for that. IMHO it's a very good UX.

Contributor

dhuebner commented Nov 15, 2016

The option "Generic IDE Support" is mandatory for the options "Eclipse Plugin", "IntelliJ IDEA Plugin" and "Web Support". It is not intuitive that this option is the last one. It should be the first option that a user could choose and dependend on the option, the other options should be made selectable.

"Generic IDE Support" is more a technical aspect for advance users. Keeping in mind, that wizards are mostly used by people who tries things out or are giving demos (except Xtext consultants), it's better to show the really important thing in top of the wizard page. This things are sorted by importance for a common eclipse user

  • I need an eclipse plugin (preselected for eclipse IDE)
  • I need an IDEA plugin too (probably not)
  • I need web support (probably not)

The two other option like Generic IDE support and tests are considered as 90% needs this and are technical aspects.

If we compare the default wizard settings with the screen shot above :
bildschirmfoto 2016-11-15 um 13 41 28

I looks like the user goes from top to bottom and tries out the checkboxes. He disables a pre-selected checkbox and gets a feedback message about why it will not work and he also gets a quick-fix for that. IMHO it's a very good UX.

@kthoms

This comment has been minimized.

Show comment
Hide comment
@kthoms

kthoms Nov 15, 2016

Contributor

Neither you nor me are these "users" and are no UX experts. I will ask our UX experts to have a look.

Contributor

kthoms commented Nov 15, 2016

Neither you nor me are these "users" and are no UX experts. I will ask our UX experts to have a look.

@dhuebner

This comment has been minimized.

Show comment
Hide comment
@dhuebner

dhuebner Nov 15, 2016

Contributor

Neither you nor me are these "users"

That is the point, for the Wizard we need to focus on other users and not the Xtext experts. The result of our discussion a year ago was: The wizard should be as simple as possible, but allow tweaking advance thing.

The first shot of the wizard UI automatically changed and disabled settings depending on last user action and it was terrible.

Contributor

dhuebner commented Nov 15, 2016

Neither you nor me are these "users"

That is the point, for the Wizard we need to focus on other users and not the Xtext experts. The result of our discussion a year ago was: The wizard should be as simple as possible, but allow tweaking advance thing.

The first shot of the wizard UI automatically changed and disabled settings depending on last user action and it was terrible.

@kthoms

This comment has been minimized.

Show comment
Hide comment
@kthoms

kthoms Nov 15, 2016

Contributor

My feeling is that the page behaves confusing. IMHO it is not simple.
As said, I'll involve UX experts to get qualified recommendations, or did you involved them in the discussion?

Contributor

kthoms commented Nov 15, 2016

My feeling is that the page behaves confusing. IMHO it is not simple.
As said, I'll involve UX experts to get qualified recommendations, or did you involved them in the discussion?

@SanniSch

This comment has been minimized.

Show comment
Hide comment
@SanniSch

SanniSch Dec 19, 2016

Because of the discussion of this issue we conducted a Usability Test in which we compared three versions of the wizard: the original one (version 1), the proposal of @kthoms (version 3) and a solution in which "Generic IDE Support" is selected automatically when the three dependent options were selected (version 2). The test results showed that the current wizard supports the users worst. Version 2 supports them best.

You can find the detailed findings here: http://www.slideshare.net/SandraSchering/usability-test-results-xtext-new-project-wizard

Based on the findings, the wizard should look like the attached mockup. This means the current structure of the dialogue is the same. However, if a user selects "Eclipse Plugin", "IntelliJ..." or "Web Integration", "Generic IDE Support" is selected automatically, the checkbox becomes disabled and a hint is shown. The checkbox becomes active again if none of the three options is selected.

In addition, the results showed that the users did not understand some terms (especially "Generic IDE Support"). Tooltips should be added explaining the meaning of the options.
version2_automatic-selection

Because of the discussion of this issue we conducted a Usability Test in which we compared three versions of the wizard: the original one (version 1), the proposal of @kthoms (version 3) and a solution in which "Generic IDE Support" is selected automatically when the three dependent options were selected (version 2). The test results showed that the current wizard supports the users worst. Version 2 supports them best.

You can find the detailed findings here: http://www.slideshare.net/SandraSchering/usability-test-results-xtext-new-project-wizard

Based on the findings, the wizard should look like the attached mockup. This means the current structure of the dialogue is the same. However, if a user selects "Eclipse Plugin", "IntelliJ..." or "Web Integration", "Generic IDE Support" is selected automatically, the checkbox becomes disabled and a hint is shown. The checkbox becomes active again if none of the three options is selected.

In addition, the results showed that the users did not understand some terms (especially "Generic IDE Support"). Tooltips should be added explaining the meaning of the options.
version2_automatic-selection

kthoms added a commit that referenced this issue Jan 2, 2017

[#119] UX improvements for Generic IDE Support option
The Generic IDE option is disabled whenever a UI plugin is selected. If
it was not enabled before, it will be selected automatically and an
information about this will be reported to the status widget.

Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>

kthoms added a commit that referenced this issue Jan 3, 2017

[#119] UX improvements for Generic IDE Support option
The Generic IDE option is disabled whenever a UI plugin is selected. If
it was not enabled before, it will be selected automatically and an
information about this will be reported to the status widget.

Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>

kthoms added a commit that referenced this issue Jan 3, 2017

[#119] Added info decoration for options
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>

kthoms added a commit that referenced this issue Jan 3, 2017

[#119] Decorated description for Generic IDE Support option
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>

kthoms added a commit that referenced this issue Jan 4, 2017

Merge pull request #148 from eclipse/kth_issue119_ux_wizard
[#119] UX improvements for Generic IDE Support option

@kthoms kthoms self-assigned this Jan 4, 2017

@kthoms kthoms added this to the release_v2.11 milestone Jan 4, 2017

@kthoms kthoms added the enhancement label Jan 4, 2017

@kthoms

This comment has been minimized.

Show comment
Hide comment
@kthoms

kthoms Jan 4, 2017

Contributor

Fixed via 96ed73c

Contributor

kthoms commented Jan 4, 2017

Fixed via 96ed73c

@kthoms kthoms closed this Jan 4, 2017

kthoms added a commit that referenced this issue Jan 16, 2017

[#119] Auto (de) selection of Eclipse projects
The creation of a p2 repository requires the SDK project. If not
selected before, the feature project is automatically selected and an
information message about the selection is presented.
When 'Eclipse plug-in' is deselected, also the feature and p2 projects
are deselected.

Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
@kthoms

This comment has been minimized.

Show comment
Hide comment
@kthoms

kthoms Jan 16, 2017

Contributor

There is a similar situation with the dependency between the P2 and Feature project. The update site project requires the feature project. Therefore it should the same that the feature project is automatically selected and disabled when the update site project is selected and the user gets a message.
Further, it does not make sense to leave the feature and update site selected when Eclipse plug-in is deselected. The user could assume that the projects are still produced since the boxes are checked. The options should be automatically deselected. A further information in the status widget should not be necessary in that case.

Contributor

kthoms commented Jan 16, 2017

There is a similar situation with the dependency between the P2 and Feature project. The update site project requires the feature project. Therefore it should the same that the feature project is automatically selected and disabled when the update site project is selected and the user gets a message.
Further, it does not make sense to leave the feature and update site selected when Eclipse plug-in is deselected. The user could assume that the projects are still produced since the boxes are checked. The options should be automatically deselected. A further information in the status widget should not be necessary in that case.

@kthoms kthoms reopened this Jan 16, 2017

kthoms added a commit that referenced this issue Jan 16, 2017

[#119] Auto (de) selection of Eclipse projects
The creation of a p2 repository requires the SDK project. If not
selected before, the feature project is automatically selected and an
information message about the selection is presented.
When 'Eclipse plug-in' is deselected, also the feature and p2 projects
are deselected.

Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>

kthoms added a commit that referenced this issue Jan 16, 2017

Merge pull request #160 from eclipse/kth_issue119_2
[#119] Auto (de) selection of Eclipse projects

@kthoms kthoms closed this Jul 9, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment