TrackStack mockup help request

conseo 4consensus at
Tue Oct 11 19:30:49 EDT 2011

Michael Allan wrote:
> Hi C,
Hey M,

> Other work has kept me away, and then the thanksgiving holiday on top
> of it.  But I wanted to mention what I already mentioned on #votorola,
> I think this design is rocking!  I can't comment yet on the history
> (bottom track), except to say I think it should be a separate series
> of mockups (I recall Thomas suggests similar) because it's a separate
> design effort in many ways.
Maybe yes. But to understand how to visualize different one-dimensional 
aspects and at the same time connect them on mouseover I needed a second 
meaningful TrackStack. History including an ETA is also a very valuable 
information. Or have you thought about other visuals?

> Regarding the resource accumulator (top track) my favourite is:

> The combination of segement + arrow motifs is superb, and that part of
> the visual seems perfect.  Other parts (ignoring the history track for
> now) do not seem to add much.  I would look at eliminating them.  My
> suggestions:
>   1. Remove the yellow 1,000,000 (votes needed?) and the red 487,320
>      (current votes?).  That kind of detail will be more repelling
>      than attractive to first time viewers, and I think it mars the
>      overall visual.
>      Is there a way to reveal the details more gently as the user
>      explores inquiringly with the mouse?  At other times, they should
>      be invisible.
I have to think about it. At least the current count in front of the 
SacSelctor made some sense to me, since when I see the unit/superaccount I am 
interested in the amount as well. Otherwise we could hide both imo. We can 
also do a TrackStack which shows all different resources and allows to select 
them from there.

>   2. The mouse over cue (green) is too bright.
>      A slight brightening/dimming of the fill colour, or other subtle
>      cue is probably all that's needed.  The user is already looking
>      directly at the mouse pointer and will notice the effect, and
>      understand: if I click, I will get more info.

Ok. I have done that to underline the visual, but it harms the view.

>   3. The hover popup (with avatar etc) seems was too much.  (Again, I
>      think Thomas or someone suggested similar.)  I will actually
>      frighten the users a little bit.  They'll become scared to move
>      the mouse anywhere near the track for fear of seeing that window
>      pop up unexpectedly.  Must be gentle.
That's right. I have put the avatar in there to show its effect. The girl 
looks feisty, so she pulls a lot of attention. At the same time, she really is 
the driver behind the visual data and Thomas agreed with me that it makes 
sense to give activists some individual space to remember them.

>      Remember, when the track is not functioning as a mere attractor
>      (in diff bridge say) but as a workaday tool, then votespace is
>      there too.  Any hover effects over user nodes will be similar
>      between the two.  My own plan is to use a HUD to bottom left of
>      the track stack.  I'll project the username there in semi-opaque
>      grey (I guess) whenever hovering over a node in the tree.
>      Probably no other info is needed, right?  You get more info if
>      you actually click, of course.
Well, but since our approach is so modular, we don't know yet if people will 
use our tools more over the embedded view on activists' pages or load a full 
Crossforum page. We need to show relevant information on mouse-hover quickly 
to get user's interested, if they need to visit Crossforum first they will get 
confused. Having said that I think we need a HUD for the attractor-version as 
well. And the MailishUsername alone is not enough, people are not familiar 
with the naming and they don't see that this is an individual activist. 
Activists who contribute their time have a right to be shown and easily 
identified. They are our "content".
>      Remember too, clicking on a node in votespace takes you up/down
>      tree, so presumeably clicking on a segment does, too.
Yes. It is the Votespace circle in a linear fashion and should share behaviour 
imo. Mouseover a segment -> same hud. Left click on a segment -> select 
candidate. Mouseover should also highlight each others segments.

>   4. I would show all mockup states on a single page.  So a series of
>      multiple mockups, one for each state: plain, mouse over, mouse
>      click, etc.

> That's mostly the stuff to take away; but I guess there's also stuff
> to add.  One may want to navigate to the account page in the pollwiki,
> for example.  There's also a question about what happens as the user
> climbs the vote tree.
Hmm. What is the problem here? Votespace visualizes the tree structure very 
well already, right? We could add a level indicator to the Left caption, if 
this is what you meant. For the resource page we could add an icon with a link 
for the resource type in front of the TrackStack line.
I will think about it.
> conseo wrote:
> > Added 2ga.m2.xht (1) which visualizes a mouse over of one of the
> > segments in the history TrackStack. Should I show the complete visual
> > like in 2ga.m1.xht (2) or is a simple tooltip like version better for
> > the segements? ...
> > (1)
> > (2)
> These two look to be identical.  I would avoid tooltips for anything
> but a tool, since many users hate the things.  They already expect
> them in toolbars, but not in visuals.  HUD is nicer, because it's in a
> fixed location and it's less in-your-face.
> Good work, I love that accumulation arrow!
Ok. But you don't like the history view?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Votorola mailing list