• Menus and Toolbars: This is a fairly generic definition, suitable for directly implemented operations.
• RCP: This is a Sash/Stack/Part containment model very much like the legacy one.
• Commands: This is the e4 version of the Commands/Handlers/Bindings infrastructure. Use this model if you need more sophisticated operations like key bindings, retargetable commands (Undo, copy...).
• Trim: Using these elements allows clients to add trim containers on any side of their window and populate them with ui elements.
• Editing: This is a specific element used to gain access to the legacy editor behavior.
• Shared Elements: These elements allow reuse of various model elements in different parts of the model. It will be used in the compatibility layer for supporting the sharing of views and editor areas between different perspectives.

The Eclipse SDK 4 includes styling data to implement the new IDE look and feel, but rich client applications can employ different CSS styling to achieve a significantly different widget appearance.

• Context hierarchies. Contexts can be nested within a parent context to override services provided by their parent. This enables application code written in one context to be easily transferred to work in different contexts.
• OSGi service lookup. Contexts can be used to obtain references to OSGi services. The context takes care of tracking dynamic service changes and cleaning up unused services when contexts are discarded.
• Dependency injection. Values from a context can be injected into an application object. This results in injectable fields and methods in the application object being provided with values defined in the context. Injection completely removes direct dependency from application code onto the framework.
• Storage of functions. Contexts can store functions that are evaluated lazily to obtain context values. A client retrieving values from a context may be obtaining raw values stored in the context, or the result of some function that was evaluated at the time of the context lookup.
• Traditional change notification, and registration of data-binding style update code with a context. Each time the registered update code is run, the context tracks which context values were referenced. Subsequent changes to any of those values will result in the update code re-running. Updates and events are batched and queued to avoid superfluous notifications.

As a result of this work the dependency injection implementation is available as an independent service. While the exact APIs are still under construction and will change, we expect to make the javax.inject-based dependency injection available as one of the core Eclipse 4 application platform services.

• Platform
• Java development tools
• Plugin Development Environment
• Equinox

• There is a 30% improvement in the overall performance of the views
• Two new interfaces have been added to the provisional API: IModelProxyFactory2 and ITreeModelViewer
• The Copy and Find actions have been re-written to work better with the virtual views
• A new viewer filter extension has been added to TreeModelViewerFilter, mitigating scrollbar presentation issues

.MToolControl.TrimStack {
	frame-image:  url(./winXPTSFrame.PNG);
	handle-image:  url(./winXPHandle.PNG);
	frame-cuts: 5px 1px 5px 16px;
}

frame-image and handle-image define the images to be used to draw the frame. The frame-cuts attribute is a set of 4 integer values that are used to divide the frame-image into specific areas by defining two widths and two heights (the third is just the image size minus the sum of the other two. This allows us to determine what part of the image to use for the top/right corner.

Here is a more interesting example that illustrates the power this gives to applications to customize their appearance:

To replace the default Find... actions clients must provide an adapter for the interface org.eclipse.debug.internal.ui.viewers.model.provisional.IViewActionProvider.

For more information see the Javadoc for org.eclipse.debug.internal.ui.viewers.model.provisional.IViewActionProvider with an example available in the org.eclipse.debug.examples.ui bundle found in the Platform Debug Git repo.

The Apache Felix Gogo project has developed an advanced shell for interacting with OSGi frameworks. Instead of continually enhancing the built-in Equinox Framework console, a new external Equinox Console bundle has been created that uses the Apache Felix Gogo bundles. The new Equinox Console bundle continues to provide support for the Equinox Console APIs (package org.eclipse.osgi.framework.console). It also adds many new enhancements which are possible through the use of the Gogo shell. This includes features such as tab completion, command history, piping, grep, telnet and ssh connections, and more. Type help on the console to see a list of available commands, or help <command-name> for information on how to use each command.

For the Juno release, Equinox will no longer support the use of older Jetty implementations and we are no longer shipping Jetty 6. The Equinox HTTP service implementation will no longer work with the Servlet 2.5 and JSP 2.1 APIs. Also note that the Jasper and expresson language implementation bundles have changed in order to support the Servlet 3.0 and JSP 2.2 specifications. The following bundles have been removed:

• org.apache.jasper
• org.apache.commons.el
• org.mortbay.jetty.server
• org.mortbay.jetty.util

• org.eclipse.jetty.continuation
• org.eclipse.jetty.http
• org.eclipse.jetty.io
• org.eclipse.jetty.security
• org.eclipse.jetty.server
• org.eclipse.jetty.servlet
• org.eclipse.jetty.util
• javax.el
• org.apache.jasper.glassfish
• com.sun.el

Default Tray Item

Highlighted Tray Item

• ExtendedModify
• LineGetBackground
• LineGetStyle
• TextChanging
• TextSet
• VerifyKey
• TextChanged
• LineGetSegments
• PaintObject
• WordNext
• WordPrevious
• CaretMoved

For more information on using this new property see How do I specify the default type of native renderer that is used by the Browser? .

For an example of how to use this API see Snippet 359.