Now that I've got two friends messing around with Shortlog, my minimalist blogging engine (crazy, I know), I've come to the realization that I need to make it easier for people to access/use my software. I need to make it less tied to my particular setup, more easily configured, and better-documented.
Then I realized that this applies not only to shortlog, but the rest of my projects as well. And the first step in using someone's code is obtaining it.
So here you go. I've gone and organized a few things enough to get a decent-looking gitweb page up to make the source available. Documentation and modularity will come in due time.
Another interesting thing I noted today: most of my computer usage is a giant hierarchical organization of data segments. Multiple desktops play home to multiple tiled windows. Most of these windows are either:
While there are also occassionally chat windows (with several tabs) or the one-off LibreOffice window or file manager, this is my most common interaction with my computer - finding and selecting the desired context to interact with.
This sounded remarkably like Ben Schneiderman's Direct Manipulation Interfaces. To make context switches cost less, I (subconsciously) put likely neighbor contexts next to each other. I may set rules, like "desktop 1 is for communications, desktop 2 is for OpenKinect development." The catch here is that some end nodes (application windows) fit into multiple places in the heirarchy.
My question is then: is there a way to keep the benefit of being able to keep such rules for quickly finding the relevant context and still preserve relative context nearness?