Re: [e4-dev] API and package structure

[Brian de Alwis <briandealwis@xxxxxxxxx>]

I've appended below the e4 classes that are imported in Kizby (which is still on 4.1M4).  Here are some confusing bits:

• UI elements are scattered between .ui.workbench and .ui.model and .ui.workbench.modeling
• Command- and handler-related items are both in .core.commands and .ui.model.application.commands.

Since the modelled workbench can make sense without any actual windows (defining commands and handlers, and addons), perhaps the ui.model.application should be promoted to a top-level item?  And unless it's supposed to be possible to have an e4 UI without the workbench, perhaps .ui.workbench merged as just .ui?

import org.eclipse.e4.core.commands.ECommandService;

import org.eclipse.e4.core.commands.EHandlerService;

import org.eclipse.e4.core.contexts.Active;

import org.eclipse.e4.core.contexts.ContextFunction;

import org.eclipse.e4.core.contexts.ContextInjectionFactory;

import org.eclipse.e4.core.contexts.IEclipseContext;

import org.eclipse.e4.core.contexts.RunAndTrack;

import org.eclipse.e4.core.di.InjectionException;

import org.eclipse.e4.core.di.annotations.CanExecute;

import org.eclipse.e4.core.di.annotations.Execute;

import org.eclipse.e4.core.di.annotations.Optional;

import org.eclipse.e4.core.di.extensions.Preference;

import org.eclipse.e4.core.services.contributions.IContributionFactory;

import org.eclipse.e4.core.services.log.Logger;

import org.eclipse.e4.core.services.statusreporter.StatusReporter;

import org.eclipse.e4.ui.di.Focus;

import org.eclipse.e4.ui.di.Persist;

import org.eclipse.e4.ui.internal.workbench.swt.E4Application;

import org.eclipse.e4.ui.model.application.MApplication;

import org.eclipse.e4.ui.model.application.MContribution;

import org.eclipse.e4.ui.model.application.commands.MCommand;

import org.eclipse.e4.ui.model.application.commands.MCommandsFactory;

import org.eclipse.e4.ui.model.application.commands.MHandler;

import org.eclipse.e4.ui.model.application.commands.MHandlerContainer;

import org.eclipse.e4.ui.model.application.ui.MContext;

import org.eclipse.e4.ui.model.application.ui.MDirtyable;

import org.eclipse.e4.ui.model.application.ui.MElementContainer;

import org.eclipse.e4.ui.model.application.ui.MUIElement;

import org.eclipse.e4.ui.model.application.ui.MUILabel;

import org.eclipse.e4.ui.model.application.ui.advanced.MPerspective;

import org.eclipse.e4.ui.model.application.ui.advanced.MPerspectiveStack;

import org.eclipse.e4.ui.model.application.ui.basic.MBasicFactory;

import org.eclipse.e4.ui.model.application.ui.basic.MPart;

import org.eclipse.e4.ui.model.application.ui.basic.MPartSashContainer;

import org.eclipse.e4.ui.model.application.ui.basic.MPartStack;

import org.eclipse.e4.ui.model.application.ui.basic.MWindow;

import org.eclipse.e4.ui.model.application.ui.menu.ItemType;

import org.eclipse.e4.ui.model.application.ui.menu.MDirectToolItem;

import org.eclipse.e4.ui.model.application.ui.menu.MHandledItem;

import org.eclipse.e4.ui.model.application.ui.menu.MMenuFactory;

import org.eclipse.e4.ui.model.application.ui.menu.MToolBar;

import org.eclipse.e4.ui.model.application.ui.menu.MToolBarElement;

import org.eclipse.e4.ui.model.application.ui.menu.MToolControl;

import org.eclipse.e4.ui.services.IServiceConstants;

import org.eclipse.e4.ui.services.IStylingEngine;

import org.eclipse.e4.ui.workbench.IExceptionHandler;

import org.eclipse.e4.ui.workbench.IPresentationEngine;

import org.eclipse.e4.ui.workbench.IWorkbench;

import org.eclipse.e4.ui.workbench.modeling.EModelService;

import org.eclipse.e4.ui.workbench.modeling.EPartService.PartState;

import org.eclipse.e4.ui.workbench.modeling.EPartService;

--

Rescue your task list with Kizby!  Free 30 day trial with no obligations.

Visit kizby.com for details.

Attachment: smime.p7s
Description: S/MIME cryptographic signature