Eclipse Community Forums: Graphiti » org.eclipse.graphiti.ui refactoring

Help

Home

Home » Modeling » Graphiti » org.eclipse.graphiti.ui refactoring

Show: Today's Messages :: Show Polls :: Message Navigator

org.eclipse.graphiti.ui refactoring [message #1684651]

Wed, 18 March 2015 14:18

Flavio Donze

Messages: 211
Registered: July 2009
Location: Switzerland

Senior Member

Hello

As described in this post https://www.eclipse.org/forums/index.php/t/965255/, I want to create an image of the bpmn model on the server side.

Since "org.eclipse.graphiti.ui" is IDE dependent (org.eclipse.ui.views.properties.tabbed, org.eclipse.ui.navigator) I was wondering if there are any plans to move certain parts of the UI bundle into separated bundles?
I was thinking about the "org.eclipse.graphiti.ui.internal.figures" and "org.eclipse.graphiti.ui.internal.parts", maybe others would make sense as well.
"figures" should be possible, "parts" looks a more difficult.

For "figures" the main work would be to replace IConfigurationProviderInternal with IResourceRegistryHolder and IDiagramTypeProvider. Also the reference to IPictogramElementDelegate could be problematic, depending on if "parts" is also moved.

It might even be possible to combine RAP with Graphiti at some point.

What do you think about this?

greets
Flavio

Prozessmanagement und Qualitätsmanagement Software QMS/IMS
https://www.scodi.ch

Report message to a moderator

Re: org.eclipse.graphiti.ui refactoring [message #1687004 is a reply to message #1684651]

Thu, 19 March 2015 12:56

Michael Wenz

Messages: 1931
Registered: July 2009
Location: Walldorf, Germany

Senior Member

Hi Flavio,

thanks for this input!

Regarding the separation of the IDE dependent stuff I think this will make
sense and I also thought about that. However, currently there are no
concrete plans in this respect. But I think that would make sense, so just
go ahead and create an enhancement request for Graphiti targeting that.

Regarding the figures/parts separation I am not sure if that will really be
a benefit as long as we rely on GEF 3.x, since that comes with some UI
dependencies. I would see that as part of a potential switch to GEF 4 which
seems to separate UI aspects better. Not fully sure though, as I didn't have
the time to go into more depths of this.

Anyhow, whatever we do in this respect can earliest be targeted for the next
release of Graphiti (after 0.12.0 targeting Eclipse Mars) as next week is M6
and with that we have API freeze.

Michael

Report message to a moderator