User photograph in votespace

[Michael Allan]

Hey C,

We were speaking about the photo too, yesterday:
http://whiletaker.homeip.net/mockups/3/trackstack-proto3.ns.png

I forgot what the #1 problem was at the time.  I thought it was
brightness, but there are programmatic solutions for that, ofc.  The
#1 problem is actually the overlap and/or traversal as we move to
higher/outer circles.  This means that the photo *cannot* be placed in
center.  So where can it be placed?
http://zelea.com/project/votorola/a/xf/vote/_/3.xht

Maybe we place it inside the outermost circle.  So just left/below
Fr. on the radial line to Ol (see 3.xht).  It could be fairly large if
need be, but not as large as in your mockup.  In any case, it will
sometimes be partly obscured by data on the radial line (numbers or
whatever the current SAC puts there).  That data must sit in front of
the photo where it is always visible, probably on a dark background.
The radial lines themselves will not obscure the photo however,
because they will run behind.

But again, this has no affect on layout.  We can defer the photo till
we actually need it.

-- 
Michael Allan

Toronto, +1 416-699-9528
http://zelea.com/


Michael Allan wrote:
> Hi C,
> 
> It occurs to me that the center photo in your latest mockups is more a
> part of the votespace design than the track stack.  When a stack is
> deployed in the difference bridge and other non-theatre pages, there
> won't be a center photo.  http://whiletaker.homeip.net/mockups/3/
> 
> So I think it factors out of the track design effort, as something
> separate.  It's a great idea, and I hope we can iron out the problems.
> (It now occurs to me that overlap of higher voter circles as we climb
> the tree is the #1 problem.)
> 
> Anyway, I think you're right to focus on this:
> 
> > My main concern atm. is how to react to a click on a TrackStack
> > segment.
> 
> When a segment is clicked, it'll most likely be the same as clicking a
> node in votespace.  Otherwise it's going to be weird that the two
> visuals (track and votespace) are disconnected.  By the same token,
> when a node is clicked, it'll be the same as clicking a segment.
> 
> So it looks like you must climb the tree, showing segments of the
> higher voter circles.  How to reconcile this with the progress
> indicator is something of a problem, because the higher circles will
> have much less resource volume = much less apparent progress.
> 
> -- 
> Michael Allan
> 
> Toronto, +1 416-699-9528
> http://zelea.com/