Updated markdwon files

Author: BasicPrimitives

apireference/readme.md

@@ -5,7 +5,7 @@
 #### [PDFKit Plugins](pdfkitplugins.md)
 * [primitives.pdf.orgdiagram.Plugin](pdfkitplugins.md#primitives.pdf.orgdiagram.Plugin)
 * [primitives.pdf.famdiagram.Plugin](pdfkitplugins.md#primitives.pdf.famdiagram.Plugin)
-#### [Organizational Chart Configuration Objects](orgdiagram.md)
+#### [Organizational Chart Configuration](orgdiagram.md)
 * [Config](orgdiagram.md#primitives.orgdiagram.Config)
 * [ItemConfig](orgdiagram.md#primitives.orgdiagram.ItemConfig)
 * [TemplateConfig](orgdiagram.md#primitives.orgdiagram.TemplateConfig)
@@ -15,7 +15,7 @@
 * [HighlightPathAnnotationConfig](orgdiagram.md#primitives.orgdiagram.HighlightPathAnnotationConfig)
 * [ButtonConfig](orgdiagram.md#primitives.orgdiagram.ButtonConfig)
 * [EventArgs](orgdiagram.md#primitives.orgdiagram.EventArgs)
-#### [Family Diagram Configuration Objects](famdiagram.md)
+#### [Family Diagram Configuration](famdiagram.md)
 * [Config](famdiagram.md#primitives.famdiagram.Config)
 * [ItemConfig](famdiagram.md#primitives.famdiagram.ItemConfig)
 * [TemplateConfig](famdiagram.md#primitives.famdiagram.TemplateConfig)

samples/AddingNewItemsToChartAtRuntime.md

@@ -8,7 +8,7 @@ Please, pay attention to the fact that the chart does not self update it's visua
 
 The `update` method supports multiple optional parameters which allow you to choose how you want to rerender your diagram.
 
-## In [JavaScript](https://developer.mozilla.org/en-US/docs/Web/javascript): 
+## In [JavaScript](https://developer.mozilla.org/en-US/docs/Web/javascript) 
 ```Javascript
 control.update(primitives.orgdiagram.UpdateMode.Recreate);
 ```
@@ -25,7 +25,7 @@ control.update(primitives.orgdiagram.UpdateMode.PositonHighlight);
 ```
 It ignores any API changes except current highlight item position, it just positions highlight item, no layout recalculation or items rendering performed.
 
-## In [jQuery](https://jqueryui.com/):
+## In [jQuery](https://jqueryui.com/)
 ```Javascript
 jQuery("#basicdiagram").orgDiagram(`update`, primitives.orgdiagram.UpdateMode.Recreate); /* Recreate */
 jQuery("#placeholder").orgDiagram(`update`, primitives.orgdiagram.UpdateMode.Refresh); /* Refresh */

samples/FirstOrganizationalChart.md

@@ -16,8 +16,11 @@ The following is the minimal set of files needed to use Basic Primitives compone
 The controls are state-full that means they keep internal state of the diagrams in order to minimize updates of visuals and avoid unnecessarily layout calculations. Library has two methods to construct instances of controls: use primitives.orgdiagram.Control for Organizational Diagrams and primitives.famdiagram.Control for Family Diagrams creation. The following code snippet creates organization chart inside empty div having "basicdiagram" id:
 
 ```Javascript
-var control = primitives.orgdiagram.Control(document.getElementById("basicdiagram"), {
-  /* regular JSON object or instance of primitives.orgdiagram.Config class*/
+var control = primitives.orgdiagram.Control(
+  document.getElementById("basicdiagram"), {
+  /* regular JSON object or instance of 
+    primitives.orgdiagram.Config class
+  */
 });
 ```
 
@@ -80,7 +83,7 @@ Historically Basic Primitives provides jQuery UI Widgets wrapping core controls,
 Basic Primitives jQuery UI widgets are added as methods on jQuery object, so for example in order to create a new organization chart inside empty div having "basicdiagram" id, we have to call following jQuery method:
 
 ```Javascript
-jQuery("#basicdiagram").orgDiagram({/* here is we define items & configuration options for our chart*/});
+jQuery("#basicdiagram").orgDiagram({/* new primitives.orgdiagram.Config() */});
 ```
 In order to get configuration object of existing widget call its method with argument "option"
 
@@ -110,9 +113,27 @@ In order to define the same chart as JSON object, replace it with the following
 ```Javascript
 jQuery("#basicdiagram").orgDiagram({
   items: [
-    { id: 0, parent: null, title: "Scott Aasrud", description: "VP, Public Sector", image: "demo/images/photos/a.png" },
-    { id: 1, parent: 0, title: "Ted Lucas", description: "VP, Human Resources", image: "demo/images/photos/b.png" },
-    { id: 2, parent: 0, title: "Joao Stuger", description: "Business Solutions, US", image: "demo/images/photos/c.png"}
+    { 
+      id: 0,
+      parent: null,
+      title: "Scott Aasrud",
+      description: "VP, Public Sector",
+      image: "demo/images/photos/a.png" 
+    },
+    { 
+      id: 1, 
+      parent: 0, 
+      title: "Ted Lucas", 
+      description: "VP, Human Resources", 
+      image: "demo/images/photos/b.png" 
+    },
+    { 
+      id: 2, 
+      parent: 0, 
+      title: "Joao Stuger", 
+      description: "Business Solutions, US", 
+      image: "demo/images/photos/c.png"
+    }
   ],
   cursorItem: 0,
   hasSelectorCheckbox: primitives.common.Enabled.True
@@ -200,7 +221,9 @@ var sampleSize = samfirstOrganizationalChartSampleple3.getSize();
 `getSize` method returns diagram size, so we can create new PDF document big enough to accomodate our diagram:
 
 ```JavaScript
-var doc = new PDFDocument({ size: [sampleSize.width + 100, sampleSize.height + 150] });
+var doc = new PDFDocument({ 
+  size: [sampleSize.width + 100, sampleSize.height + 150] 
+});
 ```
 
 Plugin draws diagram in current PDFkit document layout transformation context, so developer can rotate, translate and scale diagrams on PDFkit document page.

src.primitives/Controls/OrgDiagram/Configs/Config.js

@@ -161,9 +161,9 @@ primitives.orgdiagram.Config = function (name) {
   this.items = [];
 
   /**
-   * Annotations. Annotations are API elements that are attached to the diagram nodes.
-   * We draw our annotations either in front of the nodes or in the background. The annotations 
-   * don't affect the nodes placement in any way. As a result the control redraws them 
+   * Annotations. Annotations are API elements that are attached to the diagram nodes positions.
+   * We draw annotations either in front of the diagram nodes or in their background. Annotations 
+   * don't affect nodes placement in any way. As a result the control redraws them 
    * instantaneously without rerendering or recalculating the actual diagram layout.
    * 
    * @type {Array.<(ShapeAnnotationConfig | BackgroundAnnotationConfig | ConnectorAnnotationConfig | HighlightPathAnnotationConfig)>}