settling in

I spent a few more hours today playing with various Movable Type features; mainly cleaning up the absymal default CSS, sorting out the “archives”:, and fixing my RSS feed. Most of the stuff I still want to do falls into the category of “don’t make me edit this in fifty places, you steaming pile”, though there are some archiving limitations that aren’t entirely pleasant.

(I’m also tempted to add some more categories, but then I’d want to go back and reclassify a pile of ancient entries, and that’s just a horrible waste of time. Why am I wired this way?)

I wonder if this thing is at all legible with NS4 anymore. (I also wonder if I still care.)

5 comments to “settling in”

  1. jwz
    entered 30 August 2003 @ 5:04 pm

    I still don’t understand why you’re wasting your time with MT instead of just using LiveJournal… Are you bored and can’t think of anything real to work on?

  2. entered 30 August 2003 @ 5:23 pm

    Something like that, yeah.

  3. mom
    entered 31 August 2003 @ 5:02 pm

    You are genetically wired to not waste time and to immediately notice the stupidity that causes people to waste time… in this case (and in a lot of my sw career) short-sighted implementation. (I am loathe to call it design because that would be insulting to things which have, indeed, been designed – read “planned, thought out”).

    I have the very same affliction. There are upsides and downsides to this. Honest.

    To fix the ‘don’t make me edit this in fifty places’ problem, you could create a script that does the edit for you – could you not?

    Have a good one.

  4. Christopher
    entered 1 September 2003 @ 9:59 am

    I’m using MT too, but I don’t see the deficiencies you’re talking about… care to elaborate?

  5. entered 2 September 2003 @ 11:14 am

    Some deficiencies, off the top of my head:

    • if you want a banner that is not just your blog name, you have to edit the <div id=”banner”> bit in about a thousand little templates, rather than one template module. (I know they have the technology!) See also the “posted by | comments | trackback” line, or the “how to display an entry” blurb, which is faithfully duplicated in every archive template.

    • rebuilding just one file, such as the stylesheet or the front index or the main index archive isn’t possible without going through the template-editing interface. I linked those templates to a file for a reason, see. (The perl mt-rebuild thing doesn’t work either, because it complains about various <$MTEntryWhatever$> tags being in the wrong spots, even though the template in question is bog-standard default-MT installation debris, and even though the template in question rebuilds without so much as a murmur when I do it though the “OK, sure, I give up — rebuild it all” web interface.)

    • (found while making this comment) if you have an <html> tag in your comment, it will be silently stripped from not only the comment as saved, but also the comment-editing box on the preview. Let’s hear it for browser history!

    New things are always sucky, though. I’ll get along.