Features of the mql5 language, subtleties and tricks - page 329

New comment
 
Nikolai Semko #:

I doubt you can help. The versions are multiplying at every attempt to edit, but the code is not even sent for checking.
I wanted to publish a bible with jpg work, but it is really scary to work with such a glitchy resource.
Really, we should move to github, and publish links to github in CB at the first (only) publication.

In my opinion, it would be nice to change the system of publishing sources in CB, adding such choices:

  • specify a link to an existing repository (to MQL5 AlgoForge or GitHub)
  • automatically create a repository on MQL5 AlgoForge from the submitted files on behalf of this user and show a link to this repository in the publication.
  • The current option is to simply show a list of uploaded files in the publication.

The two new options automatically remove the problem with the lack of updating files in archives. But they require a bit more skill from other users. At least, they should be able to download the repository archive by following the link to it.

In principle, it is already possible to place all the code of the publication in a separate public MQL5 AlgoForge repository and provide a link to it in the description of the publication in CB. This should not violate any rules, as this repository is a MetaQuotes resource, and a link to it can be specified.

 
Yuriy Bykov #:

In my opinion, it would be a good idea to change the system of publishing sources in CB by adding such choices:

  • specify a link to an existing repository (on MQL5 AlgoForge or GitHub)
  • automatically create a repository on MQL5 AlgoForge from the submitted files on behalf of this user and show a link to this repository in the publication.
  • The current option is to simply show a list of uploaded files in the publication.

The two new options automatically remove the problem with the lack of updating files in archives. But they require a bit more skill from other users. At least, they should be able to download the repository archive by following the link to it.

In principle, it is already possible to place all the code of the publication in a separate public MQL5 AlgoForge repository and provide a link to it in the description of the publication in CB. This should not violate any rules, as this repository is a MetaQuotes resource, and a link to it can be specified.

This is a good idea. I also had the thought rolling around in my head for a long time that it would be cool to link the Codebase publication to the AlgoForge repo.

But then I looked at it from a different angle. I decided to treat the Codebase as a channel for the simplest possible distribution - so that it’s as easy as it can be for a non-programmer to download and install. So for Codebase publication, I built a special single-file version of the source code. And for programmers, I put a link to AlgoForge in the description of the Codebase publication, where the source code is split into .mqh files.

This logic makes sense, because I’ve had several cases where - despite the installation video I provided - someone took only the .mq5 file from the archive (ignoring the .mqh files) and asked me to fix the code, saying it doesn’t compile.

 
fxsaber #:

It would be possible to download all actual files from kodobase by one click (to a folder or archive). Now it has to be done manually many times, as here.

AI instead of MQ...

Another browser extension? It's not hard for me to generate.... But maybe it's easier to move to git finally?
 

Andrey Khatimlianskii #:
Еще одно браузерное расширение? Мне не сложно сгенерировать....

Yeah. Clicked and got it in the browser.

But maybe it's easier to move to git, finally?

I'm old, I guess. I couldn't do it.

 
Think it’s all good. Simple projects on CB and open source projects that are open for multiple developers for Algo Forge. Besides AI used the MQL5 Codebase to get good at MQL5 by the way. Any guy who can use the internet can easily navigate the Code ase.
 
fxsaber #:

Yeah. Clicked it and got it in the browser.

I'll generate it now, no problem.

 
fxsaber #:

Yeah. Clicked it and got it in the browser.

Done. Even drew a button for convenience (not me):


 
Andrey Khatimlianskii #:

Done. Even drew a button for convenience (not me):

The thing came out very handy, thank you very much!


There are two comments.

  1. In the name of some subfolders there is an underscore character.
  2. It would be clearer if the time of files in the archive coincided with the time of modification in kodobase.
 
fxsaber #:

  1. An underscore appears in the names of some subfolders.
  2. It would be clearer if the time of files in the archive coincided with the time of modification in codobase.

1. Standard practice to avoid problems with loading/saving in different operating systems. It's just the name of the archive, inside all the names are original

2. and it is not original? Doesn't correspond to the time of modification of a particular file? I think it is logical to store it, if there is one.

 
Andrey Khatimlianskii #:

1. Standard practice to avoid problems with downloading/saving in different operating systems. This is just the name of the archive, inside all names are original

2. Is it not original? Doesn't correspond to the time of modification of a particular file? It seems logical to me to store it exactly, if there is one.

  1. Inside the paths contain the underscore character.
  2. There time of all files is the time when the browser extension created the archive.
1...322323324325326327328329330331332
New comment