GoJS is a JavaScript library that lets you easily create interactive diagrams in web browsers. GoJS supports graphical templates and data-binding of graphical object properties to model data. You only need to save and restore the model, consisting of simple JavaScript objects holding whatever properties your app needs. Many predefined tools and commands implement the standard behaviors that most diagrams need. Customization of appearance and behavior is mostly a matter of setting properties.
The following code defines a node template and model data, which produces a small diagram with a handful of nodes and links.
// the node template describes how each Node should be constructed
diagram.nodeTemplate =
new go.Node("Auto")
.add( // the Shape will go around the TextBlock
new go.Shape("RoundedRectangle")
// Shape.fill is bound to Node.data.color
.bind("fill", "color"),
new go.TextBlock({ margin: 8}) // Specify a margin to add some room around the text
// TextBlock.text is bound to Node.data.key
.bind("text")
);
// the Model holds only the essential information describing the diagram
diagram.model = new go.GraphLinksModel(
[ // a JavaScript Array of JavaScript objects, one per node;
// the "color" property is added specifically for this app
{ key: 1, text: "Alpha", color: "lightblue" },
{ key: 2, text: "Beta", color: "orange" },
{ key: 3, text: "Gamma", color: "lightgreen" },
{ key: 4, text: "Delta", color: "pink" }
],
[ // a JavaScript Array of JavaScript objects, one per link
{ from: 1, to: 2 },
{ from: 1, to: 3 },
{ from: 2, to: 2 },
{ from: 3, to: 4 },
{ from: 4, to: 1 }
]);
// enable Ctrl-Z to undo and Ctrl-Y to redo
diagram.undoManager.isEnabled = true;
You can interact with this diagram in many ways:
You can also pan, pinch zoom, select, copy, move, delete, undo, and redo with your fingers on a touch device. Most commands that can be invoked from a keyboard can be invoked from the default context menu that you get by pressing your finger and holding it motionless for a moment.
What is unique about all of the examples in the documentation is that they are all "live" -- there are no screenshots! They are actual Diagrams implemented by the source code shown. You can interact with them -- some even display animation.
If you'd like to see more examples of what GoJS can do, see the GoJS Samples directory. To make it easier to search the JavaScript code and documentation or to experiment by modifying the samples, you can install the GoJS kit in various manners:
npm install gojs and npm create gojs-kit.Diagrams consist of Parts: Nodes that may be connected by Links and that may be grouped together into Groups. All of these parts are gathered together in Layers and are arranged by Layouts and Routers.
Each diagram has a Model that holds and interprets your application data to determine node-to-node link relationships and group-member relationships. Most parts are data-bound to your application data. The diagram automatically creates a Node or a Group for each data item in the model's Model.nodeDataArray and a Link for each data item in the model's GraphLinksModel.linkDataArray. You can add whatever properties you need to each data object, but there are just a few properties that each kind of model expects. They are shown in bold in the gray data objects.
Each Node or Link is normally defined by a template that declares its appearance and behavior. Each template consists of Panels of GraphObjects such as TextBlocks or Shapes. There are default templates for all parts, but almost all applications will specify custom templates in order to achieve the desired appearance and behavior. Data bindings of GraphObject properties to model data properties make each Node or Link unique for the data.
The nodes may be positioned manually (interactively or programmatically) or may be arranged automatically by the Diagram.layout and by each Group.layout. Nodes are positioned either by their top-left corner point (GraphObject.position) or by a programmer-defined spot in the node (Part.location and Part.locationSpot).
Tools handle mouse and keyboard and touch or stylus events. Each diagram has a number of tools that perform interactive tasks such as selecting parts or dragging them or drawing a new link between two nodes. The ToolManager determines which tool should be running, depending on the mouse events and current circumstances.
Each diagram also has a CommandHandler that implements various commands, such as Delete or Copy. The CommandHandler interprets keyboard events, such as Ctrl-Z, when the ToolManager is running.
The diagram provides the ability to scroll the parts of the diagram and to zoom in or out. The diagram also contains all of the layers, which in turn contain all of the parts (nodes and links). The parts in turn are composed of possibly nested panels of text, shapes, and images. This hierarchy of JavaScript objects in memory forms the "visual tree" of everything that may be drawn by the diagram.
Animations are implemented and controlled by the AnimationManager. Automatic animations happen after automatic layouts and upon the execution of various commands. You an define your own custom Animations.
The Overview class allows the user to see the whole model and to control what part of it that the diagram displays. The Palette class holds parts that the user may drag-and-drop into a diagram.
You can select one or more parts in the diagram. The template implementation may change the appearance of the node or link when it is selected. The diagram may also add Adornments to indicate selection and to support tools such as resizing a node or reconnecting a link. Adornments are also how tooltips and context menus are implemented.
All programmatic changes to Diagram, GraphObject, Model or model data state should be performed within a single transaction per user action, to make sure updating happens correctly and to support undo/redo. All of the predefined tools and commands perform transactions, so each user action is automatically undoable if the UndoManager is enabled. DiagramEvents on Diagrams, and event handlers on Diagrams and GraphObjects, are all documented whether they are raised within a transaction or whether you need to conduct a transaction in order to change the model or the diagram.
Before you can execute any JavaScript code to build a Diagram, you will need to load the GoJS library.
When you include the library, the "go" JavaScript object will hold all of the GoJS types.
During development we recommend that you load "go-debug.js" instead of "go.js", for additional run-time error checking
and debugging ability.
We recommend that you declare that your web page supports modern HTML:
<!DOCTYPE html> <!-- Declare standards mode. -->
<html>
<head>
. . .
<!-- Include the GoJS library. -->
<script src="go-debug.js"></script>If depending on your npm environment:
import * as go from "gojs";
If you want to use ECMAScript modules, use go-module.js in the release/ directory.
The extension classes are implemented in TypeScript and compiled as ECMAScript modules in the extensionsJSM/ directory.
The extension classes are compiled into regular script-loadable JavaScript in the extensions/ directory.
Please copy the extension file into your project so that you can adjust the import statement to
get the same GoJS library that the rest of your code imports.
import * as go from "./path/to/gojs/release/go-module.js";
import { DoubleTreeLayout } from "./path/to/gojs/extensionsJSM/DoubleTreeLayout.js";
If you are using RequireJS,
the GoJS library supports UMD module definitions.
Copy each extension file into your project, and update its require statement
so that all of your code loads the same GoJS library and only does so once.
Every Diagram must be hosted by an HTML Div element. GoJS will manage the contents of that Div element, but you may position and size and style the Div as you would any HTML element. The diagram will add a Canvas element to that Div element that the diagram will draw in -- this is what users actually see. The Canvas element is automatically sized to have the same size as the Div element.
<body>
. . .
<!-- The DIV for a Diagram needs an explicit size or else we won't see anything.
In this case we also add a border to help see the edges. -->
<div id="myDiagramDiv" style="border: solid 1px blue; width:400px; height:150px"></div>
Then you can create the Diagram in JavaScript with a reference to that Div element.
Build the diagram by constructing plain JavaScript objects and adding them to the diagram's model.
Note that all references in JavaScript code to GoJS types such as Diagram are prefixed with
"go.".
<!-- Create the Diagram in the DIV element using JavaScript. -->
<!-- The "go" object is the "namespace" that holds all of the GoJS types. -->
<script>
const diagram = new go.Diagram("myDiagramDiv");
diagram.model = new go.GraphLinksModel(
[{ key: 1, text: "Hello" }, // two node data, in an Array
{ key: 2, text: "World!" }],
[{ from: 1, to: 2 }] // one link data, in an Array
);
</script>This completes the implementation of the "Hello World!" live diagram that you see above.
GoJS outputs error or warning messages when something goes wrong. When developing with GoJS, be sure to check your browser's developer console for information. The "go-debug.js" version of the library contains extra type-checking and error-checking code, and should be used during development. The "go.js" version has less error checking, but is faster as a result, and should be used in production.
Your JavaScript code should only use properties and methods that are documented in the API. The GoJS libraries are "minified", so if you look at an instance of a GoJS class in the debugger, you will see many one or two letter property names. All of those are internal names that you should not use. At the current time the only one letter property names are "x" and "y" on Point, Rect, Spot and LayoutVertex. The only two letter property name is InputEvent.up. Otherwise you should not try to use any one or two letter property names on any GoJS-defined objects.
Do not modify the prototypes of the GoJS classes.
Only use the properties and methods documented in the API.
You can also use TypeScript in order to get better "edit-time" and
"compile-time" type checking and "edit-time" documentation.
The TypeScript definition files for GoJS are named "go.d.ts" and "go-module.d.ts" and are located in the same directory as the libraries.
The extension classes are implemented in TypeScript, available at ../extensionsJSM/
and compiled to JavaScript in ../extensionsJSM/ and ../extensions/.
Copy the extension definitions into your project and make sure they import the same GoJS library as all of your code does.
To learn about new features and bug fixes, read the Change Log. Read about getting the latest releases at Downloads.
You can see the variety of kinds of diagrams that you can build at GoJS Samples.
In the next introduction page we discuss building GoJS Parts and adding them into Diagrams.