|Graphiti and e4 / compatibility layer [message #903480]
||Thu, 23 August 2012 15:20
| Johnny Qin
Registered: April 2012
I see ppl talking about Graphiti and e4 on the forum, at least in these couple of threads
Seems right now compatibility layer is a must to have Graphiti work with e4 concepts. I am not sure about what this "e4 compatibility layer" really means. In Lars Vogel's tutorial, seems "org.eclipse.rcp" feature should be added to feature based product and he points out that "In Eclipse 4 this feature has been upgraded to include most of the necessary additional plug-ins for the compatibility mode. If your product is based on this feature you can directly start your Eclipse 3.x product and it will work."
In my feature based product file, I have feature as follows.
<feature id="my.own.feature" version="1.0.0.qualifier"/>
Every time I add a graphiti plugin as a dependency of any local plugin (in MANIFEST file). That local plugin cannot run. Am I missing any feature in the product?
When I created a plugin in Juno and checked Graphiti editor template, "org.eclipse.ui" is automatically added as a dependency. Am I suppose to add some feature including "org.eclipse.ui" plugin to my product? This is completely Eclipse 3.x stuff, I am really getting confused about how to take advantage of compatibility layer to find a work-around and get Graphiti editor work in an e4 rcp application.
Can anyone provide a tutorial or example? Just to get people started with the Graphiti and e4 integration.
Powered by FUDForum
. Page generated in 0.01755 seconds