Re: [eclipse-ide-wg] A (slightly different) proposal to address the cons

[Andrey Loskutov <loskutov@xxxxxx>]

Hi Martin,

Assuming you have a plan how to solve all the technical issues, the proposal leaves a big open question: who should drive all that (non trivial) work?

Last time we've tried to add Chromium based rendering engine to SWT we end up with bulk of unsupported code based on unstable / not secure old Chromium build.
The contributors that pushed initial contribution were not responding to any bugs / not maintaining original contribution and were only interested in promoting their own commercial offering, so finally Chromium support was removed again.

So if we have both a plan and resources, why not?

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov


> Gesendet: Dienstag, 15. November 2022 um 09:24 Uhr
> Von: "Martin Lippert" <mlippert@xxxxxxxxx>
> An: "Discussions on Eclipse IDE Working Group" <eclipse-ide-wg@xxxxxxxxxxx>
> Betreff: [eclipse-ide-wg] A (slightly different) proposal to address the constant struggle with browser support in Eclipse
>
> Hey!
> 
> I would like to propose and discuss a slightly different approach to address the browser integration issues and difficulties that we suffered from over the years.
> 
> My quick summary of the situation:
> - support for the system browser in SWT is a constant source of issues and difficulties
> - the support is outdated and problematic - and I don’t see a solution for this coming up anytime soon
> 
> My proposal:
> - remove the system browser integration from SWT altogether
> - ship a Chromium-based rendering engine as part of SWT
> 
> The details:
> - there are different technical proposals around to integrate Chromium with SWT (e.g. (J)CEF and Electron offscreen rendering)
> - pick the most promising one (performance-wise probably CEF)
> - include the latest (CEF) runtimes that are available