npm install --save force-horse
With a modules bundler (recommended):
import 'force-horse'; // Imports the web component, not compiled
// OR
import 'force-horse/dist/main.bundle.js'; // Compiled. Less recommended because can't dedupe
@import 'force-horse/src/index.scss'; // Imports the SCSS index file, not compiled
// OR
@import 'force-horse/dist/style.bundle.css'; // Imports the bundle as CSS, compiled
Directly from HTML:
<link rel="stylesheet" type="text/css" href="node_modules/force-horse/dist/style.bundle.css" />
<script type="application/javascript" src="node_modules/force-horse/dist/main.bundle.js"></script>
From the template
<!-- Web component -->
<force-horse data='{"nodes": [], "links": []}' config='{"anything": true}'></force-horse>
<!-- Angular: Note that you have to add CUSTOM_ELEMENTS_SCHEMA -->
<force-horse [attr.data]="data | json" [attr.config]="config | json"></force-horse>
From Javascript:
const forceHorse = document.createElement("force-horse");
forceHorse.setConfig(someConfig);
forceHorse.setData(someData);
someContainer.appendChild(forceHorse);
To be rendered, force-horse must first get data
, which can be passed as an attribute, or directly using setData
A force-horse element does not have an intrinsic size. It adapts itself to the size that is set by its parent. force-horse is implementing CSS flex-box display logic.
The graph's data (nodes and links):
{
"nodes": [{
"id": "string",
"label": "string",
"svg": "string|optional"
}],
"links": [{
"sourceId": "string",
"targetId": "string"
}]
}
Configure options in the component. Defaults to:
{
"showButtons": true,
"showLabels": true,
"numOfLabelsToShow": 10,
"showNodeWeight": true,
"showEdgeWeight": true,
"hideOrphanNodes": false,
"showFilterButton": true,
"showLabelsButton": true,
"showNodeWeightButton": true,
"showEdgeWeightButton": true,
"showOrphanNodesButton": true,
"forceParameters": {
"friction": 0.5,
"charge": -100,
"linkStrength": 1,
"gravity": 0.3,
"linkDistance": 10
}
}
You can use the API by querying the force-horse
element, and accessing viewer
.
// In JS
const viewer = document.qeurySelector("force-horse").viewer;
// In Angular
// Template: `<force-horse #fh></force-horse>`
@ViewChild('fh') forceHorse: ElementRef;
ngAfterViewInit() {
const viewer = this.forceHorse.viewer;
}
Outputs are event emitters. You can subscribe and unsubscribe in the following way:
const subscription = viewer.hoverEvent.subscribe(() => { /* some callback */);
subscription.unsubscribe();
These are the current events. PR's and suggestions for more are welcome:
ready (readyEvent
): an SVG is drawn and ready
hover (hoverEvent
): a node/link is hovered upon
select (selectEvent
): a node/link is selected (selectedItems: Array, isMultiple: boolean, currentSelected, currentData
)
dblclick (doubleClickEvent
): a node/link is double-clicked upon
filter (filterEvent
): remove the selected nodes/links from the graph
The forceHorse project contains a complete demo application. You can see it in action here
On activation, force-horse shows the given graph. The graph stabilizes after a short force simulation. Then, if needed, it zooms out, so that the whole graph can be seen at a glance.
Beside showing the graph itself, force-horse provides visual indication of hovering over a node/link, and of selecting a node/link. It supports node dragging, and also pan and zoom.
In addition, force-horse is providing the following buttons:
- filter: remove selected nodes/links from the graph
- pause/play: allows to “freeze” the graph, to locate nodes without subsequent changes by the force-layout simulation
- home: automatically pan/zoom so that the whole graph can be seen at a glance
- labels: show/hide node labels
- node weight: show/hide node weight (weightier nodes will be larger)
- link weight: show/hide link weight (weightier links will be thicker)
The only dependency of force-horse is:
- d3.js v4
force-horse was designed for high performance. Some of the measures in use are:
- minimal use of DOM manipulations
- large graphs are not rendered continuously, but only a few times during the force simulation. The screen rendering is controlled programmatically, implementing javascriptrequestAnimationFrame(). A thin progress bar is displayed, during a force simulation, so that even if rendering is held, the user can know the stage and the pace of the current force simulation.
The ability to compute multiple, parallel link between two nodes is not currently supported intrinsically by d3.js. It was also not yet developed by the users community. Therefore, we developed this ability especially for force-horse. For the mathematical and implementation details, see here.
Set localStorage.setItem('force-horse', true)
to get informative console messages from force-horse.
To turn it off, remove that item by doing localStorage.removeItem('force-horse')