Building Indicator Objects and Collections for Multi-Symbol Time Series
Summary
This article extends a trading-platform library by creating concrete indicator objects from an abstract base class and collecting them in a searchable, sortable list. Each object stores properties such as indicator type, timeframe, handle, group, symbol, and name. The collection is intended to provide a common place to access indicator data and later attach event handling across indicators.
The implementation adds property descriptions, sorting criteria, and descendant classes that specify the details of particular indicators. The article’s evidence is a software design and implementation walkthrough, not a trading experiment: it discusses how the classes fit together and includes a testing section, but the excerpt gives no performance or strategy results. This infrastructure can help developers manage indicators across symbols and periods, yet it does not explain whether any indicator generates a useful trading signal or how such signals should be evaluated.
Key ideas
- Concrete indicator classes extend a shared abstract base and provide details for specific indicator instances.
- Indicator properties include type, timeframe, handle, group, plotting value, symbol, and names.
- A collection supports searching and sorting indicator objects by their properties.
- Centralizing indicators is intended to make access and future event handling easier in programs.
- The article describes library architecture rather than validating indicator signals or trading performance.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.