Let's discuss joint projects in the editor - why and where they are going - page 12

 
Artyom Trishkin:

Set the compilation language and substitute the required messages accordingly.


can you give me an example ?

 
Vladimir Pastushak:

can i have an example ?

Through the defines, look in the documentation, there is an example

 
Vitaly Muzichenko:

Through the defines, look at the documentation, there is an example


I know the documentation well, that's why I'm asking here, and I'm asking because by setting properties of the program in the project we get a big inconvenience in development of really big projects...

 
Renat Fatkhullin:
The publication of new products with the full package of descriptions, pictures and the logo will be from the project. The publication of the new version is similar.

The project is needed because the product is not just an ex4/ex5 file. There is also a list of default *.set files, so that traders can quickly understand what settings are recommended.

Automated checks will be introduced gradually, so that the developer can quickly see the modes to be tested in order to reduce the traders' problems.

The support of other languages and integration will be introduced gradually. The goal is to run the main projects directly in MetaEditor. Essentially we are following the way of aggregation, as in Visual Studio.




I think it is a right way. We do not have to re-invent the wheel where everything has been already tried out by millions of programmers with such a monster. The main thing is to correctly distribute forces and resources in the direction of the main stroke.

And do not listen to "desires" from those who have never written anything except an EA on two muwings )))
Good luck to you and MQ!

 
Vladimir Pastushak:

I know the documentation well, that's why I'm asking here, and I'm asking because setting program properties in the project is a big inconvenience when developing really big projects...

The main description (in the launch window) is in English, for everyone. And detailed and localized - in any convenient form after launch, depending on TERMINAL_LANGUAGE.

 
Andrey Khatimlianskii:

Main description (in startup window) is in English, for all. And detailed and localised - in any convenient form after launching, depending on TERMINAL_LANGUAGE.


and advisor settings?

 
Vladimir Pastushak:

what are the settings for the advisor?

The basic (brief) is in English.

If a lazy Russian (or Spaniard, Ukrainian, ...) needs to understand it, there is a helpline.
But what should happen to make it difficult to understand, for example, "Min distance" or "Bars number"?

 
Andrey Khatimlianskii:

The basic (short) is inlish.

If you have to spell it out for lazy Russian (or Spanish, Ukrainian, ...) - the helper panel.
But what should happen to make it difficult to understand, for example, "Min distance" or "Bars number"?


Andrei, it is not hard to understand, but it is competent and correct to write it in the user language. It increases the quality of programmes...

You probably work on russian-language Windows/linux?

 
Vladimir Pastushak:

Andrei, it's not hard to understand, but to write competently and correctly in the user language. It increases the quality of programmes...

You probably work on russian-language Windows/Linux?

The answer has already been given. Through a compilation language define. Things that must have several languages - settings for example - are written for each language.
Then #ifdef is your help.
 
If "insert mqh" is used in ME, then let the selection open INTO the sandbox.