events for - updating streams, receiving something on socket, gui events, error events, etc… https://github.com/stuartsierra/cljque/]]
Indicaator data shouldnt change, ask/bid rate, spread shouldnt change when ea is executing once. Or we should have the option for it not to change, anyways (pause/unpause also needed for repl environment). Also, it should access the latest available data, but only indirectly through a background update thread. That way, if the internet or socket is down, no errors will be thrown unless the user attempts to do something which requires the socket, like getting new data streams, placing orders, etc.
Eas need : (1) Signal source (i.e. run every tick, etc) (2) Ability to refresh rates (constant environment) (3) Own special environment - (market-orders returns orders that the ea made, etc.) (4) Mutable vars Creating an ea should be a simple matter of - ‘specify a function ‘x’ which will run every event ‘e’
Architecture which allows access to multiple accounts, multiple data streams, etc. Should be able to mix and match
Maybe we want data from socket X but want to place orders using interface Y. Think on this ....
New time frames, offset time frames, and price stream time data should be able to be created. (renko chart also??) Also what would be nice is to somehow combine a database of price data - somehow merge that with the idea of updating persistent vectors and the shorthand notation for accessing indicators.