| | 62 | The idea is that a preference set consists of |
| | 63 | |
| | 64 | * A single set of static prefs |
| | 65 | * One or more configurations; |
| | 66 | e.g. a config for "in use" and another config for "not in use". |
| | 67 | Or a config for time/day in a certain range, and another config |
| | 68 | for outside of that range. |
| | 69 | |
| | 70 | This raises a question: if we allow config selection |
| | 71 | based on both in-use and time-of-day, |
| | 72 | which one has precedence? |
| | 73 | My inclination is to allow selection either by in-use |
| | 74 | or time-of-day, but not both. |
| | 75 | |
| | 76 | == Time of day specification == |
| | 77 | |
| | 78 | We may as well generalize time-of-day spec |
| | 79 | to allow selection on a per-hour basis, rather than contiguous periods. |
| | 80 | |
| | 81 | == Custom prefs: summary == |
| | 82 | |
| | 83 | If the user selects Custom, the editing GUI shows: |
| | 84 | * the static prefs |
| | 85 | * a radio button selection of |
| | 86 | * same prefs all the time |
| | 87 | * if selected, a single set of dynamic prefs |
| | 88 | * different prefs depending on time of day/week |
| | 89 | * if selected, a time-of-day selection interface, |
| | 90 | and two sets of dynamic prefs |
| | 91 | * different prefs depending on whether computer is in use |
| | 92 | * if selected, two sets of dynamic prefs |
