-
Currently, this is the behavior of clicking on a node:
**Github Icon**: Go to github.com
**Issue title**: Go to that issue on github.com
**Clicking/Hovering depends/related/blocks icons**: Nothin…
-
We need to have fewer entity types that share more common fields and have some specific ones.
---
Here is the first idea:
* Task
* Attributes:
* Type -> the type
* IsDummy -> if …
-
-
The graph today is walked backs to the _dependencies_, but does not show _dependents_ directly, as this involves walking backlinks, or other references.
- See original designs
- There's some discus…
-
Currently, you're only allowed to declare the dependencies in a "depends on " message in the top-level issue. There have been some discussion that this is not enough, and we should be able to declare …
-
The “navigate by clicking on nodes” idea has come up a few times (#2, #17, #30), but the current implementation is based on dragging the `viewBox` around. As I [mentioned][1] in #17, cards are a bit …
wking updated
7 years ago
-
It looks like there's no functionality to traverse a scene graph (ie. parent/child connections). Is that correct? Just checking in case I'm blind, before I implement it myself.
I see the connection…
-
We don't do this at the moment (there's a FIXME in the GitHub module). Screenshot for the designed display in #9. Related but (I think?) distinct idea in #15.
wking updated
7 years ago
-
Would be nice to be able to have a "rapid prototyping" for the dot code, or its generation. Basically, a special window we can show and edit the generated dot on a text area directly on the page, and …
-
Here I will write down some references, ideas, requirements and generally thoughts on how to tackle this.
What I want is some kind of visualization to show how different issues on gitlab or github…