Moodle

Work on Question Bank UI to ensure at least minimal consistency with new Quiz UI

Details

  • Type: Sub-task Sub-task
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0
  • Fix Version/s: 2.0
  • Component/s: Quiz
  • Labels:
    None
  • Affected Branches:
    MOODLE_20_STABLE
  • Fixed Branches:
    MOODLE_20_STABLE

Description

At least some UI enhancements (especially from the new Quiz Question Bank Window should probably be taken to the Question Bank's own UI, too, to stay consistent.

This was CONTRIB-643

Issue Links

Activity

Hide
Tim Hunt added a comment -

Moving, for my convinience.

Show
Tim Hunt added a comment - Moving, for my convinience.
Hide
Olli Savolainen added a comment -

Related: ensure the links for moving from and to the question bank in quiz editing, quiz paging/ordering and question bank editing are in the same place in all the three user interfaces, to make switching between quiz and question bank as seamless as possible.

Tim, I see you've assigned this to yourself. I will be willing to at least keep a close look on the progress, unless I will find the chance to work on it myself. Do you plan to do the refactoring of the question bank display functions for question bank and for quiz while making the UI's consistent?

Show
Olli Savolainen added a comment - Related: ensure the links for moving from and to the question bank in quiz editing, quiz paging/ordering and question bank editing are in the same place in all the three user interfaces, to make switching between quiz and question bank as seamless as possible. Tim, I see you've assigned this to yourself. I will be willing to at least keep a close look on the progress, unless I will find the chance to work on it myself. Do you plan to do the refactoring of the question bank display functions for question bank and for quiz while making the UI's consistent?
Hide
Olli Savolainen added a comment -

Oops, didn't notice those three bugs was what this was all about.

Show
Olli Savolainen added a comment - Oops, didn't notice those three bugs was what this was all about.
Hide
Tim Hunt added a comment -

I done some work on this. There is probably more to do, but I will tackle it as part of other subtasks. I don't need this one any more.

Show
Tim Hunt added a comment - I done some work on this. There is probably more to do, but I will tackle it as part of other subtasks. I don't need this one any more.
Hide
Olli Savolainen added a comment - - edited

Thanks. Looks more consistent now.

Hate to be the one to be finding faults in your work all the time, though I guess you must be used to it already... I know, I could have said more of this earlier. Anyway, here goes:

In the quiz editing view's question bank window, the change seems to have broken the CSS to cut longer-than-table-width question texts with overflow:hidden; and white-space:nowrap; so now the table gets blown out of viewport whenever the question text is just a bit longer ... there were some quite intricate things that needed to be true in the CSS to make that work, but I cannot seem to remember what they were. (That kind of CSS would be useful in the actula question bank, too though - to test, I had questions with really long question names and the layout broke pretty badly, had to edit that question to see what your new layout looks like.)

Further consistency would also be nice, as you mention - Namely, separating the category selection from the category name, and graphically linking the category name with the description, to avoid issues such as this: http://docs.moodle.org/en/Development:Quiz_UI_redesign_-_prototype_testing_report#Issue_2 , and solved by the current design in quiz editing in the following testing: http://docs.moodle.org/en/Development:Quiz_UI_redesign/usability_testing_of_August_2008/Executive_summary#Issues_that_were_solved_from_previous_iteration

Also, I am betting that [Delete][Move to >>][Default for course fullname \/] is causing some serious confusion as to which control is related to what. This could be easily fixed by making the ordering and labeling more standard:
[Delete] * Move to: [Default for course fullname \/][Move]

  • (some horizontal space, say 1-2em, according to gestalt laws, to have users group the elements as separate)
Show
Olli Savolainen added a comment - - edited Thanks. Looks more consistent now. Hate to be the one to be finding faults in your work all the time, though I guess you must be used to it already... I know, I could have said more of this earlier. Anyway, here goes: In the quiz editing view's question bank window, the change seems to have broken the CSS to cut longer-than-table-width question texts with overflow:hidden; and white-space:nowrap; so now the table gets blown out of viewport whenever the question text is just a bit longer ... there were some quite intricate things that needed to be true in the CSS to make that work, but I cannot seem to remember what they were. (That kind of CSS would be useful in the actula question bank, too though - to test, I had questions with really long question names and the layout broke pretty badly, had to edit that question to see what your new layout looks like.) Further consistency would also be nice, as you mention - Namely, separating the category selection from the category name, and graphically linking the category name with the description, to avoid issues such as this: http://docs.moodle.org/en/Development:Quiz_UI_redesign_-_prototype_testing_report#Issue_2 , and solved by the current design in quiz editing in the following testing: http://docs.moodle.org/en/Development:Quiz_UI_redesign/usability_testing_of_August_2008/Executive_summary#Issues_that_were_solved_from_previous_iteration Also, I am betting that [Delete][Move to >>][Default for course fullname \/] is causing some serious confusion as to which control is related to what. This could be easily fixed by making the ordering and labeling more standard: [Delete] * Move to: [Default for course fullname \/][Move]
  • (some horizontal space, say 1-2em, according to gestalt laws, to have users group the elements as separate)
Hide
Olli Savolainen added a comment -

That is, it seems to me that those same gestalt laws, namely the law of proximity, explain why there would be a problem now - the automatic processes of perception group the three controls as /one/, not two groups and thus the user has to think to make sense of what his/her "intuition" cannot make sense of.
http://www.interaction-design.org/encyclopedia/gestalt_principles_of_form_perception.html

Show
Olli Savolainen added a comment - That is, it seems to me that those same gestalt laws, namely the law of proximity, explain why there would be a problem now - the automatic processes of perception group the three controls as /one/, not two groups and thus the user has to think to make sense of what his/her "intuition" cannot make sense of. http://www.interaction-design.org/encyclopedia/gestalt_principles_of_form_perception.html
Hide
Tim Hunt added a comment -

This is all very much work in progress. It would be better if you waited a week or two, until almost all of the subtasks of this issue's parent have been finished. I have not got onto the search options and bulk actions UI yet. That will happen next week. I think the long question text issue got fixed again in the middle of this afternoon (so, about 9 hours ago).

Show
Tim Hunt added a comment - This is all very much work in progress. It would be better if you waited a week or two, until almost all of the subtasks of this issue's parent have been finished. I have not got onto the search options and bulk actions UI yet. That will happen next week. I think the long question text issue got fixed again in the middle of this afternoon (so, about 9 hours ago).
Hide
Olli Savolainen added a comment -

Oh, right, I always fail to navigate these tasks... I hope it didn't all go to waste, anyway.

Show
Olli Savolainen added a comment - Oh, right, I always fail to navigate these tasks... I hope it didn't all go to waste, anyway.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: