Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Platform UI/Plan/4.8"

Line 9: Line 9:
 
== Simplify and improve the user experience ==
 
== Simplify and improve the user experience ==
  
The Eclipse Platform UI team need to continue to simplify and improve the user workflow in the Eclipse IDE. For example, Dialogs should use verb orientated labels instead of OK and cancel and we should allow to search and filter. It it planned to integrate the Glance project into the platform code to provide general search functionality.
+
The Eclipse Platform UI team need to continue to simplify and improve the user workflow in the Eclipse IDE. For example, Dialogs should use verb orientated labels instead of OK and cancel and we should allow to search and filter. It it planned to integrate the [http://ystrot.github.io/glance/ Glance project] into the platform code to provide general search functionality.
  
 
== Code cleanup, Simplify platform API and simplification of the committer and contributor workflow==
 
== Code cleanup, Simplify platform API and simplification of the committer and contributor workflow==

Revision as of 16:13, 23 August 2017

Planning page for Photon (4.8)

You find all bugs targeted for this release in our Eclipse 4.8 milestone wiki. The note and newsworthy of all Eclipse top-level projects can be found under Eclipse 4.8 Photon Note and Newsworthy.

Performance and stability

The Eclipse Platform UI team need to continue to improve stability and performance of the user interface. This includes improving the initial startup time of the Eclipse IDE as well as improving the interactive performance.

Simplify and improve the user experience

The Eclipse Platform UI team need to continue to simplify and improve the user workflow in the Eclipse IDE. For example, Dialogs should use verb orientated labels instead of OK and cancel and we should allow to search and filter. It it planned to integrate the Glance project into the platform code to provide general search functionality.

Code cleanup, Simplify platform API and simplification of the committer and contributor workflow

The Eclipse Platform UI team neeed continue to simplify the workflow of existing and new committers and contributors. This includes the migration of the test suite to JUnit 4 or JUnit 5, code cleanup and improved API. It also includes the update of the code to remove compiler warnings. Also outdated Java constructs like for example StringBuffer should be replaced with better performing constructs like StringBuilder.

To be more inviting to other Open Source contributors we also need to update our code with constructs of modern Java versions. Compiler warnings but also issues identified by code scanners like Sonar should be reduced.

Enhance the generic editor

Add to the Generic Editor missing interesting features such as folding, aggregated hover...

Factorize common code features, commands and actions into a Language Toolkit

Platform UI/Text should provide the definition of the very usual code-related commands, so each language could simply add handlers rather than redefining commands. That would also allow a better factorization of UI and shortcuts, and thus more consistency across plugins.

Improve light and dark theme

The Platform UI team plans to improve the light and dark theme. For example, in several cases popups are dark in the light theme under Linux and this should be solved.

Provide a Tip of the day

To improve the experience of new Eclipse users, the Platform UI team plans to provide a Tip of the day framework. During startup such a tip will be displayed, unless the user decides that it should not be shown anymore. An extension point will be provided so that other plug-ins can contribute tips.

Back to the top