Remove proposal that test clients do PCMCIA-like beep codes on status changes.

I had this described as an easy first project, but it turned out to be
nothing of the sort.  The short version is that generating beeps is
surprisingly hard to do in a way that is robust and portable. Support
for beep() is flaky in xterm, and even when it is supported there's no
way to do beeps of varying pitch. X-based clients would have to drag
in a boatload of fragile sound support for this one operation. The
result would be a support mess.  If third-party clients want this,
they can code it themselves.

1 files changed, 0 insertions, 22 deletions

diff --git a/TODO b/TODO
index 62f575ea..ad7c8ef0 100644
--- a/TODO
+++ b/TODO
@@ -158,28 +158,6 @@ AsteRx and PolaRx, NovAtel Superstar2 and OEMV, Thales (Magellan
 Professional) AC12 and DG14 would all be welcome. Of course, these
 are not $50 USB mice...
 
-*** Audio cues in the client when the fix status changes
-
-Calum writes:
->Is it possible to add functionality (with a switch to enable it to
->avoid annoying those that don't want it) so that beeps indicate NO
->FIX, FIX, and OFFLINE status changes?
->
->For example - I run cgps and my laptop battery doesn't always supply
->my PS2 port-powered GPS device with enough power, and it goes into
->OFFLINE mode. As I can't drive, and check my laptop all the time, if
->it emitted 5 1 second beeps when it went OFFLINE, it would be a handy alert.
->
->Similarly, a PCMCIA "eject" 2 beeps for NO FIX, and a PCMCIA "happy" 2
->beeps when it gets a fix again?
->
->Or something like that.
-
-This is a good idea for supporting hands-free operation, e.g. while driving.
-
-It would be an easy first project for somebody who wants to get into
-the client code.
-
 *** Set the system time zone from latitude/longitude
 
 If we're going to give gpsd the capability to set system time via