aboutsummaryrefslogtreecommitdiffstats
path: root/TODO
diff options
context:
space:
mode:
authorfishsoupisgood <github@madingley.org>2019-04-27 22:20:21 +0100
committerfishsoupisgood <github@madingley.org>2019-04-27 22:20:21 +0100
commitfd6bb20116127f6ac903d4b03abac72a49baa1ae (patch)
tree22e1e44fad2f844096f2d79bef9262112b45158c /TODO
downloaddatalink-fd6bb20116127f6ac903d4b03abac72a49baa1ae.tar.gz
datalink-fd6bb20116127f6ac903d4b03abac72a49baa1ae.tar.bz2
datalink-fd6bb20116127f6ac903d4b03abac72a49baa1ae.zip
fish
Diffstat (limited to 'TODO')
-rw-r--r--TODO23
1 files changed, 23 insertions, 0 deletions
diff --git a/TODO b/TODO
new file mode 100644
index 0000000..c91e44c
--- /dev/null
+++ b/TODO
@@ -0,0 +1,23 @@
+Document the Ironman protocol
+add options in the datafile parser to
+ -set the watch model
+ -set the order of phone entries
+ -set the spacing of the lines
+ -set all other options that can be specified on the commandline
+being able to abort a transfer while the screen is flashing would be nice
+
+figure out why just sending alarms will corrupt the phone entries
+(later entries like 17 or so)
+
+Mon Jan 22 22:38:50 CST 2001
+question from a user,
+I can't seem to move fast enough for me to put my watch in front of the
+screen before your program starts sending data to the watch...
+
+How about showing the initializing sequence (the many bars on the screen
+that makes DataLink go beeping while in COMM mode), then wait for a key
+to be pressed before actually sending the data?
+
+probably not a bad idea to show the sync signal until the user initiates
+the data mode, also possibly have an option for the time to wait while
+displaying the sync signal