TrackStack mockup help request

[Michael Allan]

> The other option is to skip tracklets and simply show the current
> top one, which we had before for the node itself... Do you think we
> need the tracklets or is there a compacter visual?

I guess I asked the wrong question in my last post.  I asked what's
the purpose of the parent tracklets (top), but the crucial question
is, "What's the purpose of the child tracklets?"

The topmost parent (the one you've been designing all along) shows
progress toward a target of resource accumulation.  It does a good job
of that.  The basic elements (segmentation, arrows, width) are all
excellent.  OK.

Does the progress change as we climb the tree?  Maybe.  It can change
if the account definition changes and redefines the target, for
example.  This could happen when climbing from B to A:


                       ( )  ( )  ( )
                         \   | 1 /
                          \  |  / 1        ( )   ( )
                 ( )  ( )  \ | /            | 1  /
        ( )        \ 1 |    \|/             |   / 1
          \ 1       \  | 1  (2) *A*         |  /
           \         \ |     |              | /  ( )  ( )
            \         \|     | 1            |/    |   /
         1   \        (2)    |         *C* (2)    |  /
     ( )-----(2)        \    |              |     | /
               \ 1       \   |              |     |/
                \         \  |              |    ( )-----( )
                 \         \ |        ( )   |    /
              1   \         \|          \   |   /
  ( )-----( )-----(4)       (5)          \  |  /
                    \       /             \ | /
                     \     / 1             \|/
                      \   /                ( )
                       \ /
                       (10) *B*

  [SAC]. Superaccounting in a delegate voting structure.  Three
         accounts are shown (A, B, C).  The counting method is a
  hypothetical "unit summation" method in which a voter may pledge 1
  or nothing.  Each number in brackets shows the total quantity of
  pledges received by a candidate and destined to flow to one of the
  terminal accounts (B or C) where they are removed from the flow and
  "held".  (from http://zelea.com/w/Category:Account)

But that's no problem.  Your original design can handle that.  No need
even for a mockup.  So OK, the progress track is fine.  But what were
those other tracklets showing, if not progress?  And why?

Maybe try this:

  1. Paste your simple progress track on top of these mockups:
     http://zelea.com/project/votorola/a/xf/vote/_/1.xht
     http://zelea.com/project/votorola/a/xf/vote/_/2.xht
     http://zelea.com/project/votorola/a/xf/vote/_/3.xht

     Paste it directly into the SVG.  Paste only the simple track (3
     strong elements) to avoid noise and confusion.  Show exactly the
     same track visual at all three levels.

  2. Let's all look at it.  We'll flip back and forth among the three
     mockups (up/down tree) and ask, "Is this OK?"

I have an idea, nothing definite... and anyway, it can be fun to look
at a problem before seeing the solutions... and people come up with
interesting ideas.

-- 
Michael Allan

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


conseo wrote:
> Hey M,
> 
> > 
> > Stacking up multiple "tracklets" is an interesting idea.  I think
> > it'll work on a desktop, but I'm worried it'll chew up too much space
> > on a mobile device..  Imagine we have multiple tracks in the stack for
> > this account type [1]:
> >>>>>>>>>>>>>>>>>>>>> snip ascii mockups
> > 
> > 
> > The above exaggerates the track height (maybe by 4X), but it shows the
> > problem.  There might be enough room on a desktop, but it has to run
> > on small mobile screens too (maybe 1/4 or less space).  And three
> > tracks is probably not enough to cover all use cases, I think we want
> > to support at least five or six.  So even *un-expanded* tracks are
> > going to take up roughly half of votespace...
> > 
> > What's the purpose of parent tracklets (3a-d)?  Is there a better
> > (less spacious) way of accomplishing the purpose?
> > 
> 
> The other option is to skip tracklets and simply show the current top one, 
> which we had before for the node itself. This carries some problems though. A 
> single node can be very small compared to the target, so we have to find 
> something else to measure it and give a sense of overall state/progress. This 
> why I have come up with the "tracklets" in the first place. Do you think we 
> need the tracklets or is there a compacter visual?
> 
> I have resized the tracks to 2/3 of its parent (1).
> 
> We can solve the space problem for too much stacks of any kind like that: 
> NOTE: each plus is supposed to represent one hidden track (could be an icon if 
> it was for a single track type). Track is (2/3)^4 wide and only consists of 
> its own resources (it is therefore the grey (always first)).
> 
> 
> This also underlines why i see some problems in directly applying this Ui for 
> mobile. Or am I doing it wrong? Maybe you have a specific mobile-compatible 
> widget style in mind Mike? I have done the circles in VoteSpace just to 
> underline that visual. I don't need them.
> 
> 
> conseo
> 
> (1) http://whiletaker.homeip.net/mockups/5/5a.ns.level2.xht
> (2) http://whiletaker.homeip.net/mockups/5/5a.ns.level4.hide.xht