Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Actually no, we do not. What we need is a new method to figure that out. NinjaScript - which does not exist to start with as it is just C# and no, having an API does not change the language at all, so NinjaTrader just fakes having a langauge to look better - can not have a keyword for the obvious reason, and finally it makes no sense to make functional specific keywords in a regular programming language when the same can be done with a method.
That said, I think we need more.
I would like to know whether I am:
* Running live
* Backtesting
* Refreshing (for indicators when the historical part of a chart is drawn)
with a nice method available in strategies and indicators.
* Running live
* Backtesting
* Refreshing (for indicators when the historical part of a chart is drawn)
* Running Replay (Simulation)
* If running Replay, access replay speed
- and an easy way to run it remotely through a local window on a faster hosted server so I can set stops not dependent on my ISP or router or OS's finicky tendencies to halt then burp missed data.
- workspaces that don't get corrupted when NT crashes
- less crashes
- adapt friendlier UI improvements like many other packages
- fix backup so they restore onto a different machine reliably
Like Multicharts, where you have a website where you can see issues etc. being worked on.
* Sensible update cycle?
Like an update every 3 months, keeping technology current (.NET framework version) and fixing stupid little issues like - installing in the wrong location for domain member computers that have folders remapped to a server.
* A programmer working on small improovements.
You know, like little STUPID issues in forms (downloading a day of data only etc.). Why do I have to wait for a version 8 for someone to put in a drop down in the replay speed change? That is an hour of work. Same with data downloads for market replay - a day and the form i a LOT more usable.
* Sensible versioning of assemblies, opening some source and the app.
No need to change the DLL version on a new build (MS even has documentation for that). Open the source of the main windows (WINDOWS - not controls) and allow us publicly to replace them (additional buttons on a window or DOM). Isolate interfaces into a separate DLL and only keep the stuff in the core obfuscated (like for example also the chart). Right now I can not add my own forms (bad), I can not expand forms legally (bad).
Mostly my complaint ar along the dmonstrated ability to properly manage this product - most of the bugs would be a lot easier to bear if the company behind would not try to run the product like the communists were running russia during the cold war - by shooting everyone not agreeing and having 5 year plans that never work out, plus keeping every sensible piece of information a state secret. if Ninja would run more open and more competent in management I would be more confident in Version 8 and forward.
For this very reason, I'm rarely connected when I run backtests. I usually just load and new data since the last load when starting up Ninja (through DTN) then disconnect and run all my testing. This seems to make things faster, since Ninja will then use its own database of prices.