6. These trend lines point to web technologies, new user interface metaphors, and distributed infrastructure. Now is the time to rethink elements of the platform so that Eclipse may remain at the forefront of application development.
15. There is growing demand for software components that can run both in traditional desktop environments, and Web browser environments.
16. We will support this demand by providing first-class integration of web-based components in the Eclipse platform. In particular, we will support embedding of user interface components written in JavaScript into the e4 UI, and provide access to e4 API for JavaScript components.
23. SWT/JFaceアプリケーションのために作成していたレイアウト用の コードや UI 関連のコードの大部分が不要 ※Just take a look at the e4 forum: the first page contains 40 messages. Of those messages, 18 (as of today 18.04.2010) are related to XWT, that is almost 50% of the overall questions found on the e4 forum. 6
26. This includes binary compatibility, contract compatibility, workbench model compatibility, and workspace compatibility.
27. e4 July 2010 includes a set of bundles that are binary and API contract compatible with Eclipse Platform UI API from the Eclipse Helios (3.6) release.
28. This set of bundles is known as the compatibility layer, and is intended to be used to create a full Eclipse SDK release on e4 that is fully compatible with previous Eclipse project releases.
29. Thus while e4 July 2010 itself is not compatible with previous Eclipse project releases, it provides the necessary infrastructure to allow a fully compatible e4-based release of the Eclipse SDK to be created.8
