Leveraging Eclipse 4 API to Build Components for the Future

Notice: Starting now, Eclipse Live will be archived. You will no longer be able to login or post to the website. New videos will be shared via the Eclipse Foundation YouTube Channel. If you’d like to submit a video, please email us at youtube@eclipse.org.

If you have any questions or concerns, feel free to share your comments on Bug #405642 - Eclipse Live Migration to YouTube.

Eric Moffat

Abstract:

When Eclipse 4.2 ships we'll be API compatible with the previous versions of eclipse but so what? Given the effort we've put into this if all that Eclipse 4 offered was a re-write of the existing presentation and some CSS then the answer would indeed be 'so what'. However, that is most certainly not the case, Eclipse 4 has a completely new paradigm underlying the compatibility layer. Based on a combination of a Modelled UI and Dependency Injection (DI) this new core API can be used to take the eclipse user experience to places we were never able to go in 3.x, both in the eclipse platform as well as for the components that adopt the new API.