Eclipse Community Forums: Eclipse Layout Kernel » what MrTree layout algorithm ID

Home » Modeling » Eclipse Layout Kernel » what MrTree layout algorithm ID

what MrTree layout algorithm ID [message #1750380]

Tue, 20 December 2016 09:29

Eclipse User

I am able to use Layered algo , but I am not able to find the MrTree Algorithm ID.

configurator.configure(KNode.class)
.setProperty(CoreOptions.ALGORITHM, "org.eclipse.elk.layered"/*LayeredOptions.ALGORITHM_ID*/)
.setProperty(LayeredOptions.CROSSING_MINIMIZATION_STRATEGY, CrossingMinimizationStrategy.LAYER_SWEEP)
.setProperty(CoreOptions.INTERACTIVE, true)
.setProperty(LayeredOptions.SPACING_NODE, 20.0f)
.setProperty(LayeredOptions.EDGE_ROUTING, EdgeRouting.ORTHOGONAL)
.setProperty(CoreOptions.SPACING_BORDER, 2f)
.setProperty(LayeredOptions.DIRECTION, Direction.DOWN);

Re: what MrTree layout algorithm ID [message #1750419 is a reply to message #1750380]

Tue, 20 December 2016 16:08

Eclipse User

Hi Abhishek,

yes, sorry about that - we are currently working on generating all necessary documentation for the different layout algorithms. For now, simply use the following ID:

org.eclipse.elk.force

With the next release (or the current nightlies), using the following constant is safer and preferred:

org.eclipse.elk.alg.force.properties.ForceOptions.ALGORITHM_ID

Re: what MrTree layout algorithm ID [message #1750473 is a reply to message #1750380]

Wed, 21 December 2016 08:35

Eclipse User

Since you were asking for tree, not force: org.eclipse.elk.mrtree.mrTree.

There's a part in the generator code that omits the last part of the id if it's duplicated (e.g. ...force.force). However, it seems to be case sensitive, which is why the mrTree's id is different. I guess we should change the algorithm id to 'mrtree'. cds?

Re: what MrTree layout algorithm ID [message #1751108 is a reply to message #1750473]

Wed, 04 January 2017 09:21

Eclipse User

Ulf Rueegg wrote on Wed, 21 December 2016 13:35

Since you were asking for tree, not force: org.eclipse.elk.mrtree.mrTree.

Oops...

Ulf Rueegg wrote on Wed, 21 December 2016 13:35

There's a part in the generator code that omits the last part of the id if it's duplicated (e.g. ...force.force). However, it seems to be case sensitive, which is why the mrTree's id is different. I guess we should change the algorithm id to 'mrtree'. cds?

Done. See this issue.

Previous Topic:	Border node "inside" its container
Next Topic:	KIELER Siguyama layout algorithm equivalence in ELK

Goto Forum:

-=] Back to Top [=-

Current Time: Sun May 18 20:08:50 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter