-
Notifications
You must be signed in to change notification settings - Fork 61
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[doc] Add shape for border node initial position
Signed-off-by: Laurent Fasani <[email protected]>
- Loading branch information
Showing
2 changed files
with
45 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
44 changes: 44 additions & 0 deletions
44
doc/iterations/2025.2/add_support_for_border_node_initial_positioning.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
= Add Support For Border Node Initial Positioning | ||
|
||
== Problem | ||
|
||
In a diagram, a `Border Node` is always created on the left of the `Node`(WEST position). | ||
|
||
== Key Result | ||
|
||
As a specifier, I can define, in the `View` model the side of the `Node` where the `Border Node` will be created. | ||
|
||
As an end-user, I can see that the border node is created on the right side of the node accordingly to the view model. | ||
|
||
== Solution | ||
|
||
Currently, there is only the `NodeDescription` concept used for container, node and border node. | ||
A `NodeDescription` is considered as the description of a border node if it is contained by the feature `NodeDescription.borderNodeDescriptions` | ||
|
||
We need to define the information on which side of the parent node will the border node be created. | ||
The information will be hold by the parent layout strategy `NodeDescription.childrenLayoutStrategy` | ||
|
||
|
||
``` | ||
class LayoutStrategyDescription { | ||
onRightAtCreationBorderNodes: List<NodeDescription> | ||
onLeftAtCreationBorderNodes: List<NodeDescription> | ||
onTopAtCreationBorderNodes: List<NodeDescription> | ||
onBottomAtCreationBorderNodes: List<NodeDescription> | ||
} | ||
``` | ||
|
||
For those four features, we will make sure that the specifier is capable of selecting only the border nodes of the current NodeDescription. | ||
|
||
== Cutting Backs | ||
|
||
No | ||
|
||
== Rabbit Holes | ||
|
||
Not identified. | ||
With this proposal, we avoid putting the information on border node itself because it would lower the reusability of this border node. | ||
|
||
== No-Gos | ||
|
||
No |