Alan’s Kiloblog

I’m not inclined to write in the Think New Orleans blog these days. I don’t like the theme. It’s not as nice as the look of the New Orleans Wiki. What a difference a theme makes. I do need to practice what I preach, and frequently update Think New Orleans.

I am lost without a goal.

What is the goal of the Think New Orleans weblog? Do I want to write about neighborhood planning? I spend so much time on that matter, it seems like a place to put it. Do I want to write news from the neighborhoods?

I’ve focused on using the Think New Orleans blog to organize Think New Orleans. This has been the place where I’ve reached out to people, posted questions and sought advice. I’ve written about my take on what goes on in New Orleans, and I’ve written my take on information systems and civics.

It seems that Think New Orleans should focus on promoting New Orleans information systems.

Need to fix that theme. It’s a battered Kubrick. It will encourage me to write more.

Somehow, I feel that all people need a high-volume weblog somewhere, where they can post whatever, get the writing out of there system, and tighten it up later. That’s what the Kiloblog is about. Maybe I’ll go and scratch out some pleadings there.

Test

I’m installing a LiveJournal Crossposter for George Williams.

There is a Mediawiki backup script for that purpose.

Removing creational patterns, that’s what I’m doing. In Relay, I have a tight creational pattern that makes a resolver immutable. Later on, I decided I’d like to reduce the configuration patterns in Varsity, and wanted to specify protocols in the transforms. I made it so that you could add a protocol to the resolver. Thus, a relay could add the protocols that it will need to run.

Unfortunately, I forgot that a relay is built by an XSLT script. The XSLT script needs the protocols to create the relay. Then I remembered that there is a boot relay that gets things going. I decided to add my protocols there. Now I wonder if it’s right.

The boot relay is a relay that creates a document and runs it as a relay. The relay runner is at the very end of the relay. It cannot be anywhere else.

This makes me think “push”.

The URI resolver in relay will evaluate a URI by running a boot relay associated with the authority of the URI. It returns a document generated by executing the relay. This makes me think “pull”.

Now I’m considering making the authority mappings something that you can configure in a varisty script. If you add the ability to set variables, you now have a way to create namespaces, and to create configurable modules.

Quite obvious, but I can use the newsletter as a follow up device, to teach attendees tips and tricks, and to show them new features.