It's been almost 3 days since the earthquake in Chile which affected many regions of the central-south areas, including the region of Santiago. While things are mostly normal here — besides the many closed stores, the many damaged buildings, unusable highway infrastructure in some places, some fallen buildings, zones without electric power, unstable mobile phone networks and a bit more than 30 dead in the region, the disaster here pales in comparison to what can be seen following the coastal line to the south near the region of Maule and Bío-Bío. There's no way I could properly summarize what happened there, so you'd better use Google if you are curious. Many locations look like ruined, flooded, destroyed battlefields.

And yet, opportunists have pillaged around 16 supermarkets in our region so far; some succeeded, but most failed. There was not enough damage on this region to justify such vandalism. Naturally, Concepción and many other locations in the south are also being constantly vandalized, enough to justify passing the control of two regions over to the army to try to keep the order. They haven't completely succeeded, and the vandals have started fires, given false alarms of tsunamis and destroyed or damaged private and public property.

The aftershocks have been scarce today and they've mostly faded out from our point of view in the Santiago region — that is to say, they haven't stopped in Maule and Bío-Bío and it doesn't let those people rest or sleep for much time. A few stronger aftershocks have reached us as well. Fortunately, they are not anything like the original earthquake.

However, they seem not to stop for me. I've been feeling dizzy since the moment I got out of the house during the earthquake and, no matter if I'm on my bed or sitting on a chair or on the toilet, everything feels the same as in the aftershocks, like a big boat on the sea that never stays still. It's very annoying but I still work on stuff and chat on IRC despite of this.

As sad as this is, and as grim as everything may seem, Santiago is mostly alright and we must move on and continue our lives and help however it is possible. But an earthquake with epicenter near our city isn't a terribly far-fetched possibility since we live next to several (relatively inactive) volcanoes, so let's not relax too much either.

The Wi-Fi WLAN router I use for connecting to the Internet stopped working last night (that dreaded “No route to host”). It's back now, but I'd have liked to post an update yesterday. Anyway, no news is good news, no? Er, well, assuming that the communication systems work, that is...which sadly seems not to be the case for the location of the epicenter, Cobquecura.

It's been more than 30 hours after the earthquake that caught me in the bathroom some minutes after 3:30 am yesterday. The aftershocks, while generally small, continue every 5-90 minutes, and at this point it just feels like one long ride on a bus through a badly deteriorated road — and it's getting fucking annoying.

I'd said that we were okay before. First I was scared when all this happened, and then I was sad after the news. Next, I was worried about the aftershocks. Now I'm just annoyed. Really annoyed.

Nonetheless, I'm not letting an earthquake and a never-ending sequence of aftershocks stop me. There's some groundbreaking work going on here — which you can't see, but I can, and I must say it looks really nice.

Now, could we just stop this madness and allow the rescue groups do something in the most affected locations near the epicenter without having the ruins of the buildings shaken every few minutes by a whimsical force of nature? That's not nice, really. Not nice at all. And you've got our dogs and cats panicking for too many hours a day and a half already. Stop it! I mean it!

As you probably know (if not, Google “earthquake in Chile”), Chile's been struck by an earthquake approx. 8.8 in the Richter scale in the region near Concepción. I live in Santiago, and we have also been affected by this unfortunate event.

(Following comes from this Wesnoth.org forum post)

I am OK right now, but I got trapped in the house during the earthquake (I was in the bathroom and some _really_ heavy objects were in the way to the kitchen, which is the closest way to exit from my bedroom) and thought I wouldn't be able to get out in time. I did (about right at the end of the earthquake, not knowing at the moment if its intensity would continue increasing...), but we are not sure whether the house deteriorated further* or not and do not really believe it'd resist a real earthquake with epicenter near Santiago.

There's a good distance between Concepción and Santiago, so it was about 7 in the Richter scale in Santiago according to the authorities last time I checked — about 10 am via FM radio on the car, we didn't have electricity, tap water or Internet at all until around 2 pm and I fell asleep around 1:16 pm after being unable to sleep the whole night with the strong and continuous tremors that followed. I originally posted this around 6:40 pm.

While everything's fine for us here right now, sadly, other areas of this same region didn't have this luck. Including areas where some of our family lives.

Naturally, everything to the south is chaos according to the news and there are still isolated people in coastal areas closer to the epicenter.

* (To elaborate, this wood house was built on 2000-2001. However, we know that the concrete floor structure wasn't properly finished or secured, there are cracks everywhere that have appeared over time since we moved here; heck, I've even seen grass grow in the middle of my bedroom in 2002. The wood structure of the second floor isn't finished and there are heavy materials left above since a few days ago that made me worry that the house would fall on me when I was walking into the approximate center of gravity in middle of the earthquake, hearing them dancing on the floor (huh) above. All the animals are nervous after the earthquake but everyone's okay and I'm thankful for that.)

***

There are still tremors as of this writing. There was a small one which cut the power lines for 1 second some minutes ago, followed by a stronger one with lots of underground noise. The movement pattern continues being the same as the original earthquake. Internet is flaky.

If anyone's really interested in speaking to me, I've temporarily opened ##shadowm on irc.freenode.net.

Almost two months after the completion of the “Dorset2” template, the website's appearance has changed again! This time it's “Dorset3”, with soft borders and shadows!

A couple of screenshots for comparison:

• Dorset2 r1
• Dorset3

There's not much new besides the aforementioned (or is there?). IE 6 support was surprisingly easier to provide this time — except for a few template glitches in the blog which I haven't yet solved. Anyway, it's 2010 and you don't really want to use a 8-years old browser, do you?

At last, the new layout is ready and deployed. Codename “Dorset2” was completed some days ago but I spent additional time figuring out ways to make a few parts work with Internet Explorer 5.5 and 6. Yes, I know those browsers are obsolete, but IE 6 is the last version that can be installed on Windows NT 4.0, Windows 98 and later (wikipedia) — yes, I know nobody should use anything older than Windows XP for Internet browsing nowadays, hush.

I also had to work around a couple of bugs in Mozilla Firefox 3.5, of all things. Webkit and KHTML-based browsers (Google Chrome understands some KHTML extensions for some odd reason) also displayed some quirks of their own.

Here's a few of screenshots that should display the overall differences between Dorset and Dorset2 (big files ahead!):

• Dorset
• Dorset2
• Dorset2 on Internet Explorer 6 SP1

Naturally, this site is no longer very compatible with IE 5, 6 and 7 because it's using some CSS 2.1 characteristics that are not implemented correctly or at all by those versions. IE 8 works like a charm except for a minor problem with the pre element height rules — which I could fix with a small work-around if I cared enough — but there are also some CSS 3 techniques and/or vendor-specific extensions in use for round borders and text shadows. Nonetheless. I made sure that the site's functionality would not differ between IE 5, 6 and 7, so even if the appearance differs, nothing should work incorrectly.

VirtualBox was very helpful when testing all this stuff. It'd been very hard to run Debian lenny and squeeze at the same time otherwise!

Opera 10.00 showed problems handling multiple children elements with transparent background images. That's a real pity and I hope that newer versions don't have this problem.

The bottom-left corner is not round. There's a good reason for this, and I hope to fix it in the next iteration, some day. For now, Dorset2 is here to brighten and soften your day!

I have recently discovered that the color scheme and overall “look and feel” of an user interface, including web sites, can do a lot with my mood. Two days ago, someone on freenode.net's social channel (#defocus) linked to her blog, which has a black background — that's not bad or unusual, but I noticed that the dark scheme affected my mood making me feel slightly upset for a few minutes. I have no idea if this is just another quirk in my brain's functionality, or normal.

Nevertheless, it does sound like something I could use to my advantage, and to please my somewhat loyal reader (hi Espreon!).

Codename “Dorset2” has been a work in progress since last November. I had experimented with round shapes, box shadows and gradients, using CSS 2.1 and background image tricks, but I didn't get very far due to Dorset's inflexibility and design flaws at the PHP level; basically, I'd have had to edit every single page to adapt them to the new scheme, and that'd be boring and tedious. However, a few days ago, “Poison Ivy” was completed, enabling me to share the basic and simple functional code with three websites, or document sets, so to speak:

• The Wesnoth-UMC-Dev website, (now codename “Kalari”);
• This website (codename “Dorset”); and
• Dorset2, not yet online.

Ivy's design allows me to simply “flip the switch” to convert every web page in my laptop's test Apache instance to use the new scheme, thanks to a extremely primitive, yet effective template and configuration system. A couple of lines of code:

define('DORSET2_ENABLED', TRUE);
define('SKEL_BASE_PATH', DORSET2_ENABLED ? '/dorset2' : '/dorset');

By toggling DORSET2_ENABLED, I can test my code with the old and new templates and stylesheets as necessary, without editing any of the actual pages!

I deployed “Poison Ivy” on the online site last night, so this is already theoretically possible in here... except that the Dorset2 files are not finished or online yet. I did resume my work on it some days ago after finishing Kalari, though.

If a dark scheme can have negative effects on my psyche, what could bright (but not too bright), soft colors and shapes do for me? Basically, Dorset2 aims for a relatively simplistic look, with soft shapes and colors using gradients and round corners for some elements. The color scheme is also slightly brighter than Dorset for some elements; but the shapes are what matters here. A box with round corners and no solid border makes the contents look soft to me; compare current Dorset which uses (way too many) rectangular boxes with solid and dark borders everywhere, inside and outside the main body.

Here's a (rather big) screenshot of Dorset2. Apologies for the admittedly awful rendering of Verdana Bold; that must be freetype's fault.

• Dorset2 (PNG screenshot)

Since it's a work in progress, I have not gotten around to tweaking the CSS to make it work as best as it's possible with Internet Explorer. It doesn't look too bad at first glance, but it gets worse at the bottom (not pictured) thanks a gradient background trick that makes some text disappear at random in IE 6 SP 1 — and for whatever reason, this doesn't affect IE 5.5 or IE 6 SP 2 and later. I figured that I'll make my work easier for now if I write rules to disable certain decoration elements with these broken browsers.

Hopefully this gets finished soon.

It took me much less time than I expected to put the new layout of the Wesnoth-UMC-Dev website together. Observe.

Okay, that's basically because most of the design was already made long time ago, in the form of the site's earlier incarnation, codenamed “Soradoc”, which looked rather busy and useless with the sidebar and other design elements. The new design, “Kalari”, removes the sidebar, clears the site banner a bit, and blends the site with Wesnoth.org as far as appearance is concerned. It's not the same design, but it's similar — that should be a good thing considering the purpose of Wesnoth-UMC-Dev.

That site also had a Blosxom-based blog, but I removed it since nobody was making actual use of the space.

The greatest thing about all this is that most of the PHP, “Poison Ivy” was finished in 1 night, while the rest took me just a few additional hours. Now that Poison Ivy is completed, I can reuse its code for the next incarnation of this very website and blog.

It's all for teaching some web design and programming basics to myself, really.

(No, not that one.)

There are many content management systems out but all of them seem to require some sort of database server and occasionally sacrifice flexibility in favor of ease of use.

This is why neither this site or Wesnoth-UMC-Dev's use one of those nifty software packages although they still use PHP. The latter website uses a bunch of ugly code codenamed “Soradoc” which has the actual XHTML layout embedded on it; the CSS stylesheet is also codenamed Soradoc and it's derived from “Glamdrol”, the Wesnoth.org wiki skin by Ettin; and “Dorset”, which is Soradoc's immediate ancestor, used on this very personal website — which in turn uses PHP code derived from the current incarnation of “Soradoc”.

Enter codename “Poison Ivy”, which is basically the same thing as Soradoc/Dorset, except written from scratch, much cleaner and more flexible; in particular, the XHTML layout and the site configuration are no longer part of the engine's source code which will allow me to share that among both websites more easily. It also introduces seamless support for document compression, which may be useful for my personal website.

Ivy is mostly finished, but I'm now busy reworking the Wesnoth-UMC-Dev site's design under a secret project, codename “Kalari”. Maybe once I'm finished with that, my next web project will be bringing umcreg (codename “Thoria”) to life.

(Okay, it's not a secret anymore. Dammit.)

Thanks to this KDE 4 feature, I no longer need to preview whatever zip, rar archive or tarball I download to check if it has a suitable structure for uncompressing directly into a separate dir without help. Awesome.

(Yes, I admit it; this is a filler, just for the sake of breaking my habit of not posting anything on Sundays.)

Finally, it's January! The New Year celebrations are mostly over and fading away, and people all around the world are going back to regular business and everything should be back to normal in a few days.

I used to be fond of the Christmas and New Year celebrations as a child as I could spend time with my family and eat delicious food. That is not the case anymore, because, even if I still live with my parents, there's no longer a sense of family here and we only want to throw sharp stuff at each other. There's not much enthusiasm by the end of the year anymore, and phrases such as “Merry Christmas” and “Happy New Year” (in Spanish, though) are truly unheard of in this house. Recent disagreements amongst us indicate that this is not going to be a good year for anyone. To add insult to injury, one of our cats died in a rather tragic and violent fashion on December 22th — it's a tradition here that one or more pets must always die in December. While we have many of them, the first ones to die are those whom we are most attached to.

To mark the actual start of 2010 (as far as the Gregorian calendar is involved, of course), there was a black-out on the area about 6 minutes 7 seconds past midnight, which left us with no Internet or tap water until around 1:50 AM. What a great way to start the first day of the year.

(In case there's doubt — I assure you, I'm not making any of this up.)

But there's still some hope at the moment. Some days before Xmas, my creativity returned from its long, chaotic journey and my Wesnoth add-on, After the Storm (sequel to Invasion from the Unknown has seen steady progress and two new releases were published in less than two weeks. Keep in mind that this add-on had not seen any public releases for almost a year.

After the last released version of AtS (0.2.1) including 5 of 12 planned scenarios in Episode I, there has been more progress in the Wesnoth-UMC-Dev repository. Just yesterday, I finished the two-part cutscene that is the sixth scenario of Episode I, one of the most important points of the plot's development, in which two forest elves finally make contact with the desert/Quenoth elves.

I won't be able to release AtS 0.2.2 or 0.3.0 until scenario 7 and the next cutscene (appropriately named “Resolutions”) are finished, since I'd be teasing the players otherwise. However, those who are really interested on it can always check AtS out from the repository's trunk into their <wesnoth preferences dir>/data/add-ons dir and play using the latest development version of Wesnoth:

svn co https://wesnoth-umc-dev.svn.sourceforge.net/svnroot/wesnoth-umc-dev/trunk/After_the_Storm

It's really exciting to work with several plot elements from quartex's Under the Burning Suns in new, creative manners — kind of like Fanfic production taken to a new level using the power of the GNU General Public License (version 2 or later!). Nevertheless, I am fairly sure he deliberately left much details unresolved in the original campaign, and that he'd fry us (Espreon, AI0867 and me) alive if he found out what we are doing with his story.

One week before Xmas, the Wesnoth.org forums saw another upgrade on which Turuk and I worked hard and quickly to improve forum usability by not only upgrading the codebase to phpBB 3.0.6, but also tweaking the templates, adding modifications and a couple of new forum styles to take advantage of the new features implemented by the phpBB devs in this iteration of their software. The main points were highlighted in this forum post (originally a Global Announcement).

This year should also bring us a new stable series (1.8) of the Battle for Wesnoth game itself. There are currently some problems delaying the first Release Candidate and getting us flooded with generic beta releases, but the developers in charge of them will (hopefully!) find a solution so we can get 1.8 released and trunk “thawed” soon, to work on new features and allow new code contributors to join the project. As for me, I can't wait for the new stable series — development series players seem to be scarce and the new versions of IftU and AtS are receiving little feedback on the forums because of this! I suppose Multiplayer content authors are similarly eager to get more fresh meat to play their add-ons.

I also recently talked about how I can finally suspend my laptop to RAM using Linux, and run some basic OpenGL-based software without crashing or destroying anything. That's something I didn't expect to be able to do in the near future, so the Mesa, libdrm and X.org radeon driver developers have my thanks for improving the Linux experience of those unfortunate enough to own onboard ATI graphics controllers!

In summary, as usual, a new year brings good and bad news. I guess it's up to us to take what's good and fix what's wrong. So, anyway (although I guess it's pretty much unnecessary at this point): happy New Year and have fun!

(The Abridged version: let's get this party started already and kill some spambots! GAAAA!)

The X.org radeon driver continues to be very stable with Mesa 7.7 and a newer libdrm (2.4.17), and now I'm running the Linux kernel 2.6.32.2. When building it for the first time, I enabled ACPI S3 suspend (to RAM) support in the configuration because I had initially planned to try it with the kernel mode-setting drivers (that part of the plan got scrapped when I found out that the KMS drivers are not intended to work well for 3D yet) — so, after rebooting, I noticed a new button in the power management widget in KDE's panel.

A shiny new button... S3 suspend had not worked for me during all this time because uswsusp and the kernel were unable to bring the keyboard, touchpad and screen back to life when resuming normal system operation, so I had disabled support for it in the configuration for many kernel versions for fear of accidentally suspending to RAM instead of disk, and losing my current work as a consequence.

However, the power of Debian Squeeze's current hibernate script package (?), the vanilla+TuxOnIce 2.6.32 kernel, and all the new graphics drivers, seems to do miracles. Suspend-to-RAM works at last on this laptop! After a year of fiddling with build and run-time kernel configuration and tools! (And this is why it's a bad idea to run Linux on a brand-new laptop; but I knew it was going to be like this and still went ahead, mind you.)

This means that the ATI mayhem is over (well, except for a little problem), and now that I can run some of my favorite OpenGL-based software, suspend to RAM and disk safely and run KDE 4, my mission is complete my work here is done. My local builds of this software are my very own Christmas gift this year.

Yays for the open-source community! \o/

The End.

...OR IS IT?

Freenode's staff and a group of users have been busy testing ircd-seven, the ircd which will eventually replace the aging collection of ugly hacks known as hyperion-ircd. So far it seems I've been the only one who's found and reported bugs in channel management code (account bans + forwarding, in particular), which is a pity; we need more testers!

Occasionally, the server instances get restarted and some people complain.

I think I cannot complain, because I just got my own 10 seconds of fame. It's a pity that I didn't have a better one-liner or a larger audience for the occasion!

<@shadowmaster> eh.

(And if you don't use freenode or IRC at all, you won't understand any of this.