- 1 Planning page for Neon
- 2 Themes
- 2.1 Performance and stability of platform user interface
- 2.2 Simplify and improve the user experience
- 2.3 Generify platform API
- 2.4 Simplify committer and contributor workflow
- 2.5 Java 8 support in JFace Databinding
- 2.6 Migrate Mylyn notifications framework to platform UI
- 2.7 Provide default spelling engine in platform UI
- 2.8 CSS Enhancements and better support for the dark theme
Planning page for Neon
Our planning list and assumptions are [].
Performance and stability of platform user interface
The Eclipse Platform UI team need to continue to improve stability and performance of the user interface. This includes regressions but also improvements compared to 3.x. The UI freeze monitoring and the reports created by the automatic error reporting tooling will also be used for this activity.
Simplify and improve the user experience
The Eclipse Platform UI team plans to simplify the user workflow. For example, by adding the smart import wizard to platform, the user experience for importing project should be improved.
Generify platform API
The Eclipse Platform UI team plans to evaluate and, if possible, implement generics in its API. This journey started in 4.4 but needs to continue. Generics are planned to be evaluated at for JFace Dialogs, the JFace Viewers and JFace Databinding.
Simplify committer and contributor workflow
The Eclipse Platform UI team will continue to simplify the workflow of existing and new committers and contributors. This includes the activation of more test suites during the Gerrit build trigger, code cleanup, migration of the tests to modern constructs (JUnit4, modern Assert frameworks, etc). It also includes the update of the code to remove compiler warnings. To be more inviting to other Open Source contributors we also need to update our code with constructs of modern Java versions.
Java 8 support in JFace Databinding
The Eclipse Platform UI team plans to support the new Date and Time API from Java 8 in JFace Databinding.
Migrate Mylyn notifications framework to platform UI
The Eclipse Platform UI team plans to migrate the Mylyn notification framework to platform UI. This change has been discussed with the Mylyn team and was well received.
Provide default spelling engine in platform UI
Currently the default spelling engine is provided by JDT. The Eclipse Platform UI team plans to migrate this spelling engine to platform.ui.
CSS Enhancements and better support for the dark theme
The Eclipse Platform UI team plans to enhance CSS support. A new CSS parser will be evaluated to support CSS 3.0 and to improve performance. The Eclipse Platform UI team will continue to cooperate with other teams like JDT and SWT to improve the styling capabilities in general and the dark theme as a special use case of the CSS styling.