* Network: use separate refresh indicator in NodeBase, instead of width parameter

* Added usage of iBaseNode.doRefresh to image shapes.

* Rearranged code in NodeBase.needRefresh()

* Fixes for review

* Removed strange link

* Added 's' in needsRefresh(); typo fix

* Fixes for review, code cleanup

* Modified ratio calc to original working.

* Made code in CircularImage.resize() more sensible.

* Reduce the time-complexity of the network initial positioning. Very substantial performance gain for large graphs.

* Remove unwanted console messages, extended comment.

* Improve the performance of the network layout engine

Short-cut the execution of a number of methods in LayoutEngine to make them
handle highly-connected graphs better.

* Demonstrations of layouts of large networks

* maximum width constraints must be violated by long words. Fixes #2604.

* chore: moved examples/network/_tests/maximumWidthEdgeCase.html to test/network/

fixes #2640

Using the 'directed' sort method, the layout engine seemed to ignore treeSpacing (or only apply it to the first tree). This would also lead to trees colliding with one another, and having their nodes tangled in space. This complaint surfaced in a couple bugs, including #2494. This should be a step toward fixing that. For whatever reason, this code never runs when using the "hubsize" sort method.

* self reference edge should now appear in all cases
* add checks for shape width being NaN to get correct circle data
* reorder resize arguments in Diamond, Dot and Star

* fix #2613 with if statement, and null for pointer value rather than referencing it when undefined

* removed if statement, since not needed, and updated documentation to note the null pointer property in certain conditions.

* Added HTML tooltip support for Timeline

* Fixed tooltip position on Firefox

* Added Timeline tooltip example

* Updated tooltip location to be next to the mouse

* Added HTML element to example

* element characteristic changes
* assume edge color inheritance is correct before choosing
* Adjust nodes’ chosen’s boolean -> bool
* Need to get user-reset size
* make example edges thicker for more noticeable shadow
* preemptive ES6 fix (see #2500/#2501)
* documentation for the feature that was previously overwritten

* Multifont node and edge labels
* adjust documentation
* rework mod-font property inheritance
* Node max/min widths, min heights; Edge max widths
* Accumulate sizes correctly for unconstrained multipoint labels
* handle font.multi when groupOptions.font is not declared
* propagate label fonts on changes, not just creation
* Allow top-level constraint numbers
* accumulate width and empty lines appropriately

* add pointer position to zoom event
* Update docs with zoom api

* { manipulation: { editEdge: { editWithoutDrag: function } } } edits an edge without dragging.
* An example of editing network edges without dragging, enabling label creation / change

* Should fix issue #2100 and fix another issue we discovered around clusterByConnection leaving phantom edges.
* fixed a wrong variable name
* fixed DataView.test.js assert
* Update Canvas.js
* remove whitespace; remove end of file newline on Canvas.js
* strip end of file newlines
* fixed styling. spacing, semicolons, line length

Thanks @federicoco for providing the translation!

* Removed restriction to allow clusters of a single node; Default functionality remains the same;  Also added new example
* Add documentation for allowSingleNodeCluster, and removed excessive cluster() calls in example.
* Changed documentation as per request.

* Added getBaseEdge, getClusteredEdges updateEdge and updateClusteredNode to allow option changes of the clustered edges as they are no longer the original base Edge

changing edge color is a good example.
i.e network.clustering.updateEdge(originalEdge.id, {color : '#aa0000'});
will now update all edges including the ones that were created when clustering.

Also when clicking on a clustered edge the event returns the clustered Edge id, which doesn't mean a lot.
This can be now converted back into the original edge with
network.clustering.getBaseEdge(clusteredEdge.id)

Similar with updateClusteredNode
This new method allows the options to be changed on a clustered Node.

i.e clicking on a clustered node gives its clustered node id.
Want to change the clustered image to a star then do this
 network.clustering.updateClusteredNode(clusteredNodeId, {shape : 'star'});

* Updated docs with getClusteredEdge, getBaseEdge, updateEdge and updateClusteredNode

Also added method subsections into contents

* Added better error handling to updateEdge and updateClusteredNodes

corrected errors spotted by @mojoaxel

* Added example html demonstrating getBaseEdge, getClusteredEdges updateEdge and updateClusteredNode

* Added getBaseEdge, getClusteredEdges updateEdge and updateClusteredNode to allow option changes of the clustered edges as they are no longer the original base Edge

changing edge color is a good example.
i.e network.clustering.updateEdge(originalEdge.id, {color : '#aa0000'});
will now update all edges including the ones that were created when clustering.

Also when clicking on a clustered edge the event returns the clustered Edge id, which doesn't mean a lot.
This can be now converted back into the original edge with
network.clustering.getBaseEdge(clusteredEdge.id)

Similar with updateClusteredNode
This new method allows the options to be changed on a clustered Node.

i.e clicking on a clustered node gives its clustered node id.
Want to change the clustered image to a star then do this
 network.clustering.updateClusteredNode(clusteredNodeId, {shape : 'star'});

* Updated docs with getClusteredEdge, getBaseEdge, updateEdge and updateClusteredNode

Also added method subsections into contents

* Added better error handling to updateEdge and updateClusteredNodes

corrected errors spotted by @mojoaxel

* Added example html demonstrating getBaseEdge, getClusteredEdges updateEdge and updateClusteredNode

Perturbing the nodes was being performed on all nodes regardless of whether they were set as fixed.

Signed-off-by: André Martins <aanm90@gmail.com>

As the documentation on vis.js nodes can be styled with align: left|center

allOptions does not include this option and throw an error on option validation.