[jira] [Work started] (CAMEL-24395) camel-tui: Unify view and edit mode rendering to use a single TextArea-based path

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-24395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on CAMEL-24395 started by Claus Ibsen.
-------------------------------------------
> camel-tui: Unify view and edit mode rendering to use a single TextArea-based path
> ---------------------------------------------------------------------------------
>
>                 Key: CAMEL-24395
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24395
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>
> The Source tab has two separate rendering paths for view mode (Paragraph widget + custom line rendering) and edit mode (TextArea widget + post-render overlays). This causes:
> - Duplicated logic for line numbers, syntax highlighting, cursor marker, doc panel, scroll
> - Visual shifts when switching between view and edit mode (F4) because the two renderers have slightly different layout math
> - Scroll position not preserved across mode switches
> The proposed fix: always render using TextArea (even in view mode as read-only). One rendering path, one scroll system, seamless F4 transitions.
> Features that need migration from the Paragraph-based view renderer:
> - Format cycling (YAML/Java/XML route dump)
> - Jump links (crosshair arrows to linked routes)
> - Markdown toggle for .md files
> - Horizontal scroll (scrollX)
> - Deprecated line scanning
> - Plain mode (borderless for copy/paste)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)