656314 - the results pane should use the hierarchical design for a "Basic" navigation

Status: RESOLVED FIXED

(Mozilla QA Graveyard :: MozTrap, enhancement)

Description

[Cameron Dawson [:camd]]

We should investigate using the hierarchical view as the "Basic" or "default" way of finding results.  And if the user wants to slice the results view in a more custom way, they can use the tabs to see the "Raw" lists and use "Filtering" to get just what they want.

Filtering should be available in both hierarchical and raw mode, however.

Perhaps we should even hide the raw lists and show them via a link of some kind.

Comment 1

[Cameron Dawson [:camd]]

A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/13274459

Comment 2

[Cameron Dawson [:camd]]

Cameron Dawson changed story state to unstarted in Pivotal Tracker

Comment 3

[Cameron Dawson [:camd]]

Eric Meyer changed story state to started in Pivotal Tracker

Comment 4

[Cameron Dawson [:camd]]

Eric Meyer added a comment in Pivotal Tracker:   
   
Jonny: I'm working on this at /wire/design/ at the moment. I've added a "view toggle" link in the top right corner that should change the .finder class (as well as it's own class) from 'expanded' to 'compact'. At the moment that doesn't do anything, but if you make the toggle happen, I'll get to the styles asap.

Comment 5

[Cameron Dawson [:camd]]

Eric Meyer added a comment in Pivotal Tracker:   
   
Jonny: another feature you could add here. :) Can you change the [bracketed] items in the button below depending on what column I've selected last?

Comment 6

[Cameron Dawson [:camd]]

Jonny Gerig Meyer added a comment in Pivotal Tracker:   
   
Eric: Do you want the rest of the selectRuns js pulled in on this page too?

Comment 7

[Cameron Dawson [:camd]]

Jonny Gerig Meyer added a comment in Pivotal Tracker:   
   
Eric: And add more sample data, horizontal-scroll, etc.?

Comment 8

[Cameron Dawson [:camd]]

Jonny Gerig Meyer added a comment in Pivotal Tracker:   
   
Eric: The basic JS is in place, and seems to work fine. Let me know if you want anything else added/changed. I'm turning this over to you.

Comment 9

[Cameron Dawson [:camd]]

Jonny Gerig Meyer added a comment in Pivotal Tracker:   
   
Eric: I wasn't sure what to do with the open links in the last section (results). You can see what I did ("see this result") and let me know if you want me to change it.

Comment 10

[Cameron Dawson [:camd]]

Eric Meyer added a comment in Pivotal Tracker:   
   
sorry, jonny, i missed one detail here. those links will also need titles (as per the products now). I'm fairly certain we'll want the tooltips on hover.

Comment 11

[Cameron Dawson [:camd]]

Carl Meyer added a comment in Pivotal Tracker:   
   
Modified the title of this story to reflect that we're actually considering it to cover the use on both Manage and Results pages.

Comment 12

[Cameron Dawson [:camd]]

Carl Meyer added a comment in Pivotal Tracker:   
   
Never mind, we already had a story for the manage pane, we just weren't using it. Going to keep both.

Comment 13

[Cameron Dawson [:camd]]

Jonny Gerig Meyer added a comment in Pivotal Tracker:   
   
Initial support for a callback fn is implemented on /wire/run/. I'll update it as necessary when I see a real use case.

Comment 14

[Cameron Dawson [:camd]]

Carl Meyer changed story state to finished in Pivotal Tracker

Comment 15

[Cameron Dawson [:camd]]

Carl Meyer changed story state to delivered in Pivotal Tracker

Comment 16

[Cameron Dawson [:camd]]

Cameron Dawson added a comment in Pivotal Tracker:   
   
looks awesome!

Comment 17

[Cameron Dawson [:camd]]

Cameron Dawson changed story state to accepted in Pivotal Tracker