Discussion of article "Order Strategies. Multi-Purpose Expert Advisor" - page 2

 

I thought.... :)

ok. of course it is a pity that you did not emphasise in the article two features that I see for myself

1. ex5 expert - knows and knows how to process all macros. it is enough for it to feed different txt files for work.
2. macro parameters can be adjusted "on the fly" in the txt file.

Otherwise, all this is nothing but a usual library of functions for working with orders and positions. It's just that you decided to call them from the outside, parse the txt and identify the necessary macros.
but honestly I don't even know who will use it. For a beginner there is a lot of code, for a pro there are few possibilities.

Dmitriy, it is necessary to put it in the visual constructor to have a wizard.
And the second thing you need (if you don't want to throw this development away) is more examples of strategies. So that they were transparent and it was visible what parameters of macros affect what.
Load a dozen strategies into the codebase. But make sure they are simple and with constant explanation of all parameters.
So that this approach is clear and they start to use it (and maybe even develop the number of macros, opensource :).

 
sergeev:

I thought.... :)

ok. of course it is a pity that you did not emphasise in the article two features that I see for myself

1. ex5 expert - knows and knows how to process all macros. it is enough for it to feed different txt files for work.
2. macro parameters can be adjusted "on the fly" in the txt file.

Otherwise, all this is nothing but a usual library of functions for working with orders and positions. It's just that you decided to call them from the outside, parse the txt and identify the necessary macros.
but honestly I don't even know who will use it. For a beginner there is a lot of code, for a pro there are few possibilities.

Dmitriy, it is necessary to put it in the visual constructor to have a wizard.
And the second thing you need (if you don't want to throw this development away) is more examples of strategies. So that they were transparent and it was visible what parameters of macros affect what.
Load a dozen strategies into the codebase. But make sure they are simple and with constant explanation of all parameters.
So that this approach is clear and they start to use it (and maybe even develop the number of macros, opensource :).

+100500
 
Dmitry, great article! I have learnt a lot of useful things from it
 

Dimitri, thank you for the article. Very interesting!

Если бы губы Никанора Ивановича да приставить к носу Ивана Кузьмича, да взять сколько-нибудь развязности, какая у Балтазара Балтазарыча, да, пожалуй, прибавить к этому еще дородности Ивана Павловича...

If I could combine your material with the format presented in sergeev's article Prototype of a trading robot....

By the way, isn't it possible to code all strategies (in your case strategies that actively use pending orders) using powerful OOP tools? It seems that creating a separate meta-language is some complication of the current task...

 
denkir:

Dimitri, thank you for the article. Very interesting!

1. Here's if we could combine your material with the format presented in sergeev'a Prototype trading robot article...

2. By the way, isn't it possible to code all strategies (in your case strategies that actively use pending orders) using powerful OOP tools? It seems that creating a separate meta-language is some complication of the current task...

1. It's kind of already combined, at least it doesn't contradict. Or is it unclear what can be combined there, and whether it is necessary?

2. This is a question like, why do we need any programming languages at all, if everything can be coded in assembly language.

I don't pretend that this is something so universal, designed to replace everything else. It's just an attempt to formalise it, as it seems to me quite successful, or at least a hint that it is fomalizable.

 
Integer:

1. It seems to be already combined, at least not contradictory. Or is it unclear what can be combined there, and whether it is necessary?

2. This is a question like, why do we need any programming languages at all, if everything can be coded in assembly language.

I don't pretend that this is something so universal, designed to replace everything else. It's just an attempt of formalisation, as it seems to me quite successful, or at least a hint that it is fomalizable.

Dima, don't listen to anyone.

// I mean, listen to me! :-) :-) :-)

You are obviously not being dragged (tried to be dragged) by the whole crowd. They are trying to shame you with insufficient connection with the practice of building trading systems. I would have sent you a long time ago, but you are still tolerating it, and you are still embarrassed.

I take the article exactly the opposite way - it demonstrates and well-documented an excellent example of a state machine written in mql5 (!) - the very finite automaton, which a certain comrade recently tried to promote as a novelty. And we should discuss the advantages and disadvantages of your implementation from these theoretical positions. All "closer-to-trading" (c) variants of discussion are children's babble in an adult sandbox. Where are the mighty theorists who were immense in that critical discussion? Where is the applause for the real realiser? Where is the discussion of this design as a "state machine"?

:)

 
And immediately in an applied form.
[Deleted]  

Dmitry, great article, thank you very much!

Personally, I liked the idea of using phases and position IDs, as it allows you to organise any money management system in a very flexible way.

But in general, I did NOT like the idea with one Expert Advisor and txt files. A wish would be to design everything as a separate class mqh include file, without any additional txt files. And also write an example of an Expert Advisor with this class, ideally, take a standard MACD Expert Advisor from the terminal, and show everyone how easy it is to "implement" your position management system in any Expert Advisor!!!! Write a second article, it is worth it....

 

Alex5757000:

I personally like the idea of using phases and position IDs, as it allows you to organise any money management system in a very flexible way.

yes. and it is very surprising that not many people use it.


But in general, I did NOT like the idea of one expert and txt files. A wish would be to design everything as a separate class mqh include file, without any additional txt files. And also write an example of an Expert Advisor with this class, ideally, take a standard MACD Expert Advisor from the terminal, and show everyone how easy it is to "implement" your position management system in any Expert Advisor!!!! Write a second article, it's worth it...

I guess you will now be able to perceive the fundamental information that is described in the Prototype of a trading robot...
[Deleted]  
sergeev:

yes. and it's surprising how few people are using it.

perhaps you can now grasp the underlying information that is described in Prototype Trading Robot....

I get it. The point is that from my point of view, such things should be laid out in the form of ready-made libraries, designed as a class. Otherwise, a number of inconveniences appear when integrating with ready-made Expert Advisors. Using external .txt files is a bad idea in principle.