Forrest O.

Would be good to find a method that can run separately from node autolayout, so edges can always be routed in a smart way. [Orthogonal Connector Routing](http://ww2.cs.mu.oz.au/~pjs/papers/gd09.pdf) from Monash looks...

noflo-ui does use the-graph-thumb: https://github.com/noflo/noflo-ui/blob/1ddb399017ecb2da99c4033f9ecfc1e4deedc9b5/elements/noflo-main.html#L199

the-graph-editor / the-graph was supposed to be like the-graph-nav / the-graph-thumb, with navigation separated from rendering. Good idea to make those separate (React) components.

Reason for including noflo originally was to listen to changes from elsewhere (p2p) -- https://github.com/flowhub/the-graph/blob/c3b6a15eb41d079c625e07359d212c9ebb84f0f4/the-graph/the-graph-graph.js#L102-L116

connecting edges doesn't work now process is left behind as graph scrolls if pointer isn't moving

Moved these changes to https://github.com/the-grid/the-graph/commits/pointergestures Rolled back changes on master, since connecting is broken.

I think this is getting overwritten in [the-graph-editor.buildInitialLibrary()](https://github.com/the-grid/the-graph/blob/8b1552bc0028be03adc99367f38498603cf2e434/the-graph-editor/the-graph-editor.html#L213): ``` nofloGraph.nodes.forEach(function (node) { var component = { name: node.component, icon: 'cog', description: '', inports: [], outports: [] }; ... ``` Should...

Works correctly with mouse.

@bergie should we parseInt for certain metadata in fbp? And/or be safe here?

@davidmaxwaterman could do the `paresInt()` thing within findMinMax, but maybe it wouldn't hurt to do a cleanup pass before https://github.com/the-grid/the-graph/blob/9c5e6d6715de8a8de897a82f62228fcce286e4b8/the-graph-editor/the-graph-editor.html#L269