Exported uk.ac.diamond.sda.polling and

uk.ac.diamond.sda.polling.preferences packages, thus external plugins
can read and write preferency values. I am working on customization of dViewer, and I would like to set all kind of preferency values from source code (dViewer plugin).

If there is objection against exporting such packages (probably I will need some more in the future in other plugins), then we should discuss a method of accessing preferency values in one plugin from another plugin. I can imagine an always exported package in each plugin where necessary, named for example ....ExternalAccess, where the required methods in a class would be placed. Here for example a setDefaultDirectory method would set the required preference, and also react for the change. This is some extra work, but it is worth, increasing modularity and customization level. In addition it would be done per request, so should not cause a lot of work at once.