You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
suppose we have a general way to map from one poset to another.
i.e.
from data -> html
from fs -> ansi
from data -> visualization
etc! it's probably possible to create quite a wide range of visualizations that work for different sorts of data - but I also bet there is considerable advantage from just being able to view the structure in a general way.
Also, this binding must be lazy, so that the details of some node doen't load until you zoom into it, or scroll down, or click open - or whatever.
Without going down the full blown ZUI route just yet a simple Hasse diagram would indeed be pretty sweet. I remember thinking a few months back that this d3 example was most of the way there: http://bl.ocks.org/mbostock/999346
Activity
refset commentedon Mar 22, 2013
Without going down the full blown ZUI route just yet a simple Hasse diagram would indeed be pretty sweet. I remember thinking a few months back that this d3 example was most of the way there: http://bl.ocks.org/mbostock/999346
dominictarr commentedon Mar 23, 2013
Yup, and there are a bunch of ways you could represent it too,
Like, for a normal tree, like the fs (ignoring symlinks) you could represent parents as boxes that contained the children.
The objective here would be to map in a generic way, so that it could adapted to any dataset, and so that custom data could be easily mapped.