Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Shared Settings
Configuration
Use case: Users have a single Eclipse install and multiple workspaces. They commonly switch between these workspaces and want to have the same user settings automatically applied.
What happens when you start and the configuration preferences are different than the instance preferences?
- instance overrides config
- config overrides instance
- user prompted
Policy should be #2.
When is this triggered? How is it triggered?
later. by a job. when the extra plug-in starts up it goes and syncs things.
Need to ensure that we don't aggresively start plug-ins.
Can we do this early enough? What happens to the UI when we start changing settings on the fly? Will people be hacking away and then their windows will change from underneath them?
Team Project Settings
Use case: Users have groups of projects checked out from a repository, into their workspace. They want to maintain a consistent set of preferences across all these projects.
- do you have a master project?
- can a project belong to multiple working sets?
If there is no master project, then you need to be able to handle the case when you start up and there are conflicts between the projects.
Need to add keys to the projects: to indicate that the project is a part of a working set store a long which is the timestamp of the last preference change?
Need to create a resource change listener to handle project creation. (loading from the repo)
No need to prompt the user since they have already indicated that they wanted the project as part of the working set.