Slackerbit.ch

Since I felt kind of bad about breaking old URLs, I dug a little in the mod_rewrite docs and came up with a solution that should make the old URLs working again. (as if anybody cared…)

After some more hacking, I am now releasing version 0.1 of waxpoetyk, codenamed “World Class Fad”.
There’s a lot of debug info printed out on the console, the UI isn’t quite finished, but it basically does what it is supposed to do.
You can grab the tarball here.
Use the code at your own risk, I am not responsible if it eats your hard drive, makes your hair fall out or hides weapons of mass destruction in your closet.

After some hair-pulling, I now have 4.3.0 up and running, and phpMyAdmin seems satisfied again. But now it’s almost midnight, and I don’t want to code anymore, so there

I suddenly get a creative rush and want to code something that I promised someone I was going to write over the holidays, and suddenly, phpMyAdmin on the server has stopped working. I get the frameset, but only two empty frames.
Let’s see if upgrading to PHP 4.3.0 helps…

It looks like the same thing that happened to icicle is happening to blogical.
Both were coded mostly in a coding frenzy, until they got to a stage that they did what they were supposed to do, with minimal error checking and no documentation. Then a few bugfixes, and suddenly, the interest in the program stops, and it just sits there, in a questionable state.
I hope that switching blogical development over to glade will speed things up a little, because, frankly, doing Perl/GTK+ development by hand is rather tedious. But it had to be done once, to get a feel for things.
And I found out, that I don’t really miss a graphical bloggin client. Since I do most of my productive work in xterms anyway, what I really need is a curses based tool. So I downloaded the Curses::Application module from CPAN and will play around with that.

Newsflash: Blogical Development: Code now online

Here are the first screenshots of Blogical:

And all of that on just one cup of coffee.

OK, I found a solution for the CSS problem, I have to position the containing block element, and suddenly, everything gets positioned as planned.
Weird…

This is starting to drive me nuts. According to CSS2, when I use position:absolute:

The box’s position (and possibly size) is specified with the ‘left’, ‘right’, ‘top’, and ‘bottom’ properties. These properties specify offsets with respect to the box’s containing block.

But that’s not happening with Mozilla. The box is positioned with respect to the whole document, not the surrounding DIV-tag.
Aaaaaaaah!

I’ve been working on marrying Movable Type and Mason, and so far, the results look pretty good.
Coupled with some CSS-fu, I might be able to create a consistent layout, which does not look like the default template of MT, even though it’s a nice template.

The power and flexibility of MT have really impressed me. It’s really nice piece of work, and if all goes well, I’ll shell out the 20 bucks for a donation, it’s definitely worth it.