CyrilFerlicot
CyrilFerlicot
See for example demo CompositeExploringHierarchy
- [x] Style (CSS) - [ ] Text area to create our own visualization on web - [x] See the code of the visualization - [ ] If a demo...
I think it would be good to have some "groups". For example ``` Connection style -------------------- --- Something .... Something else ___ Something new Border style -------------------- … ``` Also...
If a framework does not remove the children of a composite by himself it should be managed in the connector and not the model.
With this method if a node is a child of two nodes from different levels it will be on the right level.
This happen because of the defensive strategy on the #expended of the Composite node. While we build the legend, the nodes are already in place but we create a requirement...