| commit | 433a7285783c47612cc62a7b385253449247caa2 | [log] [tgz] |
|---|---|---|
| author | John Taylor <johnpaultaylorii@gmail.com> | Fri Jun 19 14:46:19 2020 -0400 |
| committer | Mickael Istria <mistria@redhat.com> | Mon Jun 22 03:51:55 2020 -0400 |
| tree | 33e6bb0f1b18d2a8245cc75938a14488517350e3 | |
| parent | 3b743da21c853e0ff1fb749c28e7f118ff72dfb2 [diff] |
Bug 564488 - Update prefs when ColorRegistry updates Adds a listener that ensures the internal preferences for the color registry are updated when the color registry is updated via .put(). This requires a few other code tweaks to ensure that there is no possibility of infinite loops, since there is also a listener to update the registry when the prefs are updated. Additionally, WorkbenchThemeManager.updateThemes has to ensure that all colors in the registry get properly refreshed, instead of only the ones with ColorOverride definitions. Change-Id: Ie6ca55af966aa74e17f536eed0d53dc810ebee6d Signed-off-by: John Taylor <johnpaultaylorii@gmail.com>
Thanks for your interest in this project.
Platform UI provides the basic building blocks for user interfaces built with Eclipse.
Some of these form the Eclipse Rich Client Platform (RCP) and can be used for arbitrary rich client applications, while others are specific to the Eclipse IDE. The Platform UI codebase is built on top of the Eclipse Standard Widget Toolkit (SWT), which is developed as an independent project.
Website: http://www.eclipse.org/platform/ui/
For more information, refer to the Platform UI wiki page.
Contributions to Platform UI are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. For a complete guide, see the Platform UI - How to contribute wiki page page on the team wiki.
Several test plug-ins have a dependency to the Mockito and Hamcrest libraries. Please install them from the Orbit Download page]3:
Currently the following plug-ins are required:
You need Maven 3.3.1 installed. After this you can run the build via the following command:
mvn clean verify -Pbuild-individual-bundles
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!
Contact the project developers via the project's “dev” list.