kz930 opened a new pull request, #9058: URL: https://github.com/apache/texera/pull/9058
### What changes were proposed in this PR? Hovering an operator for half a second shows a card with its first rows, its error, or how to keep a result the run did not keep. Pinning the card turns it into a window beside the operator with the whole result table, tied to it by a line. Several windows can be open at once; each can be dragged and resized, and follows its operator when it or the canvas moves. The hover preview can be turned off under Layers. An operator with more than one output gets a tab per output port in its window. The first port is the one the running execution reports on; another port is read when its tab is shown, using the port-aware page requests from #9054, and pages by the row count those replies carry. The table in a window fills the window's own height by the same rule it uses to fill the result panel. The result panel is unchanged here; trimming it to the console is the next step in #9052. (screenshots) This needs #9054, so the diff includes its commit until #9054 merges. The PR's own change is the last commit. ### Any related issues, documentation, discussions? Closes #9057. Part of #9052. Design discussed in #8842. ### How was this PR tested? New specs for the hover card and the pinned window, and new cases in the specs of the workflow editor, the result table and the result service, cover the delays, pinning, the port tabs, port-aware paging and the window's page size. The full frontend suite passes. In the running app, a Split of 20 rows into 13 and 7 shows the first output's 13 rows in its first tab and the other 7 in its second, each paged correctly. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 5.5) 🤖 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]
