dan.verweire.com

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.