davsclaus opened a new pull request, #29457:
URL: https://github.com/apache/camel/pull/29457

   _Claude Code on behalf of davsclaus_
   
   The Timeline screen gets the same layout pass as Overview ▸ About in #29429. 
On a tall screen it used about half the rows: its two panels sat directly on 
top of each other, and the empty rows were all at the bottom.
   
   On a tall screen (12 or more rows to spare):
   - There is padding inside both panels, a blank line after the Errors/s 
chart, after the Routes legend and around the detail lines, and a blank line 
between the panels.
   - Each route's strip is 2 rows high (16 levels), with the name and summary 
on the bottom row, and there is a blank line between routes.
   - The Errors/s chart and the per-second chart of the selected route grow 
from 4 rows to as many as 6.
   - Spare rows are used in this order: the room around the panels, the blank 
lines between routes, the taller strips, and then the charts. With many routes, 
the routes keep one row each.
   - Clicking a route's strip selects that route. Clicking the blank line 
between two routes does nothing.
   - When Enter opens the exchanges of a second, the list gets the taller 
detail panel.
   
   Smaller screens keep the compact layout unchanged. At 198×48 the screen now 
uses 41 of its 48 rows, up from 23.
   
   Tests:
   - New tests in `TimelineTabRenderTest`: the tall layout, the compact layout, 
how the spare rows are shared out, and selecting a route by clicking its strip.
   - The full `camel-jbang-plugin-tui` suite passes.
   - Checked live with a launcher bundle.
   
   Docs: the Timeline help page and `camel-jbang-tui-observe.adoc`.
   
   🤖 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]

Reply via email to