Repository navigation
Replies: 1 comment
|
makes sense as a general feature, not only for a launcher: a window overlay, an HTML page owned by the window rather than by a session. It would behave like the session HTML overlay: full or sized panel, the same it is a bigger change than it looks (page ownership, input routing, and the remote path for sessions attached from another Mac or served by agterm-server), so I'm postponing it for now. the closest thing that works today is a keymap custom command bound to a hotkey. It runs without a session as long as it uses only creating a workspace at a given place in the sidebar is a separate gap: |
Uh oh!
There was an error while loading. Please reload this page.
As suggested in the Telegram chat, I'm moving this idea here.
I'd like to open an HTML overlay without binding it to a session, including when there are no sessions yet. The overlay would appear over whatever is currently in the window: the selected session, if there is one, or the empty content area otherwise.
Use case
I'm building an HTML launcher that reads a file and shows folders on the local host or a remote VM, along with additional information about each folder that doesn't fit in the standard
agtermctl pickUI. Selecting a folder can open a session there or trigger another action. When opening a session, the launcher may first need to create a workspace at a particular place in the workspace tree, then create the session inside it.The menu is how I choose what to open and where it belongs, so I don't want to create a terminal session just to display it. It should also work when opening the very first session.
Why a temporary session doesn't fit
Currently, I can only open the HTML overlay in an existing session. Creating a temporary session just to host the menu would mean creating and later removing an otherwise unnecessary session, and potentially switching workspaces as well. I'd expect that to cause visible flicker during the transition to the session I actually want.
I also want a compact floating menu, not a terminal session taking up the whole content area just to host it.
Desired behavior
A window-level HTML overlay that:
As a nice-to-have, it could also be a top-level overlay that appears above any HTML or program overlay already open in the selected session, without closing or replacing it. That would let the launcher work regardless of what the session is currently showing, but it's not essential to the session-independent behavior.
The launcher logic would remain in my script/HTML; the missing piece is a way to display it before a session exists. Would you consider supporting this?
All reactions