Update Programmer's FAQ

Programmer's-FAQ.md

@@ -1,3 +1,12 @@
+**Obsolete**
+
+For the most up to date information, please visit [https://wfview.org/wfview-user-manual/](https://wfview.org/wfview-user-manual/)
+
+---
+**OLD INFORMATION**
+---
+
+
 For installation directions, please see [INSTALL.md](https://gitlab.com/eliggett/wfview/-/blob/master/INSTALL.md) in [the repo](https://gitlab.com/eliggett/wfview/-/tree/master). 
 
 **What language is wfview coded in?**
@@ -29,4 +38,4 @@ I tried! But basically, every existing library I found was not designed to work
 wfview makes a pseudo terminal device using the comm-handler. This happens when the program starts. The pseudo term is generally something like /dev/pts/0, but the number can change if another program is making pseudo terms. wfview always tells you the device number in the console output. (Note, wfview automatically symmlinks the psudo term to /tmp/rig on startup). Within comm-handler, it is easy to discern if incoming traffic is intended for the pseudo term device or to wfview (each packet has a TO and FROM clearly indicated). However, we cheat a little here -- all packets received get parsed into wfview, because, why not. Any packet from the pseudo terminal client gets sent to the serial port. To make this work, first configure flrig to connect to the pseudo terminal device, and then launch fldigi and tell it to use flrig for the radio interface. In practice this works pretty well except for the following issues:
 1. Most if not all client programs will reject device names like /dev/pts/0. Thus I have to write them into the preference files (~/.flrig/IC-7300.prefs) and be careful not to touch those 
 2. On the Raspberry Pi, last I checked, it seemed like sometimes client programs couldn't latch to the pseudo terminal device reliably. More work to be done there. Fortunately, fldigi isn't that great on a pi... 
-3. There is an issue where, if the client program is closed, the pseudo term remains locked or something, and new programs can't attach. If you know how to fix this, please tell me! 
+3. There is an issue where, if the client program is closed, the pseudo term remains locked or something, and new programs can't attach. If you know how to fix this, please tell me!