Development (UI)

• 1. Create a local MongoDB database with hypothetical and (reasonably) arbitrary stock transactions. "Columns" should contain: stock ticker (string), transaction type ("buy" or "sell" for now), number of shares (integer), date of transaction (date), price per share (float). Databases and IPC (interprocess communication) with the Python application will provide data for the front end.
     Sell dates should be after a buy of the same ticker. Price per share should be positive. Shares should be positive and whole numbers. Date/status: 2018-1-6/completed by Tyler.
• 2. Create a backend Express.js application (in ui/app.js) that runs on the default port and serves a page with text "Home" (no need for HTML for now). A sidebar, HTML/CSS formatting, and summary of the purpose of the UI will be added to the home page later. Submit changes to UI/app.js in a pull request when complete. Contact Tyler via Skype for questions about Express.js if necessary.
     Date/status: 2018-1-4/completed by Aswath.
• 3. Render a page with a table containing algorithm transactions extracted from the sample MongoDB database. The page will be rendered when a GET request is made for api/algorithms/sample/transactions.
     Date/status: 2018-1-6/Assigned to Aswath.
• 4. Create a mock socket application using socket.io under dev/mock/socket with main file dev/mock/socket/app.js. The application will listen for connections and messages on an arbritrary/default port. Write configuration files to build and deploy the application on Heroku. See notes about deploying from a repo subdirectory below (this may require some steps done by the repo owner). Either deploy on your own heroku account or ask Tyler to deploy it on his heroku account.
     References: https://coderwall.com/p/ssxp5q/heroku-deployment-without-the-app-being-at-the-repo-root-in-a-subfolder
     Date/status: 2018-1-6/created by Tyler.
• 5. Connect to a socket application on startup in ui/app.js using Socket.io. Accept -p and -i parameters on the command line for custom port and ip/hostname for the socket. See if there is an argparse module for this. Default port will be 4594 and default ip will be 127.0.0.1. Command line parameters -p and -i will be optional. If the socket application cannot be connected to, display an error message and exit the application with exit code 1. Test with the mock socket application deployed on heroku.
     Date/status: 2018-1-6/created by Tyler.
• 6. Add a help dialogue for command line option -h in ui/app.js. The help dialogue will display the purpose of the application and explain the usage and purpose of the -p and -i options.
     Date/status: 2018-1-6/created by Tyler.
• 7. Add mock data files for the heroku mock socket application. The files will contain data transmitted to the main application when socket requests are made.
     Date/status: 2018-1-6/ Assigned to Tyler.

Topics to learn about: Node.js MongoDB library, grunt, gulp, ejs, express.js, heroku, socket.io, argparse module?