Towards a modern Eclipse UI: Adding Chromium support to the Eclipse IDE
summary
Three approaches are evaluated: use OS browsers, embed Chromium Embedded Framework, or run Electron offscreen rendering. Prototypes exist: CEF prototype runs well on Windows but breaks on Linux/Mac with SWT deadlocks after Chromium updates; Electron prototype uses socket/shared-memory image frames, about 130 lines TypeScript plus 600 lines Java, performs well on Windows/Linux but hits a Mac Retina rendering blocker, increases bundle size (~100 MB) and requires timely Electron/node updates; keyboard mapping and some features remain unfinished.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:15Motivation and UI challenges
- 6:45Browser integration research
- 11:28Chromium prototype demo
- 13:47Electron architecture
- 15:16Technical implementation
- 17:45Prototype performance tests
- 19:17Drawbacks and challenges
- 22:42Conclusion and resources
- 23:46Q&A session
related talks
29mThe Busy RCP Developer’s Guide to Eclipse Theia
27mBuilding Cross Platform Desktop Apps With Electron
39mSwapping your IDE in Eclipse Che
33mApproaching Light Speed - News from the Eclipse Platform Project
36mIf, when and how? - Strategies towards web-based tooling
35mEclipse IDE and RCP Platform: Unveiling the Past, Present and Future
33mWhen changing theme is not enough: swapping your IDE in Eclipse Che
37mEclipse Dirigible's WebIDE - Deep Dive
