Uses of Interface
org.eclipse.e4.ui.model.application.MApplication
Package
Description
Application programming interfaces describing the Eclipse 4 application model elements.
Application programming interfaces describing the Eclipse 4 fragment model elements.
Application programming interfaces describing Eclipse 4 handlers and the workbench.
Application programming interfaces for interaction
with and extension of the Eclipse Platform User Interface.
-
Uses of MApplication in org.eclipse.e4.ui.internal
ModifierConstructorDescriptionLocaleChangeServiceImpl
(MApplication application) Create a newLocaleChangeServiceImpl
for the givenIEclipseContext
. -
Uses of MApplication in org.eclipse.e4.ui.model.application
Modifier and TypeMethodDescriptionMApplicationFactory.createApplication()
Returns a new object of class 'Application'. -
Uses of MApplication in org.eclipse.e4.ui.model.application.impl
Modifier and TypeClassDescriptionclass
An implementation of the model object 'Application'. -
Uses of MApplication in org.eclipse.e4.ui.model.application.util
Modifier and TypeMethodDescriptionApplicationSwitch.caseApplication
(MApplication object) Returns the result of interpreting the object as an instance of 'Application'. -
Uses of MApplication in org.eclipse.e4.ui.model.fragment
Modifier and TypeMethodDescriptionMModelFragment.merge
(MApplication application) Merges this MModelFragment into an MApplication. -
Uses of MApplication in org.eclipse.e4.ui.model.fragment.impl
Modifier and TypeMethodDescriptionModelFragmentImpl.merge
(MApplication application) StringModelFragmentImpl.merge
(MApplication application) -
Uses of MApplication in org.eclipse.e4.ui.workbench
Modifier and TypeMethodDescriptionorg.eclipse.emf.ecore.resource.Resource
IModelResourceHandler.createResourceWithApp
(MApplication theApp) Creates a resource with an app Model, used for saving copies of the main app model. -
Uses of MApplication in org.eclipse.ui
Modifier and TypeMethodDescriptionstatic Optional<MApplication>
PlatformUI.getApplication()
This methods allows code of eclipse.ui to gracefully migrate to E4 as it has the following properties: It does not throw an exception but returns an empty optional if something is not ready (yet or anymore) so code can choose how to handle this (e.g. useOptional.orElseThrow()
if required orOptional.orElse(Object)
if a fallback exits. If this is is actually a (ui) Workbench running, this is returned and could be used If not the service registry is searched for an org.eclipse.e4.ui.workbench.IWorkbench so code can run inside a pure E4 (e.g. -
Uses of MApplication in org.eclipse.ui.internal
Modifier and TypeMethodDescriptionfinal void
BindingToModelProcessor.addBinding
(MApplication application, Binding binding) BindingToModelProcessor.getBindingContext
(MApplication application, String id) static String
CoolBarToTrimManager.getToolbarLabel
(MApplication application, MUIElement elt) void
WorkbenchPage.setup
(MApplication application, EModelService modelService, IEventBroker broker, MWindow window, EPartService partService) ModifierConstructorDescriptionCoolBarToTrimManager
(MApplication app, MTrimmedWindow window, List<MTrimElement> workbenchTrimElements, IRendererFactory rf)