Glad I could help :)
I'll continue to play with the extension and will post back if I feel I have something more you might find useful.
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Actually, Mark, I realised I didn't 100% answer your question. The above comment describes how I use Visual Studio's ability to dock tool windows (which answers part of your question - whether I'd want it always visible) but the other part (whether a side-docked approach works) wasn't answered.
To answer that, yes I think a side-docked arrangement does work, but you have to be very careful about using horizontal space because you're effectively in a thin vertical strip down the side, and currently I think it uses more horizontal space than is strictly necessary (meaning that I have to allow that strip to be wider than I'd like).
I understand that this is still WIP, and the UI isn't final :), but I thought it was worth giving the feedback anyway.
No, not exactly. Basically, because of my need to move between multiple contexts at once (for example, different projects), I keep a pane docked at the right hand side of my Visual Studio window. That's always open, and has the Solution Explorer, Team Explorer, Properties window etc in a tabbed arrangement. See http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-29-92/1854.Visual-Studio-11-Beta-Full.png
Along the bottom of my VS window, I typically have things like the output pane and Error List, again in an always visible tabbed pane docked against the VS window. When they are pinned like this, I generally try and size the window so it doesn't steal my screen real estate.
Depending on what I am doing, I will sometimes collapse these panes or close them altogether. However, even when I do that, I often want to see both the code and that pane at the same time, for example, I am comparing what I see in the code against something in Properties, or I am looking at an error in the error list and trying to locate the offending line in the code. Clearly, in that situation I will still want to size those panes so they don't hog the screen.
I also don't want to have to dock AutoHistory differently to how I treat other windows. I like to treat things the same where possible.
I think you may need to take another look at the UI layout. If I dock it against the side of the VS window (as you have it in the video) then it takes up a large portion of the screen - if I shrink it down to a reasonable size the snapshot name boxes disappear. If I dock it against the bottom of the window (again, sized so it doesn't hog my screen real estate) then the ticks on the history timeline become almost invisible.
Ah probably should have looked at that first. Thanks!
And well done Kaitlin
Was there something weird with the microphones? Every time Andrew spoke, there was a bunch of background noise (like he was stood next to a noisy air conditioner) and then he dropped out every time someone else spoke.
Graphical Device Interface
Edit: oh, just noticed the note in the timeline