Migrate SWT to FFM

未关闭
#3,605 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
java
领域
desktop

调研方向

Start by reviewing the linked FFM migration prototype and the existing SWT platform bindings. The issue identifies GTK4, WebKit, GLX, the Linux AWT bridge, Win32, Cocoa, C.java, and Callback.java as remaining areas; determine which is not already covered before choosing a scope. Done means the selected binding is migrated and validated without regressing the IDE or SWT tests; the issue notes that FFM performance is still under investigation.

由索引模型根据 Issue 内容生成。

描述

We should migrate SWT GTK3 and GTK4 for use FFM. I already prototyped that and have a running Eclipse IDE based on https://github.com/vogella/eclipse.platform.swt/tree/ffm-migration.

Not yet covered: GTK4, WebKit, GLX and the AWT bridge on Linux, Win32 and Cocoa.

Also not yet done: C.java and Callback.java to FFM in the product build as they live in shared folders that the win32 and cocoa builds also compile, and those have no FFM version. That's why the product build still loads the JNI libraries.

Good news is, IDE starts without any failures and according to the SWT tests, our vogella SWT harness and our vogella Eclipse harness the IDE is pixel identical.

Image

Performance with FFM is currently worse compared to JNI, we are currently investigating.

主要语言
Java
星标
202
派生
206
平均合并
1 天 12 小时
30 天内合并 PR
115

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

eclipse-platform/eclipse.platform.swt 的其他 Issue

查看 eclipse-platform/eclipse.platform.swt 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。