Plugin development strategy : still Eclipse 3? Really?
summary
Argues that new plugins should use Eclipse 4 concepts instead of Eclipse 3 extension points, showing concrete demos: creating views via application model fragments, importing Eclipse 3 command IDs into E4 fragments, mixing E3 and E4 parts in a perspective using snippets and placeholders, and bridging selections via the selection service. Requires installing Eclipse 4 injection tooling, the fragment model editor and model spies. Provides a GitHub test project that instantiates parts for integration tests and runs under Tycho/Travis; demos run successfully.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:03Legacy Model
- 6:50Fragment Model Editor
- 8:38Create a View Using a Model Fragment
- 9:36Path Descriptor
- 11:12Demo
- 13:58Shared Elements
related talks
35mEclipse IDE and RCP Platform: Unveiling the Past, Present and Future
01h 03mSpring Tools 4 - Eclipse and Beyond
27mMastering your Eclipse IDE - Java Tooling, Tips & Tricks!
37mTips & Tricks - 2022
37mWhat Eclipse IDE must learn from other IDEs to survive?
52mThe Eclipse IDE: The Force Awakens
43mPlug and Play: Power Up DevX with Android Studio Plugins
30m5 things you can do with Maven in Eclipse other IDEs don't want you to know