Do you want TradingView charts for free? Their lite weight charts are open source. github.com/tradingview/light… Give that to @OpenAI or @claudeai with this prompt; “You are a senior quant-platform engineer and graphics engineer. Build an open-source, production-quality trading charting platform using open-source libraries. Do NOT use TradingView Advanced Charts, proprietary chart SDKs, embedded TradingView widgets, or paid charting components. Use these as building blocks/reference implementations where useful: - TradingView Lightweight Charts: github.com/tradingview/light… - PixiJS: github.com/pixijs/pixijs - uPlot: github.com/leeoniya/uPlot - Apache ECharts: github.com/apache/echarts PRIMARY GOAL Create a modular trading-chart engine that can eventually support a TradingView-style charting experience while allowing any market-data provider to be plugged in. Do not make a demo. Build the foundation of a real charting product. CORE CHART Implement: - Candlestick, bar, line, area, and Heikin-Ashi charts - Volume - Multiple synchronized panes - Multiple price scales - Timeframe switching - Symbol switching - Smooth mouse/touch pan and zoom - Crosshair synchronized across panes - Price/time tooltips - Autoscaling - Logarithmic and percentage scales - Extended-hours sessions - Session breaks - Real-time candle updates - Historical pagination when scrolling backward - Efficient handling of hundreds of thousands of bars INDICATOR ENGINE Create an indicator architecture separate from the renderer. Include initially: - SMA - EMA - VWAP - RSI - MACD - Bollinger Bands - ATR - Volume Profile Indicators must be dynamically added/removed and able to render either over the price chart or in independent panes. Design the API so community-created indicators can eventually be loaded as plugins. DRAWING ENGINE Implement an independent drawing-object system supporting: - Trend line - Horizontal line - Vertical line - Ray - Rectangle - Price range - Date range - Fibonacci retracement - Parallel channel Every drawing must support: - Selection - Dragging - Resizing - Deleting - Style properties - Serialization - Restoration - Undo/redo Do not tightly couple drawings to Lightweight Charts internals. DATA ARCHITECTURE Do NOT hard-code a market-data provider. Create interfaces such as: - MarketDataProvider - HistoricalBarsProvider - RealtimeTradesProvider - RealtimeQuotesProvider Support normalized events such as: - Trade - Quote - Bar A market-data provider should be replaceable without changing the charting system. Build a WebSocket ingestion layer capable of batching high-frequency updates before sending them to the renderer. PERFORMANCE Treat performance as a first-class requirement. Use where appropriate: - Canvas/WebGL/WebGPU - Typed arrays - Object pooling - requestAnimationFrame batching - Incremental calculations - Web Workers for expensive indicators - Viewport-based rendering - Intelligent downsampling Avoid rerendering React/Angular components on every market tick. The architecture should remain responsive with large historical datasets and high-frequency real-time updates. UI Keep the interface minimal and professional. Desktop-first layout: Top: - Symbol search - Timeframe controls - Chart type - Indicators Left: - Drawing toolbar Center: - Main chart Right: - Optional watchlist/details panel Bottom: - Optional indicator panes Use a dark neutral appearance. Do not waste time building a marketing interface. Focus on the charting engine. ARCHITECTURE Split the project into clear packages/modules such as: - chart-core - chart-renderer - data-engine - indicator-engine - drawing-engine - provider-sdk - ui Keep the core engine framework-agnostic wherever practical. DELIVERABLES Produce: 1. A working application. 2. Complete source code. 3. README explaining the architecture. 4. Data-provider interface documentation. 5. Indicator plugin documentation.