Skip to content

Latest commit

 

History

History
163 lines (127 loc) · 4.69 KB

upgrade_guide.md

File metadata and controls

163 lines (127 loc) · 4.69 KB
Raw

Migrating from 0.6.x to 0.7.x

Main reason for breaking changes is shift from monolithic architecture to modular design. Now VivaGraph consists of small modules from ngraph family. ngraph modules are usually very well documented and tested.

Layout API changes

Viva.graph.Layout.forceDirected is replaced with ngraph.forcelayout. This module is faster than older one, and has better test coverage.

layout.getLinkPosition()

v.0.6.*

var linkPosition = layout.getLinkPosition(link);

v.0.7.*

var linkPosition = layout.getLinkPosition(link.id);

layout.setNodePosition()

v.0.6.*

layout.setNodePosition(node, x, y);

v.0.7.*

layout.setNodePosition(node.id, x, y);

layout settings

Force based layout settings can be now accessed from layout.simulator:

  • layout.drag() is now known as simulator.dragCoeff()
  • layout.springCoeff() -> simulator.springCoeff()
  • layout.springLength() -> simulator.springLength()
  • layout.gravity() -> simulator.gravity()
  • layout.theta() -> simulator.theta()

Generator changes

The module is replaced with ngraph.generators which contains all original graphs + new graphs.

v.0.6.*

Viva.Graph.generator().randomNoLinks(42);

v.0.7.*

Viva.Graph.generator().noLinks(42);

Deprecated API

Migrating from 0.5.x to 0.6.x

Version 0.5.x and 0.6.x are almost identical and do not have any breaking API changes. Primary reason for version bump was that 0.6 had changed build system from grunt to gulp. Also v.0.6 had lots of small changes with fixed typos/documentation.

Migrating from 0.4.x to 0.5.x

Main reason for breaking changes below is that v.0.4 does not allow to render the same graph by multiple renderers. Please feel free to email me and ask for help, if you find this migration guide not sufficient.

node.position

position attribute is moved out from the node object into layout provider.

Why? Having shared node position makes impossible rendering of the same graph by two different layouters.

v.0.4.*

    // each node object has "position" on it:
    graph.forEachNode(function (node) {
      var position = node.position;
      position.x += 1; // move by one pixel
    });

v.0.5.*

    // "position" is now part of layouter:
    graph.forEachNode(function (node) {
      // layout here is instance of Viva.Graph.Layout.forceDirected or Viva.Graph.Layout.constant:
      var position = layout.getNodePosition(node.id);
      position.x += 1;
    });

To give initial positions to nodes in v.0.5.* simply call: layout.setNodePosition(node, x, y).

node.ui

ui attribute is moved out from the node/link objects into graphics provider.

Why? having shared ui attribute makes impossible rendering of the same graph by multiple renderers.

v.0.4.*

    // each node object has "position" on it:
    graph.forEachNode(function (node) {
      console.log(node.ui);
    });

    // each link object has "position" on it:
    graph.forEachLink(function (link) {
      console.log(link.ui);
    });

v.0.5.*

    //  "ui" is now part of graphics:
    graph.forEachNode(function (node) {
      // graphics here can be instance of Viva.Graph.View.svgGraphics or Viva.Graph.View.webglGraphics:
      console.dir(graphics.getNodeUI(node.id));
    });
    //  "ui" is now part of graphics:
    graph.forEachLink(function (link) {
      // graphics here can be instance of Viva.Graph.View.svgGraphics or Viva.Graph.View.webglGraphics:
      console.dir(graphics.getLinkUI(link.id));
    });

node.isPinned

node.isPinned is no longer used to determine whether node is pinned or not. This responsibility is moved to layouter.

Why? Same reasons as above. Disabling node movement in one renderer should not affect movement of the same node in other renderers.

v.0.4.*

// toggle node pinning:
node.data.isPinned = !node.data.isPinned;

v.0.5.*

// toggle node pinning:
var wasPinned = layout.isNodePinned(node);
layout.pinNode(node, !wasPinned);
// layout here is instance of Viva.Graph.Layout.forceDirected or Viva.Graph.Layout.constant.