4 ms·
The patch grid and ribbon in the Patchworks Editor this proposes are exactly what I didn’t know I needed
by dylanmclark 8y ago
The patch grid and ribbon in the Patchworks Editor this proposes are exactly what I didn’t know I needed
- vanderZwan 8y agoI think I'm already emulating that to some degree by tiling multiple windows on multiple desktops and switching between them. So yeah, might as well have the editor support it from the start. The Wandercode interface on the other hand I can't find a quick replacement for. From a quick skim it seems like it hits a good balance of making navigation easier without putting so much information on the that it becomes noise. Really would like to try that out!
- azhenley 8y agoTiling and window managers are exactly what inspired Patchworks! It is possible that Wandercode may be released to the public in the near future. It is an Atom plugin in working state, it just needs some fixing up on how it generates the call graph to make the recommendations. Stay tuned!
- alanbernstein 8y agoI'm particularly interested in trying out Wandercode. What's a good way for me to follow its development? Wandercode looks very similar to an idea I had for navigation while working on a task that was 100% code review and comprehension. I wanted similar graph displays for inheritance, and data flow through variables. I envisioned all of this displayed together in a large window, basically with multiple DAGs overlaid on each other in different colors. Now, seeing Wandercode, I imagine a handful of small, "localized" displays, focused on a selected function/class/variable. Any thoughts on that? Or are function calls more interesting for you?