dashboard with studies

Comments on the original and on yoroy's version.

- @yoroy - Having the disclosure triangle at the start of the row fixes a confusion point. With it in the second column, it isn't immediately clear what it is.

- The disclosure triangle looks a bit like a "play" button on a media controller. Is departing from the default triangle purely aesthetic, or was there another motivation?

- @yoroy - I agree the expanded study should be highlighted in some way, but I'm not sure about the blue border. What about changing the background colors for the expanded rows a bit? Perhaps bringing the saturation more towards gray?

- I'm not sure what the participant count on each task is trying to tell me. Is it the number of the test total that have completed the task? I.e., 5/5 have completed "Create a menu" and 2/5 have completed "Place menu block in a region"? If so, I think this may be a little redundant with the completion rate bar graph next to it showing the same information. @yoroy - Indenting this number does separate it from the study total, but it now looks like a column with no header.

- Do the bar graphs have tooltips providing numerical data on percentage complete?

- @yoroy - Changing the appearance of the task bar graphs from the study bar graph is good since it indicates they are not equivalent individually with the study. I'm not clear on how these individual graphs are used to compute the parent graph, but that may not be a question that most user ask.

- The button and menu on the right seem really out of place. Are these meant to replace the action tabs normally on top?

- The 'Create Study' button looks a bit like a header for the items below it, and the plus symbol looks a lot like the draggable indicator on the block admin page.

- A button is a call to action -- an interruption in the flow of reading. It's typically used as a sort of punctuation on interfaces. For LTR language readers, the eye will scan across the table header and then to the button. Is this where you want that interruption to happen? Even if it is where you want the reading break to happen, it's very different from the other interfaces the user will have already encountered while using Drupal.

> - We are working on the highlighting, from a tab idea purposed in the other issue.

The highlighting ideas in #307946: Study Dashboard are looking really nice.

> - The play button is a Mac.com thing, we could change it, do you have an idea?
> I am not sure if Drupal ones applies very well.

I think moving the triangle to the left of the text removes most of the ambiguity. Next to the number, it might be taken as a control to start the study. Apple uses a solid triangle on their desktop UI for disclosure areas. Microsoft uses a round button with two downward chevrons to indicate an area will expand; the chevrons point upward when the area is expanded.

> - Regarding the graphical bars of tasks, I am not sure what you mean. It is
> essential information to display.

I didn't mean the bar graphs themselves; I was referring to the indented participant count for each task. That number seems redundant and a bit out of place. For the study itself, the number in the participants column means how many people have started that study. For the task rows, the context of that number changes to be the number of participants that have completed the task. Completion rate has the same context for study and task.

> - I am not sure on your notions of the right menu, it is definitely a completely
> different way of navigating in Drupal is it therefore out of place aesthetic?

I don't think I understand the context of the items in this menu. Are they all top level actions, or are some of them contextual? The items in this menu changes when viewing an individual task (mock-up in 307946).

I'm not sure there is an existing precedent in Drupal for adding this sort of functionality. I'd look at some other modules that add large blocks of functionality such as CCK, Views, and Panels. I don't think there's a consistent pattern, but possibly some ideas, and probably something that should be touched on in the HIG.

> - We definitely want that interruption to happen, it is one of the most
> important tasks on this page.

What about putting a header over that section with a label like "Actions" and changing create into a link like the items below it? Elsewhere in Drupal, a button is an action on the current form or is in the context of a previous action (confirming a delete, for example); this is breaking that pattern.

Is there documentation such as use cases on how you intend the user to move through UTS performing various tasks?

Looking at this and the other related UTS user interface issues, the project is looking really good.

This looks really nice.

I only have two suggestions on this one:

1. Change "Progress tasks" to "Task progress" for the English strings.
2. In the tooltip over task such as the "Add several menu-items" task that you've annotated, provide information has to why 5/5 isn't fully complete. That may be needed the first time someone is using UTS to indicate how the participant count / participant slot ratio differs from the task progress bar.

Great work!