Community
Participate
Working Groups
Because Eclipse preferences import and export is too much things imported, and keys are hidden inside, so we creating a proper keys settings import/export for easily customize keys for different users and companies.
The Export CSV is for reporting, not for exporting/importing. The correct way to do this is to provide an org.eclipse.ui.preferenceTransfer extension so you can use File>Export...>Preferences and select Keys only (just like there are currently transfers for "Installed JREs" only) PW
Yes, I know how to export the keys by File>Export...>Preferences, but use that way, the export keys are magic things. I want the export keys can be human readable and exchanged between people. And besides, we can use this functional to define custom Keys Scheme. For example, we can define custom keys for our company, and clearly readable.
(In reply to Yonggang Luo from comment #2) > Yes, I know how to export the keys by File>Export...>Preferences, > but use that way, the export keys are magic things. I want the export keys > can be human readable and exchanged between people. > And besides, we can use this functional to define custom Keys Scheme. > For example, we can define custom keys for our company, and clearly readable. To define whole key schemes, you need to use plugin.xml and the org.eclipse.ui.bindings extension point. That can't be done with Import/Export at all. The CSV export doesn't contain enough information to re-import, and it doesn't make sense to me to support a second way to import/export keybindings when preferences with an optional preferenceTransfer are the import/export mechanism In Juno and Kepler, the keybindings are stored in the application model. You can create a fragments e4xmi file (looks like XML) to add MKeyBinding elements to an MBindingTable, but without an existing model to work against it can be hard to do it by hand. It sounds like you need to write a tool that can read your tables of keys however you want to specify it and generate a plugin with plugin.xml that you can use with eclipse. PW
Created attachment 235744 [details] I create a patch for the Export part. No test attached. how to test it?
As mentioned, import/export of CVS is not an option. If you want to do that you can create your own plugin and share it within your company. If you want to contribute a preferenceTransfer that would certainly help with keybinding only preferences. PW
Could there be a message to warn the user that the exported CSV is not importable?
Sure, we just need a patch to implement it. PW
We had a discussion at Eclipse Hackathon about the usability of a warning message. As a result we think that it is just disturbing and instead the function should be documented. There it will be mentioned that the exported data is not meant to be imported. Opened bug#519781
