Community
Participate
Working Groups
There have been a number of features added to the E3.x fragment that have not been reflected in the e4 variant. The e4 variant was originally intended to make the system menu integration available to pure e4 apps. It's unclear what should happen if there are changes that properly belong in the org.eclipse.ui land.
This bug follows on bug 328755. With the new SWT Display.getSystemMenu() APIs (bug 338825 and bug 329456), we should see if there's a way to allow the pure e4.workbench.renderer.swt.cocoa fragment to co-exist with the E3.x ui.cocoa fragment. The e4 fragment does two things: (1) it handles selections from the pillbox (upper-right on windows), and (2) it remaps the About, Preferences, and Quit items. When any of these elements are selected, it invokes an appropriate command through the e4 command service. It's possible that if the e4 and E3.x cocoa bits are loaded simultaneously, then we'll have two listeners for About, Preferences, and Quit. One possibility would be to use a a system property for the two bits to communicate whether the mapping has been done? Alternatively one could check to see if the other bundle is available and loaded. I think this might be my preference.
These changes were made Wed Apr 27, 2011 in commit 'a58d957a4eab69da0d8411b78892e38fc6b3820e'.