Tabs, too many tabs.
In VS when coding you can quickly navigate to other code via instances and referances in the code. The trouble is that this opens any unopened files in a new tab, in most medium to large code bases you can end up with masses of opened files. Navigating through the code can also get confusing, you forget what file you started with, what file you are most interested in etc. One idea is using one tab rather than many and the use of a navigation medium , a mocked up example would be as follows.
This uses two mediums from the web world, tag clouds and breadcrumb.
The file cloud (tag cloud) lists every file you have opened, each opening in the tab window. The longer you stay in the file the bigger its presence in the cloud, the less time the smaller (until it vanishes from the cloud). You could opt to keep files present in the cloud to prevent them being removed.
With XmlFile.cs our root for every other file that is associated with the root a crumb is created, this holds any navigation we make between files and allows you to move between the crumb to revisit files. I would see the crumb removing any child crumbs, going from TextFile.cs to XmlFile.cs for example would remove all crumbs.
Like or dislike this idea, let me know?