4 ms·
This is really cool! I like the fact that when you navigate to a method/declaration/whatever, it only contains the relevant snippet, rather than opening a secon
by sensanaty 2y ago
This is really cool! I like the fact that when you navigate to a method/declaration/whatever, it only contains the relevant snippet, rather than opening a secondary tab with the whole file scrolled to where the definition is.
I often end up in a situation where I keep losing track of whatever method I'm reading since I need to compare where a method is called vs its definition, which is frustrating. I like that I can just "pin" the method to the side, and can glance at it without accidentally switching to scrolling through the whole file in the pinned view.
I tried it out for a bit and I found it a bit too mouse-centric unfortunately, and I quickly ended up in a situation where I had way too many floating windows to manage, especially once I got into checking out methods inside of other methods. It would be nice to have an arrow or line to keep track of what the "parent" window is so that it's easier to build a sort of flowchart.
Regardless of my personal issues with it, hope you succeed with this! It's great to see alternative ways of thinking in this space, as I often feel things could be better but it's also hard to imagine how.
- WillAdams 2y agoLiterate Programming affords a 1D (vertical/scrolling) implementation of this with two views: - raw code w/ comments/text - nicely typeset code with formatted text and hyperlinks for navigation http://literateprogramming.com/ http://literateprogramming.com/
- akshaysg 2y agoYeah we have some work to do to make it easier to navigate on the keyboard. For the "parent window" what are you imagining here as your frame of reference? This idea makes sense but I'm wondering if you want to designate a specific window as an anchor vs some heuristic that identifies such an anchor.
- andybak 2y agoI viscerally dislike manually arranging windows. Have you investigated auto tiling? Also how well does this work on smaller screens? My preferred ergonomic posture is slumped on the sofa with a laptop on my belly.
- akshaysg 2y agoWe should be placing the editors in your viewport so that you don't have to do manual arrangement. We try to fit as many editors in your viewport as possible. I use a 15 inch laptop and it works well there. I do not know how small your screen is, but please let me know if you feel like it's not ergonomic for smaller screens.
- broken-kebab 2y ago>I like the fact that when you navigate to a method/declaration/whatever, it only contains the relevant snippet I see why you like it, but I suspect it could be sum negative in a long run. I believe it's beneficial to just be aware of what and where is in the code. Can it be that few years went with a project, and you still don't know what all those files are about because you has been working only with small chunks?