Discussion of article "How to Post a Product in the Market" - page 15
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
I see, thanks.
I suspect there's no point in suggesting that we expand the functionality of the Marketplace in favour of greater flexibility to address the issues raised.
What does "type" mean for a library if it is not an Expert Advisor, indicator or script, but a library?
It's bad that references to internal anchors in the description are killed - the text could be more convenient.
I'm trying to make a description of functions in the style of MQL documentation - references to CSS are removed, classes are removed.... Maybe there is a simple way? Maybe someone can give me a hint?
It's bad that references to internal anchors in the description are killed - the text could be more convenient.
I'm trying to make a description of functions in the style of MQL documentation - references to CSS are removed, classes are removed.... Maybe there is a simple way? Maybe someone can give me a hint?
Use css styles with the same names as in our documentation on the site.
Css file can be downloaded from the site, and style names can be found in the source page of the documentation.
Use css styles with the same names as in our documentation on the site.
You can download the css file from the site, and see the style names in the source of the documentation pages.
Thanks, but the style names are not saved. I copied from css and paste into span styles, only the colour is saved, but in general it already looks similar. After the first function went easier.
But for the future it would be good to think of something (visual editor is generally quite powerful).
I came across the fact that the description of my product exceeds the established limit of 3600 characters. Who came up with this stupid limitation? How can you describe a product in such a short form, if this product is more complicated than two moving averages and all kinds of black boxes in the style of "just run it and it will do everything by itself".It is required to describe in detail the principle of operation, features, assignments of all parameters, other nuances. It can't fit into 3600 characters. Or what should I do, abbreviate every word (dr. tr. pr.)?
In general, somehow it's all frivolous, I would even say petty. Yandex is giving away terrabytes for free use, and you squeeze on extra kilobytes of text, shrink the size of pictures to 640x480 and other restrictions, while getting a share from the sales of this product. I.e., it would seem that they should be interested in high-quality description. Or from saving on matches more profit is made?
The situation was aggravated by the fact that the system does not even let you save in the draft description that exceeds the limit. And as a result, switching to another tab and then back to "Description", I lost all the work I had done in a few hours (everything was already written and formatted properly). In general, so far only unpleasant impressions.
I came across the fact that the description of my product exceeds the established limit of 3600 characters. Who came up with this stupid limitation? How can you describe a product in such a short form, if this product is more complicated than two moving averages and all kinds of black boxes in the style of "just run it and it will do everything by itself".It is required to describe in detail the principle of operation, features, assignments of all parameters, other nuances. It can't fit into 3600 symbols. Or what should I do, abbreviate every word (dr. tr. pr.)?
Users have the sin of not reading long texts. So, giving them a big technical text as a blow to the head is not good for the product itself.
My product is not for such users. It is a purely technical thing, where a detailed description of all the nuances is required.
I realise that there are a lot of products where the whole description is reduced to cheerful exclamations and pink snot in the style of "it's very cool", "you won't regret trying it", etc. A few lines are really enough, because there is no point in looking at the rest (as well as the product itself). As they say, what product is, what description is.
Create full documentation and post it in the discussion of your product. What's the problem?
The product on display should come in a complete set, with documentation and other things. Not smeared somewhere on forum discussions. Imagine if the documentation for your MT was posted not in a specially designated place, but in some forum discussions.
What prevents you from making a separate tab "Documentation" for this purpose? Or give an opportunity to attach your PDF file with documentation. So that everything would look civilised: there is a product, there is documentation for it, which is in the "Documentation" section, and not in the "Flood" section as you suggest.