Skip to content

Commit 08ca6ea

Browse files
Removed non-implimented options
1 parent 9ef4456 commit 08ca6ea

3 files changed

Lines changed: 1 addition & 49 deletions

File tree

changelog.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,4 @@
11
#### Version 6.4.0
2-
* Added `Director`, `SuperAdviser` and `SuperAssistant` item types.
3-
* Added `directorsPlacementType`, `advisersPlacementType` to `OrgItemConfig`
42
* Added `minimumVisibleLevels` option to `OrgConfig` and `FamConfig`
53
* Added `padding` option to `OrgConfig` and `FamConfig`
64
* Fixed `childrenPlacementType` option breaking multiple root nodes placement.

src/configs/OrgItemConfig.js

Lines changed: 0 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -169,31 +169,6 @@ export default function OrgItemConfig(arg0, arg1, arg2, arg3, arg4) {
169169
*/
170170
this.adviserPlacementType = AdviserPlacementType.Auto;
171171

172-
/**
173-
* The property defines the shape of directors formation.
174-
* By default, control places directors nodes in a horizontal line above parent node side.
175-
* On a large scale, this may result in a long stripe of nodes,
176-
* and the end-user has to scroll the screen to view all of them. To compensate for this,
177-
* we provide the option of placing them in a vertical or square/matrix formation.
178-
* That will reduce sideways screen scrolling by compacting the directors into
179-
* a much smaller area on the screen.
180-
*
181-
* @type {ChildrenPlacementType}
182-
*/
183-
this.directorsPlacementType = ChildrenPlacementType.Auto;
184-
185-
/**
186-
* The property defines the shape of child advisers' formation.
187-
* By default, control places adviser nodes in a horizontal line on the parent node side.
188-
* On a large scale, this may result in a long stripe of advisers chained to each other,
189-
* and the end-user has to scroll the screen to view all of them. To compensate for this,
190-
* we provide the option of placing them in a vertical or square/matrix formation.
191-
* That will reduce sideways screen scrolling by compacting the advisers into a much smaller area on the screen.
192-
*
193-
* @type {ChildrenPlacementType}
194-
*/
195-
this.advisersPlacementType = ChildrenPlacementType.Auto;
196-
197172
/**
198173
* The property defines children's layout formation. By default, control places children
199174
* in a horizontal line below the parent node. On a large scale, this may result in the end-user

src/enums.js

Lines changed: 1 addition & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -510,28 +510,7 @@ export const ItemType = {
510510
* The sub-adviser type places node on the right or left side of the parent.
511511
* The connection line goes out of the top side of the sub-adviser node.
512512
*/
513-
SubAdviser: 5,
514-
/**
515-
* The super adviser type places node at the column between parent and
516-
* adviser nodes above the connection line going from the parent to advisers.
517-
* The super adviser node is opposite to the sub-adviser, and
518-
* it rotates the entire hierarchy of its children in the upward direction.
519-
*/
520-
SuperAdviser: 11,
521-
/**
522-
* The director type places node above the logical parent. So it opposite position
523-
* to the regular nodes. The director node rotates the organizational chart layout
524-
* and the hierarchy of its child nodes upward. If there is no space to place the
525-
* director above the parent, control transforms it into a regular adviser node.
526-
*/
527-
Director: 9,
528-
/**
529-
* The super assistant type places node between parent and directors
530-
* on the left or right side of the connection line connecting the parent with directors.
531-
* The super assistant node is opposite to the assistant, and
532-
* it rotates the entire hierarchy of its children in the upward direction.
533-
*/
534-
SuperAssistant: 10,
513+
SubAdviser: 5,
535514
/**
536515
* The general partner type is an imitation of multiple inheritances in the organizational chart hierarchy.
537516
* The general-partner node is drawn side by side with its logical parent, and control places

0 commit comments

Comments
 (0)