[Feat]: Visual EXPLAIN Table view enhancements - Loops column, detachable window, and customizable column order

[clipper0317]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal

This is a follow-up feature request after the
recent improvements in #302 and #303.
I would like to suggest three enhancements
to further improve the Visual EXPLAIN experience.

1. Add "Loops" column to Visual EXPLAIN Table view

The "Loops" value is currently only visible in
the right-side detail panel when clicking a node.
It would be very helpful to display it as a
dedicated column in the Table view alongside
Time and Actual Rows.

This is especially important because:

• Time column shows per-loop time (e.g. 2 us)
• Loops shows how many times it executed (e.g. 331,603)
• Users need both values visible at once to
  understand the real performance impact

Screenshot attached shows Loops: 331,603 hidden
in the detail panel while Time shows only 2 us.

2. Detachable / Movable Visual EXPLAIN window

Currently the Visual EXPLAIN window is fixed
and cannot be moved or detached.
It would be extremely useful to detach it and
move it to a separate monitor in a
multi-monitor setup, so users can:

• View the execution plan on one screen
• Edit and run the query on another screen
• Compare both simultaneously during tuning

3. Customizable column order in Table view

(I understand this may require significant
development effort)

Currently the column order in Table view is fixed:
Operation | Table | Cost | Est.Rows | Time |
Estimate Gap | Filter

It would be wonderful if users could
drag-and-drop columns to reorder them
according to their own tuning workflow preference.

Motivation

I am an Oracle performance tuning specialist
who recently started working with MySQL and
MariaDB. I use Tabularis as my primary tool
for Visual EXPLAIN analysis.

1. Loops column: Without seeing Loops in the
   table, it is easy to misread the Time value.
   For example, 2 us × 331,603 loops = ~663ms,
   but the table only shows 2 us which is
   misleading without context.

2. Detachable window: Multi-monitor setups are
   standard for database professionals. Being
   able to compare the execution plan and query
   side by side on separate screens would
   significantly improve productivity.

3. Column reorder: Different tuning workflows
   prioritize different metrics. Oracle's SQL
   Developer allows column customization and
   it greatly improves the tuning experience.

Environment:

• Tabularis version: 0.13.1
• MariaDB version: 12.3.2
• MySQL version: 8.4
• OS: Windows 11

Example

No response

[clipper0317]

참고로, 제가 영어가 서툴러서 AI의 도움을 받았습니다. 양해바랍니다.