Bug 482932 - Add support for a hierarchical layout based on strongly connected components.
Summary: Add support for a hierarchical layout based on strongly connected components.
Status: CLOSED DUPLICATE of bug 440098
Alias: None
Product: GEF
Classification: Tools
Component: GEF Layout (show other bugs)
Version: 0.2.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: gef-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 440098
Blocks:
  Show dependency tree
 
Reported: 2015-11-24 12:19 EST by Alexander Nyßen CLA
Modified: 2016-05-06 16:07 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Nyßen CLA 2015-11-24 12:19:08 EST 
As the GEF4 layout algorithms are not really capable of handling graphs with strongly connected components (see forum discussion: https://www.eclipse.org/forums/index.php/t/1072184/), it could make sense to add support for this in Zest.

Having computed strongly connected components up front, layouting could be performed for each component individually, as well as for the overall layout of the respective components. 

IMHO this could fit in nicely with the currently not very useful hiding mechanism in Zest (hiding currently does not lead to re-layout and also does not improve the visual appearance).
Comment 1 Alexander Nyßen CLA 2015-11-24 12:32:48 EST 
Having considered this in more depth, it could also be something we directly provide as part of GEF4 layout through some composite/hierarchical layout algorithm.
Comment 2 Alexander Nyßen CLA 2016-02-03 07:27:31 EST 
This is closely related to support for subgraphs/clusters (bug #469469), as subgraphs would probably have to be considered as "strongly connected". The question would be wether this functionality should rely within Zest (so it uses hierarchical layout contexts) or wether the layout interfaces would have to be extended. This should probably be investigated after having reviewed the ELK data model (bug #440098).
Comment 3 Alexander Nyßen CLA 2016-05-06 16:07:55 EDT 
As this functionality can directly be realized by using (invisible) clusters, Resolving this als s duplicate of bug #440098.

*** This bug has been marked as a duplicate of bug 440098 ***