Open elviskahoro opened 3 years ago
This is a really cool feature idea. This could be super useful.
I think it makes sense to allow the unpinned block to go back to its original location. I imagine in the case of unpinning items and having them just go next in line, vs back to their original locations, could get pretty confusing, when it comes operations that were performed in a specific sequence. It would be hard to follow the history, IMO.
My imagined experience for a pinned block was that it would behave like a "sticky" header that becomes fixed to the top of the viewport when it would have scrolled out of view. That does however create the possibility that pinning a block that's taller than the viewport would completely render the viewport unusable (or it could shrink down and have its own scrollbar).
Another possibility is that you can "pop out" a block. The "Share Block" experience almost does this, but it also pops up in a modal inside the app window, so I can't continue using the terminal while it's there.
My use case is a command that spit out a bunch of information I'll need to reference as I continue to do work:
Some folks made a prototype of bookmarking Blocks during our hackathon. Hopefully it's something we can share soon!
We just launched the bookmark feature in the latest version of Warp! You could find documentation for this feature at: https://docs.warp.dev/features/blocks#bookmarking-a-block
The bookmark feature is brilliant. Pinning blocks to the top of the viewport is a very desirable feature too.
Describe the solution you'd like?
Is your feature request related to a problem? Please describe.
Additional context
Related Issues: