There should be a possibility to open a Chart from code.
And display an indicator in this chart.
This would allow extensions like "Indicator Profiler" to quickly show how a selected indicator looks like.
In the next step such a Tool could generate a coded strategy which uses this indicator as an entry condition. This would allow to quickly show what such an indicator can do. (performance-wise)
This would be the turbo method to generate a profitable trading strategy form a tool like "Indicator Profiler" or "NeuroLab" or some other clever upcoming extensions.
So I guess the complete feature request reads like this:
Please make it possible for a script/an extension:
1. To generate a coded Strategy, along with a default DataSet and default Symbol etc.
2. Start that strategy
3. Show a chart with all the results (Bars, Indicators, etc...)
4. Show the complete Backtest with the results
And display an indicator in this chart.
This would allow extensions like "Indicator Profiler" to quickly show how a selected indicator looks like.
In the next step such a Tool could generate a coded strategy which uses this indicator as an entry condition. This would allow to quickly show what such an indicator can do. (performance-wise)
This would be the turbo method to generate a profitable trading strategy form a tool like "Indicator Profiler" or "NeuroLab" or some other clever upcoming extensions.
So I guess the complete feature request reads like this:
Please make it possible for a script/an extension:
1. To generate a coded Strategy, along with a default DataSet and default Symbol etc.
2. Start that strategy
3. Show a chart with all the results (Bars, Indicators, etc...)
4. Show the complete Backtest with the results
Rename
Let's make sure that program's capability is exhausted first to qualify for a feature request?
There already is I believe. It should be possible to instantiate a chart object from code because even WL6 could do it easily.
A script that runs a backtest inside a backtest?
QUOTE:
There should be a possibility to open a Chart from code.
There already is I believe. It should be possible to instantiate a chart object from code because even WL6 could do it easily.
QUOTE:
4. Show the complete Backtest with the results
A script that runs a backtest inside a backtest?
QUOTE:
A script that runs a backtest inside a backtest?
This one is meant to be called from an extension, not from a running strategy....
QUOTE:It might be useful for a brokerage extension to call a Chart/Strategy window displaying the symbol that's currently being traded.
This one is meant to be called from an extension, not from a running strategy.
Charts from code are coming your way DrKoch. Here's a sneak peek of the new DrawImageAt method from Build 9 at work creating a panel of stacked charts using ScottPlot:
While the ScottPlot is a great new addition, I don't think it satisfies this feature request.
The idea here is to provide a method whereby an extension can launch a chart window, optionally with certain indicators and/or strategy included.
The the specific case of Indicator Profiler, my feeling is that a new Chart tab in the extension window itself would work better.
The idea here is to provide a method whereby an extension can launch a chart window, optionally with certain indicators and/or strategy included.
The the specific case of Indicator Profiler, my feeling is that a new Chart tab in the extension window itself would work better.
A strategy or an extension should be able to run another strategy. This will allow to do slideshow for a list of symbols.
In this case, if there is already a window for a strategy, then that should be reused instead of launching a new window with the same strategy.
In this case, if there is already a window for a strategy, then that should be reused instead of launching a new window with the same strategy.
Let's be clear, an Extension can already include a Chart component, and chart symbols and indicators. The CandleStick, Chart Patterns, and the NeuroLab Extensions are already doing this. I think what's missing is proper documentation, so this Request can encompass documenting this piece of Extension development. The second half is running a backtest from within a Strategy. Again, it's already possible, but I plan to create a new helper class to make it simpler and to document this in the QuickRef as part of the dev effort for this #FeatureRequest.
As far creating a Strategy dynamically, that's just code generation, and the new helper class should allow a Strategy to execute any dynamically generated source code.
As far creating a Strategy dynamically, that's just code generation, and the new helper class should allow a Strategy to execute any dynamically generated source code.
Your Response
Post
Edit Post
Login is required