OK...now I understand...and it makes sense..roger-write wrote:It may not be quite as impressive as you might think. Oq parses primarily the class structure elements but mostly leaves the contents of the body of the methods/functions intact. In other words, I don't parse out every name, token and expression, etc in the flow of code. Oq will take the body of a class method/function and copy it straight into mql. The only exception to this is that it will scan for the @ and : characters and do some replacements based on the surrounding names. But for the most part, once you're inside a class method, the code looks exactly like mql with the mentioned exceptions.
It makes completely sense. Does this also mean that we could use OQ eventually with a continuous integration system later on if we have different libraries and create on top of these indicators, EA's or whatever?roger-write wrote:As for converting from mql to oq, you can actually take your existing mql code and run it thru oq without any issue, because anything outside the class {} construct will just get passed straight thru anyway. A good way for coders to start getting accustomed to oq might be to simply take an existing ea or indicator's code and set it up to build thru oq. Then they can start experimenting with a class here or there as needed. But hopefully the reboot, documentation, and examples will go a long way in helping people get accustomed to it. But the existing base of code should co-exist just fine inside oq.
Hopefully this makes sense.
The Template Idea sounds really great. Please don't forget to document this functionality and add also some implementation examples to it. It is sometimes a little difficult to grasp new concepts when you don't have proper examples and/or use-cases.roger-write wrote:One last thing. The rebooted oq will have types of classes called templates. There will be a standard template definition for, say, a trader mechanism or a signal, or an ea manager, etc. When the time comes, I really would like input from coders on defining the various templates. Once these are defined, then lets say a coder wants to create a new signal module for NB's 10.4 system, then all they do is follow the spec for the signal template (what methods are required, etc) and then anyone using oq could simply plug in the new signal and their EAs or indicators become NB 10.4 aware, so to speak.
Regarding your inputs from developers. If our platform is running we will have a idea management system up and running. I think your whole project could be a great asset in our toolset and you could use the infrastructure to get more input on different topics and discuss it also there.
Did you have by any chance the opportunity to look into other Trading Platforms who already implemented OO based Languages (and I don' think about MT5 here.. e.g. NinjaTrader which is based on C#).
Maybe you can get also some Ideas out of their OO implementations.
Thanks again for your creative work and keep it up...
happy trading,
Robert
-