Commit

29c7ec2

For A - I cannot float a window at all. Because it either goes to the edge or opens as another tab, the only way to float it is to click on the float button. Once floated, I cannot move its position. So I cannot judge because I'm not sure if this behavior is intended. For B - It…
Thanks. A's problem is real, not a bug in the lab: the panes fill the screen, so every spot is a dock target. A window can never just move. That rules A out. So B wins. To cut its UI, I can make B2: show the five buttons only in the pane under your finger, and the edge buttons…
On it: B2, plus A2. In A2, touching a pane's tab bar arms that pane, then its edge zones work until you leave it. Anywhere else, the window just moves.
B2 it is. I'll record that on #20, move the lab to a branch, then start building real drag-to-dock (#25). That one takes a while, so I'll post when there's something to try.
OK. I closed #25 and moved the keyboard part to #33. Next, I suggest #26: save the workspace, so a layout survives a reload. Or #22 first, a tiny doc fix. Which one?
#22 is done. Starting #26 now. #27 and #28 build on it, so they can't run in parallel; I'll do them after. #29 is big and mostly separate. #30 needs your answers first.
#30 Q1: a tool's main window is docked, and the tool opens a sub-window. Where does it appear the first time? A) a tab in the main window's pane (it covers the main window) B) floating at the usual cascade spot (today's behavior) C) the tool decides I suggest B: a sub-window is…
Agree

commit 29c7ec2

Done and live: #22, #26, #27, #28, #30. Try: open a tool at /, press "Save as workspace", name it. The URL becomes ?workspace=<name>, and it saves as you go. ?tool=counter,echo opens two tools. One gap: if a tool fails to load during restore, it drops out of the workspace. Left:…