Google chrome web application (phase 2)

Problem statement: The financial market charting analysis platform, TradingView (TV) doesn't provide functionality for traders to automate their strategies. Solution: A third party application built with Google developer tools can retrieve alerts from TV then send these alerts to various brokers (such as Saxo Bank and Oanda) via an API. These messages then trigger trades on the brokers platform. Examples: There's 2 businesses which currently provide this exact functionality. Please conduct a quick google search of 'Autoview' and 'Alertatron' - this will give you an understanding of the requirement. A freelancer has already built most of the Google Chrome Web application, however they had to stop working on the project due to personal reasons. I'm now looking for a new Freelancer to help finish this off and the high possibility for regular ongoing work as my head developer. The steps needing to be completed are: 1. Understand the handover document from previous Freelancer (2 pages) 2. Understand what has been completed so far 3. Understand Saxo Banks open api (relatively easy to learn) (credentials can be provided) 4. Add a pine parser to parse the user message. Can be done at front end or by querying the python backend 5. Add some ajax code to make regular queries to the python backend to get the access token. 6. Update the status on the options page. a. Add some css/html to make the options page look good. b. Add some code to make the extension pop-up look good c. Syntax builder for pine orders. Steps completed thus far: -The python(flask) web app Runs on the backend which handles authentication from Saxo Bank. It is built to run on a digital ocean server. It accepts the request token from Saxo bank after successful login, uses it to get an access token, and then stores the obtained access token and refresh token. (please look at [login to view URL]). The tokens are stored in a mysql database with the following schema: -state VARCHAR (the identifier for which user just logged in) -token VARCHAR (the access token for the user) -refresh_token VARCHAR (the refresh token) -status VARCHAR (the status of the access token - valid, expired, null, etc) On successful auth, the web app stores the access/refresh tokens and then serves them to the Javascript front end(the chrome extension) when a request is made (http://{url}:5000/statequery?state={state}). For all effects and purposes, the state is the user id. Create a virtualenv and install requirements from a requirements file. -The javascript front end(chrome extension) The button on the extension pop-up takes you to the options page for login. The login for the Saxo Bank portal is already implemented in the options page. The user clicks the login button, signs in to Saxo and then authorises our python backend. Currently if an alert is set up on trading view, the user-specified message shows up on the [login to view URL] console(used Jquery to identify the message)