If you were building a charting library on top of…
0 reactions
If you were building a charting library on top of Lightweight Charts, what extension points would you expect?
I've been open-sourcing a charting toolkit built on top of TradingView Lightweight Charts that includes drawing tools, indicators, replay functionality, pane synchronization, and broker integrations.
One area I'm still refining is the plugin/extension architecture.
For developers who have worked with charting libraries:
* What extension points do you expect?
* How would you structure custom indicators?
* Would you prefer a plugin registry, hooks, middleware, or something else?
* What API mistakes have you seen charting libraries make?
I'd love to hear opinions before locking down the architecture.
#programming #dev #js #technology
I've been open-sourcing a charting toolkit built on top of TradingView Lightweight Charts that includes drawing tools, indicators, replay functionality, pane synchronization, and broker integrations.
One area I'm still refining is the plugin/extension architecture.
For developers who have worked with charting libraries:
* What extension points do you expect?
* How would you structure custom indicators?
* Would you prefer a plugin registry, hooks, middleware, or something else?
* What API mistakes have you seen charting libraries make?
I'd love to hear opinions before locking down the architecture.
#programming #dev #js #technology
| 2,000 mlx | |
| 3 | |
| 0 |