Ticket #372 (closed task: fixed)
Opened 2011-03-14T13:31:52-05:00
Last modified 2011-09-12T15:06:38-05:00
Change location of preference keys
| Reported by: | bdezonia | Owned by: | bdezonia |
|---|---|---|---|
| Priority: | major | Milestone: |
|
| Component: | Core | Version: | |
| Severity: | serious | Keywords: | |
| Cc: | curtis | Blocked By: | |
| Blocking: |
Description
In order to get the Preference code working a class called SettingsKeys was created in the common imagej package. It holds the static final Strings that are used as key lookup indices for the Preferences.
To improve the design we will want to relocate these. Either we will have a common dialog for all settings (and thus the keys could live there), or we will have them aggregated into a dialog by sezpoz (and thus individual keys would live with their parent plugin) or lastly we could locate them all to the Preferences class as static constants.
Change History
comment:1 Changed 2011-03-14T14:26:52-05:00 by bdezonia
comment:2 Changed 2011-03-23T12:13:49-05:00 by bdezonia
- Milestone changed from imagej-2.0-alpha1 to imagej-2.0-beta1
comment:4 Changed 2011-09-12T15:06:10-05:00 by bdezonia
- Status changed from new to closed
- Resolution set to fixed
Removed SettingsKeys completely in 0c803bfcb23b34910d2221e1e7192b5c0e6a2761. Preferences are now stored from an OptionsPlugin using it's own classname and fieldnames to persist values.
comment:5 Changed 2011-09-12T15:06:38-05:00 by bdezonia
- Milestone changed from imagej-2.0-beta1 to imagej-2.0-alpha5
leaning towards see
Currently leaning towards 2nd approach (sezpoz harvesting). See #366 for more information.