Discussing the article: "Developing a Replay System (Part 40): Starting the second phase (I)"
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Check out the new article: Developing a Replay System (Part 40): Starting the second phase (I).
Today we'll talk about the new phase of the replay/simulator system. At this stage, the conversation will become truly interesting and quite rich in content. I strongly recommend that you read the article carefully and use the links provided in it. This will help you understand the content better.
In the previous article Developing a Replay System (Part 39): Paving the Path (III), we looked at how we could organize communication between processes to enable certain actions. At the moment we are using an EA and an indicator, but as necessary we will be able to expand these tools. The main advantage of this type of communication is that we can build our system in modules. You may not yet understand what we can really do. Ultimately, we will be able to exchange information between processes over a more "secure" channel than when using global terminal variables.
To implement this and show how to integrate our replay/simulator system into a modular system, let's take a step back and then a step forward. In this article, we will remove the study system that uses the EA mouse. We will convert the same system into an indicator so that it is compatible with the next step we will implement.
If we succeed, it will become clear that after this we can do much more. There is a high chance that the indicator will not end here, since we will need to do other things later, but eventually it will be completed. The big advantage is that we will be able to update or modify the module without affecting the rest of our main system.
Author: Daniel Jose