|Published (Last):||13 September 2015|
|PDF File Size:||12.95 Mb|
|ePub File Size:||12.10 Mb|
|Price:||Free* [*Free Regsitration Required]|
Anchor – a location, relative to an element’s origin, at which an Endpoint can exist. You do not create these yourself; you supply hints to the various jsPlumb functions, which create them as needed.
They have no visual representation; they are a logical position only. Anchors can be referenced by name, for the Anchors that jsPlumb ships with, or with an array containing various parameters, for greater control.
Getting started with jsPlumb
See the Anchors page for more detail. Endpoint – the visual representation of one end of a Connection. You can create and attach these to elements yourself, which you are required to do to support drag and drop, or have jsPlumb create them when creating a Connection programmatically using jsPlumb.
You can also join two Endpoints programmatically, by passing them as arguments to jsPlumb. See the Endpoints page for more detail. Connector – the visual representation of the line connecting two elements in the page.
jsPlumb Toolkit – build Flowcharts, Diagrams and connectivity based applications fast
You do not interact with Connectors; you just specify definitions of them when you need to. See the Connectors page for more detail.
Group – a group of elements contained within some other element, which can be collapsed, causing connections to all of the Group members to be pooled on the collapsed Group container. For more information, see the Groups page.
One Connection is made up of two Endpoints, a Connector, and zero or more Overlays working together to join two elements. Each Endpoint has an associated Anchor. But you still need to be across the concepts encapsulated by Anchor, Connector and Overlay. Whenever you need to define a Connector, Endpoint, Anchor or Overlay, you must use a “definition” of it, rather than constructing one directly.
This definition can be either a string that nominates the artifact you want to create – see the endpoint parameter here:. There is also a three-argument method jsplumg allows you to specify two sets of parameters, which jsPlumb will merge tutoeial for you.
The idea behind jsolumb is that you will often want to define common characteristics somewhere and reuse them across a bunch of different calls:.
This syntax is supported for all Endpoint, Connector, Anchor and Overlay definitions. Here’s an example using definitions for all four:.
The allowed constructor parameters are different for each artifact you create, but every artifact takes a single JS object as argument, with the parameters as key,value pairs in that object. Building jsPlumb Documentation while developing.
This definition can be either a string that nominates the artifact you want to create – see the endpoint parameter here: