davsclaus opened a new pull request, #27196: URL: https://github.com/apache/camel/pull/27196
_Claude Code on behalf of davsclaus_ The source editor features had grown into a long part of the camel-jbang TUI page. They now have their own page, `camel-jbang-tui-source-editor.adoc` (in the nav under Camel TUI): - a list of the top features at the top; - one section per feature, each with a screenshot of it in use, annotated to point at the feature; - the keyboard tables of viewing and editing. The main page keeps a short Source section with the live run data screenshot and a link to the new page. Features covered: live run data, problems as you type and the blocked save, quick fixes, fix with AI (with the AI edit confirmation), completion, quick documentation, navigation (jump links, go to route/node, the YAML path in the title), change markers and the F7 diff, and YAML/Java/XML format cycling. ### Screenshots 12 new PNGs in `images/jbang/camel-tui-source-*.png`, 1600 px wide like the existing ones (about 350 KB each). They were taken with the TUI's own screenshot export (Take Screenshot / the `screenshot` MCP action), rendered from SVG with headless Chrome. The yellow notes are drawn on the screen with the MCP `tui_draw` overlay, so they are part of the export. The demo is a small project: a Java route with a failing branch, sending to a YAML route. ### Corrected along the way - The old text said *i* toggles inline documentation. That key is gone: the quick documentation panel replaced it and is always shown. - Saving and continuing is *Ctrl+S* (the old table said Shift+F5). ### Merge order This page describes and shows features from #27187 (quick fixes), #27188 (fix with AI), #27189 (live run data) and #27190 (AI writes refuse only new problems), so it should go in after them. #27189 also touches the Source sections of `camel-jbang-tui.adoc` that this PR moves; I will rebase this one after those merge. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
