Several Eclipse based projects still rely on Eclipse 3.x API and mechanisms that are outdated. Although still valid, the performance of the product and its development can be improved by using state-of-the-art technologies that are already provided by the Eclipse Platform and the Eclipse infrastructure.
Several Eclipse based projects still rely on Eclipse 3.x API and mechanisms that are outdated. Although still valid, the performance of the product and its development can be improved by using state-of-the-art technologies that are already provided by the Eclipse Platform and the Eclipse infrastructure.
If you know how to write Eclipse 3 UI plugins but you are not confident with the E4 writing, this talk is for you.
Pure E4 plugins can be fully mixed with legacy E3 plugins and there are no reasons today to still write legacy Eclipse 3 plugins while Eclipse 4 provides a lot of advantages.
This talk will compare in details the ways to write the UI code in Eclipse 3 vs Eclipse 4, without loosing the Eclipse 3 modularity while increasing testability.
This overview will focus on views, perspectives, editors, commands, preference pages and so on…
Let’s take 35 minutes to explain how you can write your new plugins using the Eclipse 4 concepts and definitively stop to use the E3 UI extension points.
Writing pure Eclipse 4 plugins is easier (thanks to injection, application model fragments, spies, …) and simplifies the unit tests for UI components.
This talk will also explain how to mix your pure E4 plugins properly with your E3 legacy plugins. It will be a complementary talk if you could not attend the E4 tutorial.
Eclipse Theia is a new project for developing IDE-like applications that run as native desktop apps or in browsers. While its scope is similar to the Eclipse RCP platform the technology stack is very different.
In this session, I will explain Theia’s architecture and the technology it is based on by means of Eclipse, Java and Eclipse RCP concepts and terminology. We will go through the most important ideas and compare them to something you are familiar with. I will point out similarities as well as differences to give you a solid overview of the topic.
The E4 Runtime has been available for more over 6 years, and we have started to write our own POJOs bound to the application model.
Nevertheless, there are not a lot of easy solutions to test these POJOs as the current UI test system libraries are still bound to the full E3 RCP stack.
This talk is about pure E4 testing. It will remind you the basic principles of the E4 runtime and architecture regarding the application model and the contribution with fragments, and it will introduce the E4 tester tooling to help you in your test management.
