commit | b89221479f198596184c480b1497989ad7d43b83 | [log] [tgz] |
---|---|---|
author | Mikael Barbero <mikael@eclipse.org> | Fri Jan 30 18:49:43 2015 +0100 |
committer | Dani Megert <Daniel_Megert@ch.ibm.com> | Mon Apr 25 15:22:09 2016 -0500 |
tree | 3f0035464ee674b709d413d7739b91e0942c0c2d | |
parent | 5715a371f7c81926f90b17e5f75bbea1bc3aa4af [diff] |
Bug 486644 - Automatic save of dirty editors -Creates model fragment to save dirty editors -Registers to the Event system for the dirty event and in case an editor is dirty it saves every 20 s (the value is modifiable in preferences). -Add a new Auto-save preference page (under Editors) that allows to enable/disable the auto-save and change the interval of auto-save. -Add PreferencePage tests Change-Id: I9bb0319faa344ed185b32dc3442d1e618b86a682 Also-by: Lars Vogel <Lars.Vogel@vogella.com> Also-by: Axel Richard <axel.richard@obeo.fr> Signed-off-by: Mikael Barbero <mikael@eclipse.org>
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] 1.
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] 2 page on the team wiki.
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.