Archive for February, 2008

If you haven’t looked at the Ext JS framework yet, you really ought to.  We use it extensively at work and we are quite happy with it.  I just wanted to point out that the 2.0.2 version of Ext has come out.  This release was mostly related to the new Adobe AIR 1.0 that was recently released.  Currently at work we don’t do any AIR related things, but we’ve looked at dabbling in that field in the future.  That being said, there are a few custom Ext components that were put in the Simple Tasks  example that came out with this release.  The TreeList, custom grid columns, and a switch button are all used in Simple Tasks, but their code could very easily be copied from that example to be put into any 2.x-compatible code.

Have you ever seen this error before when working with CURL:

“Protocol https not supported or disabled in libcurl”

Yet, you know that https works. Or even:

“Protocol http not supported or disabled in libcurl”

And you think, “What the hell? That’s basically what CURL is for. Why would HTTP not work!?”

Try wrapping that echoed out error message with <pre> tags:

Protocol  https not supported or disabled in libcurl

Notice anything?

There is an extra space before ‘https’. Make sure that when you do set CURLOPT_URL, you don’t put a space before the http, CURL won’t know what to do with it.

I recently got a new MacBook Pro and am finally starting to get the hang of it.  One of the irksome things I noticed was that in terminal, my .bashrc file wasn’t getting sourced initially.  I could source it myself, but that seemed a bit ridiculous.

The reason this was happening is that bash in terminal was looking in the .profile file, not .bashrc.  The simple fix here is to tell bash to look for .bashrc when it looks through .profile.  Here’s the simple bit of code to do this:

if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi

If you’d like a little more information about what you can do with .bashrc, take a look at this post I did a while back about my .bashrc file that I use.