ntcharts

This is cool to see from a research team. A few weeks ago I was exploring a similar idea with ntcharts, where a user or LLM can specify a chart in a Golang or JSON object... and then that spec would be rendered either to a Bubble TUI via NTCharts or to HTML/SVG via ECharts. That Echarts HTML could be naturally served by a Golang http service. But Flint goes much deeper with semantic layers and settings optimizations. Perhaps a NTChart, or whatever terminal chart, could be a rendering target? I'll add it to the list to explore... https://github.com/NimbleMarkets/ntcharts/blob/spec/spec/REA...

Just yesterday I was looking for a free-as-in-freedom image to embed in my repo, and this gem popped up again! I'm adding a BubbleTea Picture widget to ntcharts. So the example is a (retro art of (retro art redone on retro tech)) done on (a redo of retro tech) ... I've added it, but it's still on a feature branch : https://github.com/NimbleMarkets/ntcharts/tree/picture/examp...

Building a TUI was easy before, especially with the great toolsets for their respective languages BubbleTea / Textualize / Ratatui. And thanks to those frameworks, LLMs can manifest useful tools. Similar to WebApps, it's only since the November'25 renaissance that I felt I could use them to create TUIs. Once I had that revelation, I started going into my backlog and using it. I maintain a TUI Charting library, NTCharts. In January, I fixed a bug - totally obvious once identified - that I personally failed to find earlier. But the test harness, prompting, and Gemini got it done [1]. Gemini's spatial understanding was critical in completing the task. I've been vibe-crafting a local LLM conversation viewing tool called thinkt. After scraping ~/.claude and making a data model, this is the point in PROMPTS.md where I start creating the

TUI libraries have sufficiently abstracted away the low-level quirks of terminal rendering that the terminal has become something like a canvas[0] available in the IDE with no extensions. This is quite a nice DevX if you want to display the state of an app that does something to data, without writing the necessary plumbing to pipe that data to a browser and render it. [0] https://github.com/NimbleMarkets/ntcharts/blob/main/examples...

As developer of one such libraries (ntcharts), and having some accessibility experience, I've thought about that irony too. On a practical level, is it simply any terminal visualization that can destroy a terminal app experience, or only Braille rune rendering? We could include some guidelines in our project for how to include such charts while ensuring accessibility. Besides via some configuration, I'm not sure how to programmatically recognize that terminal charts would be poorly experienced by a user. EDIT: made a ticket for this https://github.com/NimbleMarkets/ntcharts/issues/2

Here's some terminal charting libraries that use Braille runes: * https://github.com/mum4k/termdash?tab=readme-ov-file#the-lin... * https://docs.rs/ratatui/latest/ratatui/widgets/struct.Chart.... * https://github.com/NimbleMarkets/ntcharts/blob/main/examples...