Haven't really had a whole lot of time to play around yet, and have so far just converted an indicator and strategy from NT7 to NT8. Planning to check out the new Strategy Analyzer, convert a few more indicators/strategies and paper trade the converted strategies over the next few days.
Some thoughts so far:
1. Perhaps NinjaScriptProperty (i.e. declaring input parameters for Indicators and Strategies) should be listed under the list of code breaking changes? Detailing how to go from the old to the new:
[Description("Stop loss in basis points?")] [GridCategory("3. Stock Models")] public double StopLossBps { get { return stopLossBps; } set { stopLossBps = Math.Max(0, value); } } [Range(0, double.MaxValue), NinjaScriptProperty] [Display(ResourceType = typeof(Custom.Resource), GroupName = "3. Stock Models", Order = 6)] public double StopLossBps { get; set; }
3. Moreover, in NT7 these parameters (Days2Load, CalculateOnBarClose, ExitOnClose, etc.) were put in Initialize(). Am I correct that the equivalent of doing that is now to put them in State.SetDefaults within OnStateChange() as opposed to State.Configure (which is supposedly the equivalent of Initialize() - doing this seems to display the default parameters, then overwrite them when the strategy is actually run/backtested). Maybe this could be clarified in one of the help files.
Some other minor feature requests which I would find useful:
4. Have a "Open/Show in Explorer" option in the right click context menu within NinjaScript Explorer, as I still like manipulating files using Windows Explorer as it allows sorting and is also easier (in my opinion at least) to create folders and move stuff around.
5. Perhaps implement a dual view option for NinjaScript Editor, such as in the case of the output window, with synchronized scrolling etc. At the moment, you can always open two copies of Editor and use Windows+Left and Windows+Right to have them side by side, but for me, it feels more difficult to manipulate files between the left and right Editor in this scenario, and having NS Explorer pinned on both instances limits the space remaining to work with.
Thanks
Comment