ianrenton / planesailing Goto Github PK

If the tab or PWA is returned to after a while, a lot of snail trail data will be missing because the app goes back to update calls, and never requests history for the gap in time for which it wasn't running.

The use of the "anticipated" symbol is really a job for the client based on its dead reckoning decisions and should be implemented there rather than in the server.

Pair of ianrenton/planesailing-server#24

Hi Ian,

I was also looking for a uncluttered frontend so I modified a script for an ESP8266 but it's not reliable.
Woudl it be a lot of work to include the baseblock from this picture? (The part that show "Type", Altitude, etc. etc.
Can you give me some pointers?

http://irishharvest.nl/Images/PlaneSpotter.jpg

Once HTTPS is set up and working properly on the server, the HTTP redirect code in the client can be removed.

Fixed tracks should still be shown as “Live” if their updates are very recent
New recentEnoughToShowLive method like the inverse of anticipated but no special logic for fixed or dead reckoned tracks

Having the server and client as separate projects works well for me but isn’t great for prospective users who just want to install something on a raspberry pi and have it work.

However GitHub Pages (currently used to host the client) won’t serve from any subdirectory apart from “docs” which means to continue working this way I’d have to host the static web content in “docs” (bit strange) or maybe work some git magic with another repository.

Hi Ian,

I was also looking for a uncluttered frontend so I modified a script for an ESP8266 but it's not reliable.
Woudl it be a lot of work to include the baseblock from this picture? (The part that show "Type", Altitude, etc. etc.
Can you give me some pointers?

http://irishharvest.nl/Images/PlaneSpotter.jpg