I’m not testing the site as compulsively as in times past, but it really seems like the uptime on Gilford has improved. I also check the Current Issues RSS from Textdrive and Gilford hasn’t made the list in some time (when I check it). This makes me happy. I almost wish I was unhappy so I could justify a more complex hosting package, but that’s obviously not the case.
I’m looking forward to more Cluster 2.0 work tomorrow.
It’s a pity that the color wheel dictates Bert’s level of terror to be less than that of Ernie’s (see bottom of left panel, thanks go to Josh). Bert is clearly the more dangerous of the two.
I wish there was a Code Black for the Count. Not that I’d ever want to get there…
This required some language editing (done creatively), but this is a song I cited in conversation today. However, it should be emphatically stated that it has nothing to do with the wedding in question. In fact, I was just talking about Emo and stuff like that and this came up. So… yeah, there it is. Or rather, here it is. Whatever.
Edit: Reading through this, I realize how awful and repetitive it is. I feel I must now say that I was actually citing the music video, not the song itself. The video is kind of cool, with a little non-special effects cast-member switcheroo at the end and junk like that. In fact, I cut the thing just to the first verse because it’s so bad. So, you can go look it up if you want more.
Still Editing: It’s catchy, though. If you don’t pay attention to the fact that they repeat every line. Twice.
This is Actually a New, Different Edit: Easter Egg alert. No further comment. — I Write Sins Not Tragedies by Panic! At The Disco
Oh, well imagine, as I’m pacing the pews in a church corridor, and I can’t help but to hear, no I can’t help but to hear an exchanging of words: “What a beautiful wedding! What a beautiful wedding!” says a bridesmaid to a waiter. “And yes, but what a shame, what a shame, the poor groom’s bride is a
I have to say, Cluster is just a raging success. I’m excited to round out a 2.0 with more features and more fun. Hopefully, we can start using a new version for a fresh story in the near future. We’ve killed off so many Muppets by now the current story must be ending soon!
The language factor is very funny to me, and it provides a novel extra contrast to all this irony and parody we’re spinning. However, I feel, as the host (somewhat accurate even in this context), responsible to communicate a somewhat post facto warning to any readers not so bemused by this “color”: these gangsters get no nicer as the story draws to a close! But it’s all in good fun.
I’m not sure what the possible subject-matter of a new story might be, if it should be more serious (or, at least, more “realistic”), or if another absurdity should be selected and developed. I’d be glad to receive comments here.
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.
Well, I had to put in a Web 2.0 reference. Who isn’t these days?
It turns out that I am currently carrying around on USB flash memory a heavily-under-construction (read: currently utterly non-functional) AJAX prototype of Cluster 2.0. It promises to feature real logins, comments on fragments, RSS, and Textile fragment formatting (MAYBE… recent investigations suggest difficulties).
I’m using Dojo as the DHTML/AJAX framework, which is painful and informative at the same time. I haven’t dealt with documentation this bad since I tried to get a DHCP server running on something like SuSE 7.0 about three years ago.
There may also be some kind of timebomb mechanism, but every time I think of a concept it seems very, very bad to me in practice.
