Target release	2.0
Epic	SNAP-47 - Getting issue details... STATUS
Document status	DRAFT
Document owner	Thomas Storm
Designer
Developers
QA

Goals

Find a specification for a way to deal with the user preferences in SNAP.

User interaction and design

We will need to clarify how to best present the user preferences to the user. The NetBeans preferences window is the natural choice for that, but still it needs to be discussed which items are migrated from BEAM VISAT, which items shall newly be introduced, and which items already offered by NetBeans shall be dropped.

Suggestion for migration from BEAM VISAT:

Move UI Behavior to new tab under Appearance
The preferences under the BEAM UI Appearence tab is already covered by Appearance->Look and Feel and Miscelleaneous->Output in NetBeans, so no action required
Module Repository: TBD if needed; anyway, Proxy settings can be set in General-tab offered by NetBeans already
Merge Product Settings and Geo-location Display (considering that the product settings only handle a single geo-location-related setting), put under tab Geo-location under Miscelleaneous
Data Input/Output: move to new tab under Miscellaneous; since there are actually only output-related settings, name that tab Write Options
Add new primary panel Layer Properties that reflects Layer Properties list in VISAT preferences; name the first sub-tab General
Move RGB-Image Profiles to new tab
Move Logging to new tab

How-to

See Preferences System Migration.

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome
Since module handling in NetBeans will be different from how it is done in BEAM: do we still need offer the user the possibility to specify the module repository URL?
The log-level property in VISAT is read-only. Shall it be kept like that?
The behavior is a bit strange: when I select "Log extra debugging information", the log level changes to "DEBUG"; when I unselect it, the log level changes to "INFO", no matter what the original value was. I guess that is a bug.
Is the suggestion acceptable?

Browser not supported