= Alarm lists = == Idea == I asked myself a couple questions: * do the alarms need to be bound to POI after all ? * how to easily add an alarm without making a POI ? * 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) ? == Result: Plain-text alarm lists ! == The alarms would be just stored in one or more plain-text files, one alarm per row with CSV notation. Row notation might look like this: {{{ lat;lon;elev;distance;enabled;name;alert }}} {{{ 51.178844,-1.826189;230;200;1;Stonehenge;Watch for the stones ! }}} === Explanation: === '''lat''' - latitude in decimal format[[br]] '''lon''' - longitude in decimal format[[br]] '''distance''' - trigger distance[[br]] '''enabled''' - 1 = enabled, 0 = disabled[[br]] '''name''' - displayed name[[br]] '''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]] === What about elevation ? === If you don't want the alarm to take the elevation into account - just don't fill it in. :) Example: {{{ 51.178844,-1.826189;;200;1;Stonehenge;Watch for the stones ! }}} === How to add new alarms ? === 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). == Implementation progress == Not yet started. :)