Sure Ed,
KIELER [1] is a graph layout library which is developed at the
University of Kiel (Germany).
The library offers quite a lot of different layout algorithms and
many possibilities for customizations and extensions.
It also offers adapters for GMF and Graphiti based diagrams.
Actually it is not so much a library than a set of Eclipse
plug-ins. They are all published under the EPL.
Our eTrice project used KIELER in a Google Summer of Code project
last year.
To integrate that code I thought it would make sense to have the
KIELER plug-ins in Orbit.
But now David pointed out that this is probably not the
appropriate place and the KIELER project should rather consider
becoming an Eclipse Modeling project itself.
Please don't hesitate to ask further questions.
I'm sure Miro will be happy to answer them.
Kind regards,
Henrik
[1] http://www.informatik.uni-kiel.de/en/rtsys/kieler/
Am 12.02.2013 20:34, schrieb Ed Merks:
Guys,
I guess I need a little bit of background about this... Where can
I found out more?
Regards,
Ed
On 06/02/2013 9:13 PM, Henrik
Rentz-Reichert wrote:
William,
thank you for pointing this out. I haven't been aware of that.
I also CC'd Miro Spoenemann who is one of the developers and
the contact person for the KIELER library.
Kind regards,
Henrik
Am 06.02.2013 20:46, schrieb David
M Williams:
Henrik,
Sorry to be the bearer of bad
news, but ...
Seeing the Orbit build fail,
and looking for the reason, I see that messages such as
those below.
These give me pause, and
pretty much change my mind about if this is appropriate for
Orbit.
I am currently thinking not.
Orbit bundles, besides being
from "third parties" are normally low level function that
does not depend on other Eclipse projects.
This large set of bundles has
so many dependencies on "Modeling" projects, and sounds like
it is a "complete system", that I think it better belongs in
Modeling. Perhaps proposed as
as a sub-project of gmf or
something, if it doesn't fit in to any existing projects.
Missing required plug-in
org.eclipse.buckminster.sax_0.0.0.
Missing required plug-in
org.eclipse.acceleo.engine_0.0.0.
Missing required plug-in
org.eclipse.amalgam.discovery.ui_0.0.0.
Missing required plug-in
org.eclipse.gmf.runtime.diagram.ui_0.0.0.
Missing required plug-in
org.eclipse.gmf.runtime.diagram.ui.render_0.0.0.
Missing required plug-in
org.eclipse.buckminster.sax_0.0.0.
Missing required plug-in
org.eclipse.acceleo.engine_0.0.0.
Sorry this wasn't clearer,
sooner. I think we've made one or two exceptions, but its
been for "small" things that were "low level" in Eclipse,
such as org.eclipse.osgi.resolver (or something ... I forget
what exactly).
Thus, I'll comment out your
contributions from the Orbit feature, for now, and ask you
to discuss the "Modeling project" approach with the Modeling
PMC. (Ed Merks CC'd on this note).
Thanks,
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
|