EnginePine Script
Pine Script
Run native Pine calculations and signals while keeping data and execution ownership explicit.
Native Pine lets an app calculate indicators, render plots, produce signals, and emit supported strategy order intents. The app stores native source in pinescript.
For the main algorithm workflow, use Pine as a calculation/signal producer and SJS for order timing and execution state. A Pine strategy can instead own order intents, but choose that ownership explicitly.
Runtime responsibilities
| Component | Responsibility |
|---|---|
| STX market-data/session runtime | Instrument, observations, aggregation, session processing, and warmup |
| Native Pine runner | Incremental Pine evaluation and plot/signal/intent output |
| SJS, when used | Main algorithm, signal consumption, order/position checks, and requests |
| STX simulator or broker adapter | Order handling, execution outcomes, and position state |
A working Pine chart is not proof of full TradingView language or strategy-tester compatibility. Verify the feature and selected execution path you need.
Read in order
- Getting started: plot averages and a named signal.
- Supported features: verified capabilities and exclusions.
- Inputs and configuration: source, input defaults, and session settings.
- Plots and outputs: visible series and raw named plot data.
- Signals in SJS: consume timestamped output deliberately.
- Strategy orders: the native intent bridge and its limits.
- Warmup and history: initialization and live startup.
- Backtesting: compare inputs, signals, and outcomes.
- Debugging: compile, chart, signal, and execution issues.
The existing Configure PineScript page remains the app-editor setup walkthrough.