Cluster-Proto
cluster-proto is up and running, at least across-my-own-browsers functional. I have a sneaking suspicion that it will give Safari a run for its money, though.
I guess a KDE LiveCD would be the way to check, since they’re both on KHTML, or what was KHTML, or stuff that was KHTML that got merged back in after a sort of confusing and ire-producing communications issue with Apple, or … whatever.
Notice the red text and opaque right pane (“information” panel, if you hack the source) upon clicking (I call this “freezing”). This should transfer to another fragment if you click on one while another is “frozen.” The info box should also line up with the top of the current fragment when it is active. It should fade when the mouse is removed from it.
The fact that my DHTML is pushing us into paragraphs means Textile should work as a code generator, which is something that excites me greatly. Textile automatically creates <p> tags around all linebreaked text, including one-line text, so the model is forced that way.
This is why I wanted to do the front-end first, as I thought it would have more influence on the back-end than vice versa.
I’m getting excited.