Thanks to the good compatibility of Eclipse E4, the interface developed using 3.x technology can also be displayed in E4 style. During the actual switchover process, some problems may occur that could cause the switch to not succeed. This article simply summarizes some of the issues that need to be noted during the switchover process, and it is possible to ensure a successful switchover by identifying these issues.
Make sure to start org.eclipse.e4.ui.css.swt.theme;
Other plugins that need to be guaranteed to start include Org.eclipse.platform, Org.eclipse.runtime, org.eclipse.ui.workbench related plugins;
The applicationcssresources and Cssthemes are configured correctly in the product definition of RCP;
Plugin org.eclipse.ui.themes boot.
The first three articles refer to the official Eclipse documentation: Http://wiki.eclipse.org/Eclipse4/RCP/FAQ#Why_are_my_CSS_theming_not_taking_effect.3F
For the 4th, it is in the process of switching itself encountered. The concrete manifestation is: The interface displays is 3.x, the appearance page of the preference Item themes drop-down list is empty. Debug Discovery Viewspreferencepage.getcssthemes () Gets the themes list empty. After troubleshooting, the Org.eclipse.ui.themes plugin was not started. Therefore, in the plugin.xml of RCP it is best to rely directly on the plug-in.
This article from "Winger" blog, declined reprint!
Eclipse RCP interface switches from 3.x to E4