Keyhole¶ ↑

Move along, there’s nothing to see here yet.

Priority ToDo¶ ↑

Adding time-coded comments
Meditate on where to do the actual hotzone-matching takes place (in the database? in event-machine? client-side?)[Client-side looks good, but what about alarms?]
hotzones/triggered zones with alarms/notifications (email, push notification, sms)
should not be dependent on jquery - it is WAY too large (this is halfway-done, jquery is just used for element-fetching now, not any heavy stuff)
Administrator-notifications when things have gone wrong
Read port-configuration and the like from both commandline and config-file, dependent on environment [This should be a config-file, to support monit]
export data [download as csv or something]
time-slider (fly through time in an efficient manner) [low-prio]
lookup (what was the state at XX hours) [interesting, but low-prio]
flag point in time as relevant with note
Think about a better overview-GUI

Adding support for displaying KML-files from the backend
Better GUI in map (remove groups for now, support for turning tracking on/off)
Investigate re-connect possibilities on both WebSocket and Tracker ends
Support for setting the color of trackers
More robustness (not crashing when not finding imei, when channel doesn’t exist)
Better notifications
Support multiple markers on the map
Share global state for the database, to prevent per-row locking
Support multiple separate sessions of trackers (i.e. webservice-setup)
Formalize the protocol for GUI–>Socket communication
Clean up the database-connections, make sure the app can share one connection instead of setting up a new one per client
se device-status (on,off,nofix,latest update)
lägga till/ta bort/administrera devices
ändra/fixa visualisering av devices (färg,symbol,grupperingar)
Investigate if possible to send commands back to tracker to change reporting period [It should, this should just be a config issue]