| commit | a189378824599658a8409a8c8e3cd6268ed72fcd | [log] [tgz] |
|---|---|---|
| author | Lars Vogel <Lars.Vogel@vogella.com> | Thu Nov 07 22:42:08 2019 +0100 |
| committer | Lars Vogel <Lars.Vogel@vogella.com> | Thu Nov 07 23:35:02 2019 +0100 |
| tree | 25ea1b0f85c68db78b142d8029cba132f17e8d38 | |
| parent | 803d51db53409c8b31613545da2ef131359f90a2 [diff] |
Bug 552691 - [Dark theme] dialogs like rename or delete have white artifacts So avoid styling artifacts we style all elements which are direct and second level children in a Composite. To avoid that this breaks part styling, we do the same stying for the part and the active part. Looks good in a runtime IDE, will run a custom build with this change to verify it more. Scenarios tested in runtime IDE: - Open Java editor -> OK - Use Rename dialog -> OK - Use Java project -> OK, still a known problem with the details page, so same situation -> Plug-in project creation wizard -> OK -> Preference clicked through a lot -> OK -> Property page of project -> OK -> HeapStatus monitor -> OK -> Starting an RCP application and tabs stay "white" and do not grayed out -> Starting an runtime IDE and tabs labels stay "white" and are not grayed out Change-Id: Idfe50da6d550085568fa88e3b81bd530f44f5822 Signed-off-by: Lars Vogel <Lars.Vogel@vogella.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 library. Please install them from the Orbit Download page
Currently the following versions 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.