dan.verweire.com

I hereby dedicate this pitcher and its estimated contents to nodejs v0.6.9, the re-introduction of dgram multicast/broadcast and all those who work on nodejs and other open source projects that rock this world.

Ingredients

• 1 20oz can of sliced pineapple including juices
• 6oz Bacardi Superior
• 3oz Bacardi 8
• 2oz Cointreau
• 2oz Parrot Bay Mango
• 3oz Coconut Syrup
• 2oz Grenadine
• ice

Directions

• Combine the pineapple and liquid ingredients into a blender.
• Fill the rest of the blender with ice.
• Blend until smooth.
• Fill pint glasses with mixture.

Optional Directions

• With your own pint glass…
• Add 1oz Bacardi 8.
• Add 1oz Cointreau.
• Stir with spoon.

I have the slightest of recollections of sleep walking in my life. There have been less than a handful of occasions and all during my childhood. I do, however, have many memories of lucid dreams. I had one such dream a couple nights ago…

I was making Frogger t-shirts, it was 1989 and I was nine years old. This alone was the trigger to my lucid state. Everyone knows that Frogger was released in 1981. So, why would I be creating paraphernalia for an 8 year old video game? It wasn’t cool to have clothing for old school eighties games yet. Maybe pong though.

As I came to realize that I was dreaming I took control. I decided that I would use this opportunity to figure it all out. Maybe I would be able to tap in to all of my brain power and find the answer to all my problems. What is it that I need in my life? What will make me infinitely happy and healthy. Well, I found out. Unfortunately, I don’t recall the events that took place that led to my answer, but that doesn’t matter. I had my answer and I needed to see if it truly existed.

My dream merged with reality as I rolled over in bed and grabbed my phone. I struggled to turn it on and draw the unlocking pattern. I hammered out the search phrase that would hopefully change my life into the Google search widget with the most care I could muster at 4:17am. There were millions of results but the top four were not relevant and I went back to dreamland.

I woke a few hours later to the sound of the alarm on my phone. I turned it off and proceeded to activate the web browser with every intention of checking Slashdot. At this time I realized the weirdness that had happened earlier. There were the search results for what would not change my life. The phrase still read prominently in the search bar: “prozac 9″.

I recently created a bootable usb thumb drive for installing Kubuntu on different computers at work. I also planned to to use this device as a live system for the rare instances where I need another Linux system in my office to test things. Creating the bootable drive was a piece of cake with the usb-creator-gtk package.

Today I wanted to test out some cool stuff like dns2tcp, ptunnel, stunnel and ppp. I pulled out my thumb drive, smacked it into an available machine and booted off the cool little guy. I quickly found that I needed to install more packages and as I did, I ran out of space in the 128 MB that I had allocated for “extra space” on the 4GB drive.

Yeah it was obviously a dumb move to only allocate 128 MB for my /home and customizations. The fun thing about Linux is where there is a stupid mistake there is a chance to learn something new and do something fun, if you like that sort of thing.

As it turns out usb-creator-gtk creates a file in the root of the drive called casper-rw. This file is an ext3 filesystem image and is what contains most of the writable data in your live environment. All I needed to do to get some more space (provided that drive wasn’t physically full) was to enlarge this file and then resize the ext3 filesystem inside the file to be able to use all of the newly available space in the file.

Oblig Warning: Only do this if you understand what these commands do and agree that they are the best course of action for your situation. Use at your own risk.

The following steps where taken from a computer which was running Kubuntu Karmic. You must not be running in the live environment on the usb device when doing this procedure.

According to http://forum.kde.org, here are some easy steps to make FireFox integrate better with KDE:

1. install your distro’s gtk-qt-engine
note: depending on how far your distro is with kde4 integration this package may either be called gtk-qt-engine or gtk-qt-engine-kde4

2. change your Firefox theme
If you use the default KDE oxygen theme install the oxygen theme for Firefox from here: https://addons.mozilla.org/en-US/firefox/addon/7962

3. change the appearance of the file selector:
type “about:config” into Firefox’s URL bar and type “platform” into the display filter below. Make sure that the value for

    ui.allow_platform_file_picker

is set to false

4. Additionally, to fix buttons and checkboxes, install package gtk2-engines-qtcurve. Now open KMenu->System Settings->Appearance->GTK Styles and Fonts and set “Use another style” (under category GTK Styles) to QtCurve. Save it and restart Firefox (copied this straight from post #5 – many thanks!)

5. For downloads – you may want to consider installing the flashgot add-on. It lets you use Kget as a download manager.

Also of interest is https://addons.mozilla.org/en-US/firefox/addon/207, a FireFox plugin which may help choosing the correct application to run when downloading files.

I love JavaScript. A lot of people hate it and think that it is a horrible language. It has it’s faults for sure and this series of videos featuring Douglas Crockford of YAHOO! goes into great length describing the downfalls and advantages of JavaScript. This is a very blunt and to the point overview of the language, not for the faint of heart. It starts with a brief history of the language and how it got its crappy and misleading name.

Douglas Crockford: "The JavaScript Programming Language"/1 of 4
Douglas Crockford: "The JavaScript Programming Language"/2 of 4
Douglas Crockford: "The JavaScript Programming Language"/3 of 4
Douglas Crockford: "The JavaScript Programming Language"/4 of 4

The Advanced section delves into the details of prototypal inheritance and other advanced features of JavaScript.

Douglas Crockford: "Advanced JavaScript" (1 of 3)
Douglas Crockford: "Advanced JavaScript" (2 of 3)
Douglas Crockford: "Advanced JavaScript" (3 of 3)

While developing a JavaScript GridLayout tool at work today, I ran in to a tough spot while traversing tables with jQuery. What I wanted was to only work with the TR and TD elements within the parent table and not any nested tables. At first, I was using code like this (see HTML later for an example of what I was working with):

But the problem with this is that both calls to the ‘find’ method would return all TRs or TDs that are decedents of #myTable, no matter how deep. I could have used a selector that would have found the tbody (the first child of the table not shown in the markup but inserted by the browser) and then found all of the TRs that were children of that and so forth. My issue with that is that I’m not confidant that all browsers insert the tbody element. I’ve read online that they are supposed to, but for real, who knows? And I don’t like programming browser-specific stuff.

At any rate, the easiest way I found to accomplish this is to pass the table.rows and rows.cells collections to the jQuery constructor ala:

And boom, no nested tables return. Wonderful. At least I think that’s what I did. It’s been a few hours now….

The HTML:

I was trying to compile XBMC from the subversion repository and was receiving an error when it got to the Goom visualization. Unfortunately, the exact error is beyond my terminal history but can be found in a thread on the XBMC forums (http://blog.xbmc.org/forum/showthread.php?t=45463&page=2). In that thread there is this dirty work-around:

sed -i xbmc/visualizations/Goom/goom2k4-0/src/goomsl_yacc.y -e 's/case FLOAT_TK/case 264/'
sed -i xbmc/visualizations/Goom/goom2k4-0/src/goomsl_yacc.y -e 's/case INT_TK/case 263/'
sed -i xbmc/visualizations/Goom/goom2k4-0/src/goomsl_yacc.y -e 's/case PTR_TK/case 262/'

It worked for me. An additional note of interest when compiling XBMC is if you want to install to a non-standard location,

./configure --prefix=/path/to/destination

DOES NOT WORK. You have to use :

make install PREFIX=/path/to/destination

So, I accidentally installed it on top of the version I received via apt-get from the xbmc ppa. Shouldn’t be an issue.

So funky.