kapusta / pzgps Goto Github PK

Add fixed bottom nav
another way to do it

WAY TOO BIG

When running npm run lint the following error is thrown wherever an es6 class method uses a fat arrow (which is desired syntax for the binding)...

error Parsing error: Unexpected token =

Useful Docs

• preact site
• switching to Preact
• preact-compat

Todo

• use preact boilerplate
• use preact-router
• investigate decko
• port index.js and App.js from the reactjs FE

• follow the pattern in the GpsData component
• add a staticmap using a consumer key if it exists
• only show the MapQuest button if the key exists
• the map should update if the gpsData changes

If the websocket dies, the reconnection attempt errors out and shows an undefined value

Use lite-server instead of live-server for local path installation in the angular1 package

https://github.com/johnpapa/lite-server

Goal is to connect to the pizero as a wifi hotspot and have the pzgps-server running too. Here's the adafruit guide.

• back up the SD card
• set up the pizero as an AP
• update packages/pzgps-preact/src/lib/conf.js to match wifi address
• write docs in pzgps-server readme explaining the process of connecting

• goog guide
• SmashingMag guide]
• upstream pr

Things to do...

• add manifest.json
• add service worker
• add icons for the install

Things to understand...

• offline-plugin
• copy-webpack-plugin
• preact-boilerplate/blob/master/src/index.js

• Move Database things to a component
• Make a db.js file and abstract indexes and such out to there
• Get most db stuff out of src/components/RouteEditor/RouteEditor.jsx
• Find a proper home for src/components/App/Db.jsx
• query the routes end point for routes instead of using allDocs()

Couch/Pouch install docs

• add feature/couchdb branch
• make a routes table, post some data into it

Questions...

• POST directly from the FE?
• send a ws frame and have that POST data into couch?
• send data somewhere after that?
• how to share that data?

• learn
• break up the components into paths (reuse App?)
• support WebSocket reuse like in the angular1 FE

Killing the socket on $destroy isn't necessary. Consider moving the connection to the WS server to the boostrapping phase in pzgps.js in a run() block.

Follow the instructions in the readme using this version...

https://nodejs.org/dist/v6.9.0/node-v6.9.0-linux-armv6l.tar.xz

Implement bluetooth connectivity

• wiki
• medium article
• Chrome code samples
• Community Group Code Samples
• adafruit bluez install guide
• lifehacker article
• bluetoothctl for node

• Fix version values in the package.json in each FE
• set up directory structure how lerna wants it structured
• use --independant mode
• document the usage of lerna in README.md

On TPV events, if distance from previous location is greater than n meters, record the new location in a Realm. Provide access to that data from the FE.

• Learn
• API Docs

• Create /lib/realmApi.js and add getter and setter
• Create /lib/realmSchema.js and define a location object
• Add UI to initiate a save of a location, with a user defined note

Needs....

• Basic app structure/outline
• Boostrap 4 css
• websocket component
• connect back end data to front end and render as an unordered list
• add mapquest component that consumes the gpsData and consumerKey

New frames come in, the data is put into the component with setState which causes the entire app to recompile/run/mount/etc, consider moving that out of a setState call

Look into using haversine to calculate distance between the current location and either a previous location, or a destination.

Current HEAD on feature/preat-pwa scores 62 on lighthouse against the webpack dev build, improve that score.

• test against prod build
• get https working on the pizero (letsencrypt and apache or ws/ssl)

• Make a small ng1 app
• figure out file/dir structure that makes sense for FE and BE
• npm install angular-websocket --save
• Add live-server support - live-server --entry-file=index.html