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

QT GUI usability problems #2030

Open
omnidan opened this Issue May 26, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@omnidan
Contributor

omnidan commented May 26, 2018

the usability test for Elektra Web also uncovered some problems with the QT GUI:

  • when keys have subkeys, but none of those subkeys have further subkeys, they are shown with a black arrow instead of the usual green one:

screen shot 2018-05-26 at 20 34 45

  • in general it is not clear where information appears (e.g. some users didn't see the search results, others clicked on a key and didn't see that something popped up on the right)
  • key values are only shown when hovering over the key or double clicking to get to the edit dialog
  • copy & pasting array keys does not work (creates a key with the same id)
  • it is not possible to edit names of array keys (which makes it impossible to fix the copy & paste issue)
  • it is not clear that the box when editing a key contains metakeys (only the button at the bottom "new meta key" hints at it), some users thought it contains subkeys, maybe add a title to this section
@markus2330

This comment has been minimized.

Contributor

markus2330 commented May 26, 2018

Thank you for reporting the problems! I think some clarifications are needed (what was expected, what the users tried to do,...)

Maybe you can also separate usability problems and the actual bug (copy&pasting array keys).

@0003088 please write if it is not clear to you what the individual problems were.

@0003088

This comment has been minimized.

Contributor

0003088 commented May 27, 2018

Thank you for your input. Do I guess correctly that you tested your GUI with an audience and included the qt-gui as well?

The first mentioned issue is no bug but a feature. It should inidicate that there exist further subkeys, without the indicator one would have to click every key in the treeview to see if there are subkeys. Or is the problem that the subkey indicator does not look similar to the expansion icon? Since the icons do have different functions I thought they should be visually different as well.

As far as I remember I experimented with colors to indicate that a search result was successful (green) or unsuccessful (red). It might be useful to implement something like that.

That the key values are only shown by hovering or clicking is true, but I did not have any better idea to solve the problem considering the general design of the viewports.

The copying and pasting issue of the arrays seems to be a bug as is the next array related icon, I will see what can be done.

Thank you for your last suggestion, this should be an easy fix.

@markus2330

This comment has been minimized.

Contributor

markus2330 commented Jun 2, 2018

Do I guess correctly that you tested your GUI with an audience and included the qt-gui as well?

Yes, it was an A/B test with Web-UI and qt-gui. You can read about the details in Daniel's bachelor thesis (to be finished soon, preliminary version is in our private repo).

Or is the problem that the subkey indicator does not look similar to the expansion icon?

Yes, I also think it is a good idea to have different icons there. Maybe the usability is better if the "Key Name/Key Value" view is also used if non-leaves are selected (up to all keys of a namespace). For irregular-shaped "trees" (especially if exactly one key has subkeys but no other) the right view is nearly always empty and the hints (hover text) need to be used very often.

That the key values are only shown by hovering or clicking is true, but I did not have any better idea to solve the problem considering the general design of the viewports.

Maybe reducing the time when the hover text is shown might already help.

The copying and pasting issue of the arrays seems to be a bug as is the next array related icon, I will see what can be done.

Thank you!

We decided that arrays should have the metadata "array" containing the last index (see #182). This should make detection of arrays easier. It would be nice to see support for it in the qt-gui.

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