| AbstractEntryPoint and the workbench [message #1004188] |
Tue, 22 January 2013 19:03  |
 Benjamin Wolff
Messages: 136
Registered: July 2009 |
Senior Member |
|
|
Hi,
since 2.0 RC1 there is a skeleton abstract class for the entry point called AbstractEntryPoint, which is the preferred approach to implement the entry point interface according to the new and noteworthy docs. So far, the implementation of my createUI() method looked like this:
public int createUI() {
Display display = PlatformUI.createDisplay();
int result = PlatformUI.createAndRunWorkbench(display, new MyWorkbenchAdvisor());
display.dispose();
return result;
}
So the WorkbenchAdvisor instance determines which initial perspective to load, which WorkbenchWindowAdvisor (configures the shell etc.) to use, and so on. With the new abstract implementation of the entry point, there doesn't seem to be any hook to use a WorkbenchAdvisor. Is this abstract class also intended to be used to run the RAP workbench? If so, do you have a suggestion how to implement it?
Cheers,
Ben
|
|
|
| Re: AbstractEntryPoint and the workbench [message #1004208 is a reply to message #1004188] |
Tue, 22 January 2013 20:04  |
|
Hi Benjamin,
right, the AbstractEntryPoint is not suitable for workbench
applications. I forgot to mention this, but will add it to the docs.
Thanks for pointing this out.
EntryPoint is not deprecated and will remain supported, so you can
continue to use it as you did. Or you can also use IApplication for
workbench apps. The idea of the base class is just to make it easier for
applications that do not use the workbench and create their own shell,
layout, main loop etc.
Regards,
Ralf
--
Ralf Sternberg
Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
Powered by
FUDForum. Page generated in 0.03023 seconds
] 
Search
Help
Register
Login
Home
