dragonwriter said it here but the actual reasoning went something like this: 1. I need to add some documentation and explanation. 2. I might as well document

dragonwriter said it here but the actual reasoning went something like this: 1. I need to add some documentation and explanation. 2. I might as well document the different parts using screenshots since the elements are visual. 3. I might as well make videos (or gifs) to show what the actions do. 4. I might as well make the video interactive to drive home the points that the user can customize the interface to look like whatever they like. (This incidentally also perpetuate the joke about this program being meta.) If this were Javascript, I think the guided tour wouldn't be an issue (but I understand that it isn't and the further step with virtualenv makes it even less approachable). There's also the issue of time. That I'd probably only make one of these, at least at first. I chose 4. Maybe it was not the best choice. I'm still trying to think of a good way to also add 2 or 3 but my gut feeling says that people are less likely to try the interactive version if I add that. I suppose this is the sort of thing that needs testing to find out. Also, most visual tools have a clearly define "this is the toolbox" and "this is the stuff the tools apply to" so some though is needed to be able to show that there isn't even such a division. For example the default first screen is probably really confusing to look at on its own (so the natural next thing to ask for it an explanation of what the viewer is supposed to be looking at!).