@@ -32,9 +32,17 @@ When the user takes an action, there should be immediate feedback, even it's jus
We'll use a view-model-controller system that serializes user actions into a queue handled by another thread, so that the UI thread can at least does not freeze.
## Error conditions should be obvious and clear.
## The view should be reflective of the model
## The interface should not punish the user.
### The user should be able to undo actions
### External / automated actions should never automatically destroyed configurations set by the user.
# Automatic Constraints Checking.
\ No newline at end of file
## Transformations are views of measured data.
Measured data is essentially always a time history. Common calculations such as PSD, transfer functions etc. Should be treated as views of the measured data and not new datasets off themselves, even if they are cached in memory and saved to file.
Persistent representations of these views are purely practical. The user can of course export these views on their own as a distinct data set.
