Skip to content

Meeting 2017 11 23 Backend

Kai Xu edited this page Nov 23, 2017 · 4 revisions

Participants

Present: Shaz, Kai, Reday

Agenda (to discuss)

Progress update

Action Points from last meeting

Shaz

  • Only need one function to generate a new key for an email address. No need to have previous key when a user logged in again.
  • Research how to trigger R script remotely, so we don't have to manually run the code every time.

Reday

  • Move the login functions to the background page browser action. Run login when user click the SenseMap button. Once logged in, call background.js to start historymap.
  • Update save/load to use the session key generated by the API;
  • Load the list of saved sessions in history map once user logged in.

Kai

  • Change SenseMap icon colour.

Discussion Points

Reday

  • Question someone to demonstrate chrome.runtime message passing (This is not required but I may be able to replace localstorage with events)
  • Question regarding current code Logic (not crucial but might help me write better code)
  • Question in regards of how NODE[] works and how nodes get added so I can finish save and load

Action Points

Reday

  • Move the login code to a separate js file and load it with background.js.
  • Automatically start history map once user logged in.
  • When history map starts, show the option to load a old session or create a new one.
  • Get the new node saving working.

Shaz

  • Local (batch) script on the server that runs the R script, or
  • Remote (batch) script to run the R script on the server
Clone this wiki locally