Lawrence Chan wrote:I think I finally answered all the questions from the initial post of this thread
If you have more questions, just ask.
I have just returned from Italy, so I couldn't respond to the answers sooner.
First of all, I would like to thank you very much for your quick and competent answers here on the forums.
If NeoTicker's development and support team is only half that quick and competent in responding to the clients' needs, Neo must be the best platform around, indeed.
Good job, thanks again!
Lawrence Chan wrote:the indicator engine works like an OS and you can effectively write your indicators written in any programming languages that utilize the core indicator object model.
Thus, feel free to use the programming language that you like, be that VC++, VB, Delphi, C#, VB.NET, etc. all works fine
The best thing is, your indicator written in a particular programming language will not affect its ability to be reused by any other indicators written for NeoTicker.
The key that glue it all together is the indicator object model.
This sounds almost too good to be true
So are we not tied to the Neo's development environment and can use Visual Studio 2005 .NET for example?
As I understand it, the core element and value of this whole approach is the object library & charting engine, written by TickQuest.
Are the objects in the library compiled as .NET objects or are they COM objects? Obviously, COM arch is obsolete nowadays.