Yesterday evening I started to think about a possible architecture of an open and flexible Multipair EA Shell.
After a stable version is reached, everything except the strategy lib should be subject to very few changes. The architecture I’m showing in my draft follows the idea that usually all libs should communicate with the system kernel through a defined interface. Obvious exceptions are error handling and logging, which should be accessible from all other modules. A possible exception is Money Management Lib, which could be accessed by Trading Lib directly.
My goal would be a future proof high quality Multipair EA Shell, which is open, adaptable, and flexible. Intended language is MQ4 only for the moment.
Would be very interested to hear your opinion. Does that make sense? Something missing? Different concepts for a software architecture around? Complete nonsense because there are enough multipair EAs around to tweak?
simplex
Creating a Multipair EA Shell
-
simplex
- Trader
- Posts: 127
- Joined: Thu Feb 07, 2013 5:21 pm
- Location: An insignificant small town close to an insignificant former capital at the Rhine River.
Creating a Multipair EA Shell
You do not have the required permissions to view the files attached to this post.
If you can't explain it simply, you don't understand it well enough. (Albert Einstein)
It appears that the Weighted Moving Average was invented by a trader who did not have a firm grasp of filter theory in hopes of reducing lag. (John F. Ehlers)
It appears that the Weighted Moving Average was invented by a trader who did not have a firm grasp of filter theory in hopes of reducing lag. (John F. Ehlers)