User-specific waypoints for inline/otrc configuration about quicksetup HOT 6 CLOSED

Also inline otrw would mean changing our android app which I'd like to avoid

from quicksetup.

or, we could split the waypoints from the config and add an .otrw and inline equivalent

from quicksetup.

Also a good idea, but I think it'll be easier for users to create a JSON array of waypoints -- syntax is a bit easier.

from quicksetup.

Also a good idea, but I think it'll be easier for users to create a JSON array of waypoints -- syntax is a bit easier.

The waypoints array in .otrc is the same as in an .otrw

from quicksetup.

which is wrapped into a dict with two additional elements:

{
  "waypoints" : [
    {
      "tst" : 1432817332,
      "lat" : 52.0,
      "lon" : 6.0,
      "rad" : 0,
      "desc" : "Main@WestWing"
    }
  ],
  "_type" : "waypoints"
}

We might support both:

• simple array of waypoints
• actual otrw files from which the list of waypoints is read

from quicksetup.

Ready for testing. Documentation here.

from quicksetup.