Making fxDreema better
-
fxDreema is a wonderful tool. But lack of good documentation or more complete help messages is a huge waste of hours and hours of time.
Is there any way to fix this?
The ability to test on MT5 and trade on MT4 is stellar. But so much is not well described, defined or explained. Too much time spent testing fxDreema when we should be testing our strategies built with it.
Thanks,
Richard -
Yes, fxdreema has a learning curve, as it is that versatile a tool. But once you get used to it, it is actually pretty intuitive and uses the basic logic of all coding languages.
This forum has very good chance of giving you answer to any problem, using the search function. What would you suggest to improve, for example? -
What is the information that you are missing?
Lately I rewrote the documentation actually. When I write there, I'm trying to write as less words as possible, and in the same time to cover maximum material. If there is too much information, I think that this will scare people. It's also true that I lost the ability to see through the eyes of a newbie, because I know everything in this system, so I don't know what more information to add

-
I have had numerous times I've come to the forum to search for answers and come up empty.
I would suggest that since the documentation is quite sparse that forum response are very complete. And when someone asks a followup question that responses continue to be complete and exhaustive.
And perhaps answers to forum questions could be rolled back into the documentation. -
@fxdreema Was just thinking about what you said here and came running back.
You say you 'write as less words as possible. (As few words as possible.) And that's wonderful ... for fiction. It's one of the most important rules for good fiction writing. NOT for documentation.
You can write a terse synopsis to keep from 'scaring people away' but you really need to cover all the bloody details below that.
Money is at stake. No details are too small. Everything must be covered.
Absolutely everything.
("Oh, did I forget to tell you a Stop-Loss isn't placed if you don't turn on these hidden options?")
Absolutely everything must be covered. Twice! Or at least try.Perhaps users would be willing to do occasional cleanup of documentation.
But there must be longer, wordy, more complete descriptions to work from.
Even written in Russian would be much better than not enough information. We have Google Translate available, after all.
Thanks!
-
Documentation is like writing a computer program. If you don't cover every detail completely and perfectly it will probably fail at some point.
(Yes, writing documentation kind of sucks. Been there, done that.
)It's a necessary evil.
Thanks for all you do!