Slides from the EclipseCon 2011 session: EclipseCon 2011 - An Early Adopter's Retrospective on an E4 Industrial Project
Abstract:
When it comes to developing a large application from scratch for Airbus Simulation Software, one would surely avoid relying on a framework that's still in beta and with a provisional API. A framework like E4 in early 2010. In this presentation, we will not only explain the reasons of this carefully-thought madness, but also how we succeeded with our approach.
We'll talk about everything we used from stock OSGi services (API-level), Declarative Services, Databinding, E4 Context tricks, extending E4's dependency injection, ... to making a custom build, testing and deployment with Tycho (without PDE's RCP export). But most of all, we will tell you why we did it, what went well and what went wrong, and how we would do it again.
This project has taught us a lot about the best practices with E4 development, we hope to share them and open the discussion on how we see E4's future for RCP applications (and whether you should use E4 for your next RCP application or not).
Talk page on EclipseCon website: https://www.eclipsecon.org/submissions/2011/view_talk.php?id=2103
See the last slide for contact information.
47. (and feel free to come for more) Simon Chemouil [email_address] simach on Twitter Benoit Viaud [email_address]
Notes de l'éditeur
Enough talk: let's see what it looks like
Faire un lien vers Celix / Universal OSGi
Faire le rappel sur la terminologie : E4 / Eclipse4 : (We'll just say E4 because we're lazy, but strictly speaking E4 is the name of incubator project) Faire le lien vers la talk de Tom Schindl
Most configuration should use simple annotations Interaction should be easy using the modeled workbench element injected through annotations Views should aim to be POJOs
Most configuration should use simple annotations Interaction should be easy using the modeled workbench element injected through annotations Views should aim to be POJOs
Most configuration should use simple annotations Interaction should be easy using the modeled workbench element injected through annotations Views should aim to be POJOs
Most configuration should use simple annotations Interaction should be easy using the modeled workbench element injected through annotations Views should aim to be POJOs
Most configuration should use simple annotations Interaction should be easy using the modeled workbench element injected through annotations Views should aim to be POJOs
Most configuration should use simple annotations Interaction should be easy using the modeled workbench element injected through annotations Views should aim to be POJOs
Most configuration should use simple annotations Interaction should be easy using the modeled workbench element injected through annotations Views should aim to be POJOs
DS : on peut faire bcp avec peu
We needed the concept of editors, editor stacks, … not available in the stock E4 Application Model
"This is not really about E4, but it's still relate to using Eclipse technologies and it has to be said"
"Yes, all OSGi services are dynamic, but" Eclipse Contexts have an OSGi lookup strategy
The project was also a testbed for new technologies. The occasion to push ourselves. With the requirement that it would not impair the final result.
![[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)