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)
i think it would be cool to be able to set conditions on NT for auto change of contracts.. so i could set it up to manually start loading the next contract when volume is greater on one than the other..
dont believe anything you hear and only half of what you see
MultiCharts may be a better platform, but unless they extend their trial period beyond 30 days they will never gain the marketshare needed to overtake NT. Per their comments in a different thread they pretty much refuse to even consider the option of a trial extension.
It was not my intention to derail this thread, so lets keep it on topic as much as we can.
But bottom line, competition is good. Without Chevy, Ford would have been dragging its heels, slow to innovate, over priced, etc etc. Competition is good.
I look forward to NT8. Based on what Ray has said in the past webinars on futures.io (formerly BMT), we can likely expect a new user interface, proper bid/ask persistent storage, and significantly improved efficiency/performance. The hard part is waiting.
I prefer companies release a core product with fewer but solid feature set and followed by frequent updates adding new features rather than take 2-3 years between releases.
"Trend Channel" tool.
would be nice with some information on line like %, Angle.
And as always no limits of numbers of lines, same thing for fibonacci retracement.
* Realize this is the 21st century and crappy release cicles are YOUR problem.
Example: These days we can not connect to Rithmic or TT (fix protocol) with 64 bit because they... use native windows libraries to connect. WHich are only available in 32 bit.
How hard would it be for a point release (7.1=) to come out and replace those connectors with something not outdated? Rithmic has native .NET libraries (ergo they work also 64 bit) and for FIX you use QuickFix .NET wrapper. Interesting enough there now is QuickFix/n which is native .NET - and 64 bit again.
The list goes on. Years between releases and no real movement in between is off. I use a lot of third party tools in my work and they all release more often. Fr example Infragistics (nice UI controls) has a couple of releases per year. They put in new features as they can but always do maintenance (btw., the same UI library that NinjaTrader uses - but they supposedly stopped paying for it because the version they use in Ninja 7 is as outdated as the one for 6.5 was before).
I would expect more pushy releases to make sure things keep technology wise more current. For example you COULD easiyl release NinjaTarder 7.5 with full 64 bit support AND .nET 4.0 runtime. I am suree it would take less than 2 days to validate NinjaTrader works fine on .NET 4. I run a lot of projects over the last 15 years and I always push to keep the platform updated.
* Learn the rules of the platform you work on.
NinjaTrader = windows application. MS has guidelines for windows programs. Why do you not sit down and READ them. For example these days I can NOT run NinjaTrader using a non-local account (i.e. a domain account). So, wherever I use ninja I have to keep a separate set of logins available. This means I can not run Ninja on the machine I work on - I have to go into a virtual machine for anything, and I HAVE (!) to run a local account. AAAAAAAHHHH.
* Understand not everyone is barely scrapping away as programmer
Visual Studio as primary development environment is something many people would love. Make your own Project Type - it takes less than 3 days to learn how to extend visual studio. It brings a lot. Sorr, I really like the editor you ahv there (been using ActiPro myself at times) but your development environment is retarded compared to a real one like Visual Studio. No soruce control integration, funny compiler tricks, no unit testing possibility.
Finally some more constructive things:
* Provide a timer callback.
I have the point that we plan to not trade at specific times, including ripping out existing trades. Sadly trades are not running on time base charts. So we add a time based bar ONLY to get callbacks. Having a once per second timer would be good enough to do that. It also allows the strategy to write out time based reports (once per minute to the database for example) without the need to run a 1 minote or 1 second bar just for getting callbacks.
I often want to queue up 20 o 30 completely different tests but can not. It also would be really nice if those unit test results could be set up in a nice XML based format with all trades so those of us thinking there are better databases than the one you use could load them into SQL Server and run some real analysis on them. There is a lot to learn from proper analysis of data (like proit per week day, per day of trading correlating to the number of trading days before and after (so a lonely friday is taken out because thursday is no trade and saturday / suday too). IT also allows more interesting scenarios like sliding optimization.
* Support proper backtest scenarios
This means backtest + forward test (backtest 6 months, forward 2 months, comapre results). Standard sutff that is a little more inteesting than what TradeStations did years ago. Check Zorro Online Manual for some really interestign concepts that you should support, also from an analysis point of view.
And my favourite:
* Open your API. Get rid of the stupid multi broker and make a real pro version for more advanced users. Ninja is open API anyway (TT FIX - here I come) and it really lacks on the backtest and analysis methods. So, I can attach any data feed and proker already as programmer (so I never will pay multi broker) but OTOH... it looks not nice on advanced features.