basicprimitives - npm Package Compare versions

Comparing version 5.6.4 to 5.7.0

package.json

		{
		"name": "basicprimitives",
		"version": "5.6.4",
		"version": "5.7.0",
		"description": "Basic Primitives Diagrams for JavaScript - data visualization components library that implements organizational chart and multi-parent dependency diagrams, contains implementations of JavaScript Controls and PDF rendering plugins.",
		@@ -5,0 +5,0 @@ "main": "primitives.latest.js",

readme.md

		@@ -53,2 +53,7 @@ # [Basic Primitives](https://www.basicprimitives.com) Diagrams for JavaScript

		#### Stable rules based auto layout of multi parent hierarchies
		The core problem of dependency diagrams layout is the endless number of permutations. As a result every time we make any changes to the diagram's relations, we get a new "optimal" layout. However that "optimal" layout can be so different from the previous "optimal" layout that the end user needs to relearn the diagram again and again. This becomes worse the more nodes you have. Analysis takes so much time, that it makes the automatic diagram layout useless. So it is very important that diagram does not change much between user edits.
		So in order to overcome that problem we added support of user rules that the auto layout algorithm follows. The problem is that "hard" rules are equivalent to manual layout if we start to define the placement of every node manually. Which destroys the whole point of even having auto layout for the nodes. So we introduced "soft" rules, which our control follows as long as they don't contradict to the purpose. Our control does ignore them when they are not applicable.
		* Moderate layout changes between edits. Multi parent hierarchy diagram does not change much when we add or remove nodes. Developer is encouraged to add order of nodes relative to each other, but that order does not enforce layout, control still has flexibility to choose optimal layout itself.

		#### Auto sorting the diagram nodes into levels
		@@ -55,0 +60,0 @@ It is not obvious, but by default we distribute all nodes in the diagram into distinct levels. This gives the end user a clear indication about a node's relations. For any given node, all nodes that are below it in the diagram, are either it's dependents or minors. On the contrary any nodes found above the node are either its parents or superiors. This is a simple and straightforward visual sorting method that helps when analyzing and viewing large diagrams.

primitives.latest.js

Sorry, the diff of this file is too big to display

basicprimitives - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics