This page is for tracking User Experience issues and discussions that appear on the Sakai mailing lists and elsewhere in the community. The UI Working Group will use this page as a way to keep track of ongoing issues, offer advice to the community and help guide our work with Design Patterns.
| Name | Description | Thread | JIRA |
|---|---|---|---|
| Date Widget / Editable Fields |
We wanted a consistent and user-friendly date widget to be used across the site. It would 1) enable keyboard- and mouse-only interaction to set date and time, 2) display localized date/time format (easier to understand), 3) take up minimal screen real-estate. The design in progress displays the date in full-date format above the textbox in grey, while allowing the users to change the quick date format in the textbox. The calendar is always displayed to give additional information but is quickly dismissed when the user clicks elsewhere. The start and end dates are colour-coded. |
Nabble Date Picker Widget Wiki Page on Fluid |
http://jira.sakaiproject.org/jira/browse/SAK-11688 |
| Pager | We wanted to improve the current page navigation design within Sakai to allow users to 1) see how many items there are in the entire list and where they are within the list, 2) quickly jump to a desired item, 3) modify the size of the page. The design in progress allows you to find a specific item (using the Find feature), jump to a specific page by typing in the page number, change the number of items per page using the dropdown, access the pager at the top and bottom of the page, and shows the total number of pages and items at all times. |
Nabble Smart Page Navigation Wiki Page on Fluid |
|
| SAK-12402 Portal support for minimized navigation / frameset mode | Nabble | http://bugs.sakaiproject.org/jira/browse/SAK-12402 | |
| Display of Help/Global Tools | Nabble | ||
| When to use delete versus remove terminology |
Both terms are used in Sakai. The question is can it be consistent or are they 2 different activities that the user needs to understand. Does the terminology need to be more explicit? At a minimum, Design pattern(s) are needed here and potentially design suggestions for each existing terminology use across Sakai. |
Coming soon -- new email address is being added to nabble. |
http://bugs.sakaiproject.org/jira/browse/SAK-9678 |
| "To save or not to save" state |
Currently some tools do and some don't. The fuzzy line is something like "legacy" tools do and new ones don't. There is a long standing debate about the right thing to do. That debate should be reopened based on data about what the state of things is. But the WORST USABILITY issue is that we currently have a mix. So users have not way to build expectations around system behavior. It's likely they can't even identify this kind of issue and blame themselves for resulting loss of data. Possible problematic use cases (which need to be verified by testing and have concrete tool examples added):
|
This discussion goes back to day 1 of the project. It will take some effort but would be good to have a list any documented discussion around this here. |