Some time ago I created a graphical editor with GMF ( xsd->ecore->emf->gmf).
Additionally I created plugins with different views, launchers (debugger) and more.
All those plugins were created with Eclipse Helios.
Now, I would like to create a RCP application out of my plugins.
I did a lot of internet research but still do not really understand how to begin.
I read this tutorial (http://www.vogella.com/tutorials/EclipseRCP/article.html#plugin_creatinge4) but I am still not sure what to do.
If I would do as told in this tutorial, I would have to build all the windows, editors, menus and so on manually, correct ?
And if so, how to get those default eclipse features in my RCP application, like: Create an empty project, starting my "New Diagram" Wizard, double click the diagram file in the project view to open the editor...and so on...
Do I really have to build all those features manually with the Application Model file ??
I really could use some pointers to the right direction.
Thanks in advance!
The tutorial you have found is describing the new e4 API. This does not support a lot of the older 3.x compatibility APIs so it is not suitable for using to build a RCP which uses plugins based on 3.x. The e4 API is good for building new RCPs which don't use 3.x plugins.
Instead you can still build a 3.x style RCP, see this tutorial for more details on doing that. The 3.x style RCP will continue to be supported for a long time.
Related
I am new to programming,
Can anyone suggest how to construct/edit the user interface in Java GWT with ui binder. A GUI editor/designer should be handy but unfortunately I couldn't find one
I am working on an existing project that uses Java and GWT with ui binder with the ui.xml files.
Eclipse Luna as the ide(python in the backend that's another story)
Searched across the internet to find that there is a GWT designer tool but that is discontinued on latest GWT. Rest all other tutorials says to add/edit the .java and .ui.xml codes which is a tired process as my project has got plenty of sheets.
Thanks in adavnce
Just do it by hand.
No editor exists anymore. The old editor you found is dead.
I guess because it was not good enough.
Never used it, programming should be done by hand.
This is more like a work around(as I wouldn't consider this an actual fix/answer)
Here is what I did
Loaded my Project onto Eclipse Kepler with GWT 2.6.1(this version has the fixed designer tool)
Voila, it works like a charm and now I can easily edit/modify the UI.
I know its a dead end if I can't move with an updated version, but its okay for now.
Hope I find an alternate.
Many thanks for the suggestions and answers.
We are redesigning a few of our applications to a new custom framework. Now we want a stage to reuse the Eclipse RCP application GUI and redesign the backend (without using Eclipse RCP framework). So we can easily switch the GUI part to JavaFX. Is it possible to only use the GUI parts of the Eclipse RCP framework without using the Eclipse RCP framework?
We don't want all the Eclipse RCP configuration crap in our new projects and we only need the full GUI layer.
Everything in an Eclipse RCP is an Eclipse/OSGi plug-in and depends on the OSGi plug-in system to work.
If you depend on existing 3.x compatibility mode plug-ins then you are stuck using the 3.x style RCP.
If you don't depend on 3.x mode plug-ins you may be able to use the e4 style RCP which can set up to look any way you like and can be written using JavaFX instead of SWT using the e(fx)clipse code.
No, you cannot use the Eclipse RCP framework without using the Eclipse RCP framework. You might want to look at e(fx)clipse which allows you to sue the Eclipse RCP framework with a Java FX layer
I have existing java application where GUI had mainly built using Swing and prefuse API (http://prefuse.org/).
I want to develop eclipse plugin for this application. I have read in vogella tutorial that SWT is prefer to use for plugin development.
My problem is that if I should use SWT, then how can I convert each swing and prefuse API component to SWT?
PS: If I use existing GUI in my eclipse plugin project, then when I run the plugin as "Eclipse Application", it display GUI outside eclipse which I am not sure is correct behaviour for plugin development.
The http://wiki.eclipse.org/Albireo_Project might help:
"The Albireo project builds on the SWT_AWT bridge to provide more complete Swing/SWT integration, resulting in a better "out-of-the-box" experience and more credibility for the entire notion of Swing/SWT integration."
Extend the SwingControl and implement createSwingComponent() and getLayoutAncestor().
http://eclipsesrc.appspot.com/jsrcs/org.eclipse.albireo/org.eclipse.albireo.core/src/org/eclipse/albireo/core/SwingControl.java.html
What type of developer are each of these IDEs aimed at? Is one IDE a superset/subset of the other? What can I do using one and not the other?
I'm looking to do mostly desktop based (Windows) work for now so I believe I am correct in ignoring the Java EE download and focusing on these two.
The comparison of features page isn't helpful as I'm still new to Eclipse and Java. For example "Code Recommenders Developer Tools" means nothing to me yet.
Eclipse standard has been downloaded 1.7 million times and is 246MB (as at 7-Sep-13). While Eclipse IDE for Java developers has been downloaded 430,000 times and is 151MB.
So I'm guessing Eclipse Standard is the way to go, but why do they offer the second option?
All the other answers are more or less true, but miss the point (in my opinion), The download page states it clearly:
Eclipse Standard ...
The Eclipse Platform, and all the tools needed to develop and debug it
versus
Eclipse IDE for Java Developers ...
The essential tools for any Java developer, including a Java IDE, a CVS client, Git client, XML Editor, Mylyn, Maven integration...
So if your focus is to develop for Eclipse itself, the Eclipse Standard includes all what you need (including the sources of all features and plugins).
If your focus is Java development (not Eclipse plugins), you should start with the Eclipse IDE for Java Developers.
If your focus is Java EE development, it is simpler to start with Eclipse IDE for Java EE Developers and so forth ...
The comparison page could certainly use some links, nevertheless a quick web search will tell you all about those plugin.
For your needs, you might look into the "for Java Developers" package, as it contains WindowBuilder, which let's you define GUIs visually in several frameworks.
(Code Recommenders is also nice, but I've personally found it a bit hit-or-miss)
However, you're fine installing any of the packages either way, since you can always install the plugins you need later on. My recommendation is to simply read about those plugins and make an informed decision on what you should install.
If you're doing GUI work then you might choose the Java Developers package as it comes with WindowBuilder.
Other similar questions are:
https://stackoverflow.com/questions/7835305/what-are-my-options-for-developing-a-gui-in-java-in-eclipse
Best GUI designer for eclipse?
Create GUI using Eclipse (Java)
The difference between the eclipse downloads are just the pre-installed plug-ins.
I'd go with standard and install the plug-ims i want, but take what fits you.
I have already developped a Java project using Eclipse.
Now I would like to integrate an help system to allow the user to open a guide.
Browsing other questions i found this tutorial to set up Eclipse environment in order to use the Eclipse Help System. Anyway, this tutorial and all documentation I found since now, only explain how to use this system creating a new plugin project.
But what about if I want simply add the help system to an existing Java Project created in Eclipse IDE?
Which step should I follow to update my project configuration?
Is it possible to integrate Eclipse Help system, without using eclipse?
No, the help system you point to is an eclipse plugin based system, useful with RCP programs. See http://wiki.eclipse.org/RCP It will only run in the context of an RCP application.
You might be able to write an RCP app that contains only help, launch it, and communicate with it through http from your java app, but it's not a simple integration ... and you still have to build your help documents so that org.eclipse.ui.help can see them.