| 1 | = Alarm lists = |
| 2 | |
| 3 | == Idea == |
| 4 | I asked myself a couple questions: |
| 5 | |
| 6 | * do the alarms need to be bound to POI after all ? |
| 7 | * how to easily add an alarm without making a POI ? |
| 8 | * how to make it easy for users to add many alarms at once (eq. with a script that generates them from a list of speed-limits/whatever) ? |
| 9 | |
| 10 | == Result: Plain-text alarm lists ! == |
| 11 | The alarms would be just stored in one or more plain-text files, one alarm per row with CSV notation. |
| 12 | |
| 13 | Row notation might look like this: |
| 14 | {{{ |
| 15 | lat;lon;elev;distance;enabled;name;alert |
| 16 | }}} |
| 17 | |
| 18 | {{{ |
| 19 | 51.178844,-1.826189;230;200;1;Stonehenge;Watch for the stones ! |
| 20 | }}} |
| 21 | |
| 22 | === Explanation: === |
| 23 | '''lat''' - latitude in decimal format[[br]] |
| 24 | '''lon''' - longitude in decimal format[[br]] |
| 25 | '''distance''' - trigger distance[[br]] |
| 26 | '''enabled''' - 1 = enabled, 0 = disabled[[br]] |
| 27 | '''name''' - displayed name[[br]] |
| 28 | '''alert''' - any string other than BEEP or SAY would go directly to text-to-speech, BEEP triggers some default alarm sound, SAY: says whats after the colon (so you can SAY:BEEP :D)[[br]] |
| 29 | |
| 30 | === What about elevation ? === |
| 31 | If you don't want the alarm to take the elevation into account - just don't fill it in. :) |
| 32 | |
| 33 | Example: |
| 34 | |
| 35 | {{{ |
| 36 | 51.178844,-1.826189;;200;1;Stonehenge;Watch for the stones ! |
| 37 | }}} |
| 38 | |
| 39 | === How to add new alarms ? === |
| 40 | There would be two ways: editing the alarm lists from the outside (just create a valid list and modRana will be able to use it) or interactively inside modRana (create new lists, add alarms from map/poi/coordinates, enabled/disable alarms, activate/deactivate alarm lists). |
| 41 | |
| 42 | == Implementation progress == |
| 43 | Not yet started. :) |