W. Trevor King

I think it may be easiest to do this in a dev environment (`npm start`) by editing `Graph.graphviz`, saving `Graph.js`, and letting the tooling rebuild/reload your view. If you use...

On Mon, Nov 28, 2016 at 01:24:20PM -0800, Juan Benet wrote: > This may be waiting on proper graphviz path drawing… Graphviz edges are #24. The Graphviz edges have arrow...

I still think the main point of this issue should be getting non-color indicators for done-ness and deps vs. blockers, but for kicks here is how the current scheme looks...

On Fri, Dec 02, 2016 at 11:42:33PM -0800, W. Trevor King wrote: > * Blockers vs. dependencies (currently a red/green pie, #12). I've spun off two non-circle blocker shape ideas...

For an issue list of any size, I expect having your related nodes all on screen is unlikely. We could keep your hover stuff, but add click-to-(un)select, which would hide...

Is the sort order something like: function sortNumber() { return youAreOpen * bigNumber + sumOverDependants(dep.sortNumber()) / 2 + createdSecondsSinceEpoc / hugeNumber; } Where `hugeNumber` is big enough for creation time...

And is this orthogonal to expanded-ness? I.e. will links look like `?expanded=true&list=true` or `?view=list`? I like the former (with a wide version of the expanded card) because I really like...

And just to clarify, the dark red background and bold ID in your mocks are “this is the selected node”? And the background grows to the right to represent the...

> not sure on that sort function What do you think of [`listSortKey`][1]? [1]: https://github.com/jbenet/depviz/pull/70/files#diff-8e87d2ee81503ad224acbccf576b924dR184

On Mon, Nov 28, 2016 at 12:13:10PM -0800, ᴠɪᴄᴛᴏʀ ʙᴊᴇʟᴋʜᴏʟᴍ wrote: > * Have a `depviz.json` file in the repository I'd rather not, since the issue cloud is fairly independent...