3 ms·
Thanks for taking the time to answer my bad question sincerely! Here's a situation that actually comes up all the time in my remote pairing sessions. Both peer
by corytheboyd 6y ago
Thanks for taking the time to answer my bad question sincerely!
Here's a situation that actually comes up all the time in my remote pairing sessions. Both peers have mutli-screen setups where a terminal (tailing logs, etc.), an IDE, and a web browser (perhaps even the browser dev tools) are all in separate windows, where some windows are on one display, some on another. With CoScreen, would "hey, can we check the logs real quick?" become as simple as the other peer clicking the window to add it to the session? That could be pretty big on its own IMO!
Also really useful, as the non-driving peer is looking up documentation and adding it to the session for group reference.
I'd love to try this out eventually, joining a new team soon and perhaps I can pull it off there if/when pairing needs arise!
- thedracle 6y ago"Thanks for taking the time to answer my bad question sincerely!" No problem! It's actually a great conversation starter. "With CoScreen, would "hey, can we check the logs real quick?" become as simple as the other peer clicking the window to add it to the session?" Basically yes, there is a tab that shows above your window. At the moment we have a shared context space, so your windows have a relative location that is based on the layout of the remote screen. Ultimately this helps in like the pair programming scenario you make above, but is a weakness in other situations: we are working on a model that will let you break all of the window locations apart, or relatively translate the position of another user's windows wherever you want. "I'd love to try this out eventually, joining a new team soon and perhaps I can pull it off there if/when pairing needs arise!" We'd love to hear your feedback. We rely heavily on our community to determine our development path, so please reach out to us when you do, and leave feedback!