This looks really interesting and well thought out. Nonetheless, I feel like the OS window manager should provide this kind of experience, with appropriate hooks so that an IDE can implement this sort of experience with native windows. I really liked using PaperWM¹ for a while, however, I'm still waiting for it to get more stable. Another system that is sort of similar to this concept, Pipeworld² (part of the Arcan p…
Show HN: Haystack – an IDE for exploring and editing code on an infinite canvas
161–170 of 227 posts
Re: Show HN: Haystack – an IDE for exploring and editing code on an infinite canvas
#162Re: Show HN: Haystack – an IDE for exploring and editing code on an infinite canvas
#163This 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…
- raw code w/ comments/text
- nicely typeset code with formatted text and hyperlinks for navigation
Re: Show HN: Haystack – an IDE for exploring and editing code on an infinite canvas
#164I published a paper comparing navigation time with a canvas-based editor (Code Bubbles) vs. traditional tab-based editor (Eclipe) vs. a carousel-based editor (Patchworks, a tool I designed). We found the canvas provided too much freedom. https://austinhenley.com/pubs/Henley2014CHI_Patchworks.pdf
> [...]
> Because users of Code Bubbles and Patchworks were able to open code at the granularity of methods, they had the advantage of never having to scroll through code to reach their navigation targets.
Have only read a bit of this paper but from this discussion over Eclipse it seem that the participants could be a lot more efficient if they used it more like an IDE than a multi-tab editor. Finding methods should be much less of an issue having an (alphabetically ordered) outline view.
Re: Show HN: Haystack – an IDE for exploring and editing code on an infinite canvas
#165I published a paper comparing navigation time with a canvas-based editor (Code Bubbles) vs. traditional tab-based editor (Eclipe) vs. a carousel-based editor (Patchworks, a tool I designed). We found the canvas provided too much freedom. https://austinhenley.com/pubs/Henley2014CHI_Patchworks.pdf
Tantalising research! Is the source-code for the Patchwork editor publically available?
Re: Show HN: Haystack – an IDE for exploring and editing code on an infinite canvas
#166I find multiple workspaces works well for large context switches, then within each workspace, maximising pixel space is done with sloppy/mouse focus, partially overlapping windows and the ability to split my text editor windows easily.
Re: Show HN: Haystack – an IDE for exploring and editing code on an infinite canvas
#167Re: Show HN: Haystack – an IDE for exploring and editing code on an infinite canvas
#168The zoom control with the wheel seems wrong too, scrolling up should zoom, not dezoom.
I also would like to display a single function in a pane but it doesn't seem to work, at least with Go code.
All in all that seems very well done and very close to what I'm looking for, but the UI is a bit confusing
Re: Show HN: Haystack – an IDE for exploring and editing code on an infinite canvas
#169Re: Show HN: Haystack – an IDE for exploring and editing code on an infinite canvas
#170I published a paper comparing navigation time with a canvas-based editor (Code Bubbles) vs. traditional tab-based editor (Eclipe) vs. a carousel-based editor (Patchworks, a tool I designed). We found the canvas provided too much freedom. https://austinhenley.com/pubs/Henley2014CHI_Patchworks.pdf