Project(s)-wide SideKick
Submitted by Monday, 23 October, 2006 - 13:46
on
The SideKick plugin currently provides a tree for the current buffer, which can be updated each time the buffer is modified or another buffer becomes the current buffer.
How about a project-wide SideKick? I normally work on an entire project, not a single buffer. I have many buffers open at the same time and I frequently switch between them (or open new ones). Nearly every single feature/bug fix I write involves several files. A project-wide SideKick could help navigate an entire project - for example, I don't need to know where a function is defined (or even type its name) in order to go to it. I can simply click it in the project-wide SideKick.
To be generally useful, a project-wide SideKick would probably need some filtering, but this in itself is an issue for another discussion. What do you think about a project-wide SideKick? The CtagsSideKick plugin, for example, could use existing (project-wide) tag files to generate much more information than it currently does.
How about a project-wide SideKick? I normally work on an entire project, not a single buffer. I have many buffers open at the same time and I frequently switch between them (or open new ones). Nearly every single feature/bug fix I write involves several files. A project-wide SideKick could help navigate an entire project - for example, I don't need to know where a function is defined (or even type its name) in order to go to it. I can simply click it in the project-wide SideKick.
To be generally useful, a project-wide SideKick would probably need some filtering, but this in itself is an issue for another discussion. What do you think about a project-wide SideKick? The CtagsSideKick plugin, for example, could use existing (project-wide) tag files to generate much more information than it currently does.