darkeclipz / cryptowatch Goto Github PK

There are not enough periods to calculate the 10 & 20 SMA. Due to this they start half way in the daily graph.

Calculate the required period to give as parameter to the Polo API. This way we don't collect any more data than we need.

Useful when we do buy/sell orders and stuff.

Cancel an open order on Polo.

The scanner just updates the last 5 records in the database (assuming that those are the last 5 candles of each chart), ordered descending by date.

Sometimes a chart is not loaded yet (so it will overwrite a second last from another chart, or more). Or when a chart has not updated for days it will still update that last value.

Suggested solution: update the last candle close from the last on the scanner for only that datetime?

Display current balances.

When a chart is updated, the timer is stopped. After the update the timer is somehow not restarted, although the code is present.

Without stopping/starting it works, but due to very low response time from Poloniex it keeps refreshing the chart with an old symbol because the multiple tasks are still waiting for the HTTP request.

Implement the settings within the application.

• Chart settings
• API settings
• Data settings

View all open orders on Polo.

The left and right most candles are only displayed half on the chart.

Show the order book for the selected symbol.

See title.

Close an open position. Save the metrics.

These metrics can be collected from SQL server with Excel. Make a dashboard in Excel?

Handle all the HTTP requests in a centralised way with a queue. Polo only accepts max. 6 requests per second. This needs to be buffered.

Implement a way to update all the data in the application when a request has been completed. Has too be reliable (retry policy) because Polo's API is not.

Open a trading position.

It should track metrics such as %P/L, targets, stop, etc...

Create a histogram for the order book. No idea where too place this yet.

Too much data...