commit | ffea23c6275993d93d497f8834baa9668c1e0ffc | [log] [tgz] |
---|---|---|
author | Mickael Istria <mistria@redhat.com> | Sat Feb 02 15:33:30 2019 +0100 |
committer | Mickael Istria <mistria@redhat.com> | Tue Feb 05 13:09:12 2019 -0500 |
tree | a2b5fa8cb8f06deaf56e411de6173a1d3fb5d236 | |
parent | fb721e93e8067b50b16a4a481ec4a3add11d6b17 [diff] |
Bug 530450 - [Project Explorer] UI Freeze with nested projects Change in marker used to trigger a refresh of the viewer, while an element update should be invoked instead. So we removed the code cascading markers changes to refresh from NestedProjectContentProvider. Instead, we made the NestedProjectsLabelProvider taking care of listening to marker changes and reacting by updating its internal model. Then, since the Label Provider doesn't have a reference to the viewer, we made the contentprovider register itself for updates to the labelprovider so the later invokes an updates of modified elements in the viewer after its internal marker model updates. Change-Id: Ib207a1bc8c7ff7a6aed85c2dc6e8ebe5420b1252 Signed-off-by: Mickael Istria <mistria@redhat.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.