Discussing the article: "Developing a Replay System (Part 60): Playing the Service (I)"
Thank you for your time and great effort to explain everything, brother!
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 60): Playing the Service (I).
We have been working on just the indicators for a long time now, but now it's time to get the service working again and see how the chart is built based on the data provided. However, since the whole thing is not that simple, we will have to be attentive to understand what awaits us ahead.
In the previous article Developing a Replay System (Part 59): A New Future, I presented and explained some of the changes made to the control indicators and mouse indicator modules. Although those updates provide us with several future use possibilities, particularly for the mouse indicator module, it still contains a minor flaw. However, this flaw does not affect us at this stage. This is because, for now, our focus will be on addressing some remaining issues related to encapsulation within the replay/simulator service class code.
Although we have already made several adjustments, as discussed in previous articles, they were not sufficient to fully resolve the encapsulation issue. There are still elements leaking from within the classes, and we need to fix this immediately. Otherwise, it will lead to serious problems soon. In addition to addressing the encapsulation problem, which causes internal elements that should remain hidden the be accessible, we also need to refactor certain aspects of the code to ensure more appropriate access to some variables and information. All of this will be discussed in this article.
Demo video
Author: Daniel Jose