Discussion of article "Multicurrency monitoring of trading signals (Part 1): Developing the application structure"

New comment
 

New article Multicurrency monitoring of trading signals (Part 1): Developing the application structure has been published:

In this article, we will discuss the idea of creating a multicurrency monitor of trading signals and will develop a future application structure along with its prototype, as well as create its framework for further operation. The article presents a step-by-step creation of a flexible multicurrency application which will enable the generation of trading signals and which will assist traders in finding the desired signals.

Even during manual trading, the trader follows a certain operation algorithm and a sequence of actions, which can be presented as five main tasks:

  • Define a trading signal.
  • Define market entry rules and entry type.
  • Manage open positions.
  • Define market exit signals.
  • Define market exit rules.

In manual trading, each of these tasks implies trader interaction both with the terminal (opening, closing and managing positions) and with the trading system (finding signals in the relevant markets using certain technical means). All these actions may take much time, and they also require from the trader to be attentive, focused and disciplined. The purpose of this series of articles is to relieve load on traders who execute operations manually. Let us create step-by-step a convenient flexible multicurrency application which will enable the generation of trading signals and which will assist traders in finding the desired signals.

Author: Alexander Fedosov

 

The idea is good. It will be extremely interesting to see the implementation of the code when monitoring more than 500 assets on a one-time basis. For example, there are extremely strict selection conditions, there is a trading account with more than 4000 assets.

I select the traded assets, I get 500 potential assets. From them I need to select those that meet my conditions (a stock screener, basically). But the conditions are such that they cannot be written in the standard constructor. But it's a small thing. The most interesting thing is how you plan to do monitoring and how it can cope with a large number of assets.

 
Thanks for the article! Fix the hyperlinks in the content by text, they take you to another article.
 
Corrected, thanks for posting
 
firsalex:

The idea is good. It will be extremely interesting to see the implementation of the code when monitoring more than 500 assets on a one-time basis. For example, there are extremely strict selection conditions, there is a trading account with more than 4000 assets.

I select the traded assets, I get 500 potential assets. From them I need to select those that meet my conditions (a stock screener, basically). But the conditions are such that they cannot be written in the standard constructor. But it's a small thing. The most interesting thing is how you plan to do monitoring and how it will cope with a large number of assets.

Thank you. Monitoring of trading signals implies, as stated in the article, independent selection of assets and working timeframes. And on the selected list the specified signals are searched for.
 
MetaQuotes:

New article Multicurrency monitoring of trading signals (Part 1): Developing the application structure has been published:

Author: Alexander Fedosov

HI,
i have copied
Signal Monitor under Experts folder
EasyAndFastGUI under Include folder
EasyAndFastGUI under Image folder

But compile give me a lots of error: what is wrong?

The error concern
Objects
ElementBase
Element
Button
ButtonsGroup
Scolls
TimeCounter
TextBox

 
Federico Pompili:

HI,
i have copied
Signal Monitor under Experts folder
EasyAndFastGUI under Include folder
EasyAndFastGUI under Image folder

But compile give me a lots of error: what is wrong?

The error concern
Objects
ElementBase
Element
Button
ButtonsGroup
Scolls
TimeCounter
TextBox

As written in the article, this is just the markup of the future application. The next article will be the first result. Wait for publications.

 

In the future it will be released:


 
I'm developing the same application. But I came across some limitations of the standard library, which will take me more time to correct the limitations or get to know other libraries shared by friends. Thanks for sharing your implementation. Maybe I don't need to spend time developing this, as it seems to me that you are going in the direction I was designing. Thank you.
New comment