We can definitely do better as mentioned in several comments already. Just 
wanted to mention ? though not very user-friendly ? there is a mechanism 
that allows to set most preferences (those that appear in the preference 
dialog) per install(s):

eclipse[c].exe  -pluginCustomization <path to plugin_customization.ini 
file> 

where the file contains the preferences [1]. See e.g. 
https://bugs.eclipse.org/287579 for an example on how to set the encoding 
and the line separator per install.

Dani

[1] 
http://git.eclipse.org/c/platform/eclipse.platform.common.git/plain/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html


From:   Henrik <h...@protos.de>
To:     Cross project issues <cross-project-issues-dev@eclipse.org>
Date:   15.07.2013 18:45
Subject:        [cross-project-issues-dev] Preferences (topic was touched 
in "Eclipse smells kind of dead" thread)
Sent by:        cross-project-issues-dev-boun...@eclipse.org



Hi all,

I know that preferences can be imported/exported.
Yet I find it a bit cumbersome to care about that every time I create a 
new workspace.

Wouldn't it make sense to have preferences arranged in several layers 
similar to git: system/user/workspace?

Also I could imagine to offer a web page with collections of preference 
settings.
They could be ordered in categories (maybe aligned to the packaged Eclipse 
installations).
And we could offer a possibility for users to cast their vote to be able 
to rank the settings.

-Henrik
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to