That along with several other factors (Google, I love/hate you) is why I decided to update my resume and forward it somewhere I hope will be a fruitful company for me.  While I’ll admit it does entail a hidden cost that I’d rather not mention, I think I can live with it knowing fully that the alternative is far from amiable.

My interview is today ._. Good  luck to me!

I’ve been doing quite a bit of reading since the beta days so hopefully, the transition won’t be as painful as I anticipated. However, since it’s a new, major release, I guess I’ll go ahead and treat it as learning Rails all over again (in a manner of speaking at least).

Off the bat, I can say that the first few hours of working with 3.0 is an interesting experience. A lot of the changes I have encountered thus far (changes with generators, routing, etc) have been quite intuitive thus far. I will however, save the rest of my expected “rants” until I get into the meaty side of things.

Current dev environment:
ruby 1.9.2p0
rails 3.0.0
OS X 1.6.4

Here’s another artwork of Lily.  I honestly can’t wait to see her in upcoming games/merchandises

Original artist: Kirabagani

source Moetron

Ruby threw a fit and dumped this message:

$ sudo gem install mysql
Building native extensions.  This could take a while...
ERROR:  Error installing mysql:
ERROR: Failed to build gem native extension.

Gem files will remain installed in /Library/Ruby/Gems/1.8/gems/mysql-2.8.1 for inspection.
Results logged to /Library/Ruby/Gems/1.8/gems/mysql-2.8.1/ext/mysql_api/gem_make.out

After some google-fu, I found out that when installing the mysql gem on OS X, you need to point it to where your mysql_config file is placed. Below is the complete guide on how to how to install the mysql gem on Snow Leopard.

• Download your preferred MYSQL version from the community download site. If you’re on Snow Leopard, you may want to install the 64-bit version.
• Install mysql via dmg or compile it from source.
• Type ‘which mysql_config’ on the terminal to locate said config. Take note of this location as we’ll use it on the next step.
• Install the mysql gem with the command below. If the location for your mysql config is different with the one below, use that instead.

   sudo env ARCHFLAGS="-Os -arch x86_64 -fno-common" gem install mysql -- --with-mysql-config=/usr/local/mysql/bin/mysql_config
  

  Note that if you’re using the 32-bit version, you have to use:

   sudo env ARCHFLAGS="-Os -arch i386 -fno-common" gem install mysql -- --with-mysql-config=/usr/local/mysql/bin/mysql_config
  

• And success!

  $  sudo env ARCHFLAGS="-Os -arch x86_64 -fno-common" gem install mysql -- --with-mysql-config=/usr/local/mysql/bin/mysql_config
  Building native extensions.  This could take a while...
  Successfully installed mysql-2.8.1
  1 gem installed
  Installing ri documentation for mysql-2.8.1...
  ...
  

If you are having problems, or have any suggestions, please post a comment.

The problem:

Turns out that datequery relies on an elements ID.  The problem?  Facebox duplicates all the contents of the div you wanted to display and all hell breaks loose.

The solution:

Quite simple actually.

Just use jQuery to replace the element id within facebox at run time.

Here’s the script:

$(document).bind('reveal.facebox', function() {
  $('#facebox .datepicker').each( function(intIndex){
    $(this).attr('id',jQuery(this).attr('id') + '-2')
  });
});

Then just modify your binding for datepicker accordingly:

$(document).bind('reveal.facebox', function() {
	$('#date_filed_for-2').datepicker();
})

And you’re done.

I found this code using google-fu on frenzicmojo.net

Things were great but like most things Java, the going was SLOW but steady.

Then came Rails.

At first, I was really hesitant.  Strong typing (READ excessive typing) was the foundation of a good programming language; at least that’s what countless Java books that I’ve read told me.  So how does a language that puts the fun back in development catches attention?  Well, it might be cliche but…

It all started with Hello World

Nearly all programming languages starts with this old and tired way of displaying the text “Hello World”. Ruby got me interested by it’s simplicity:

puts ‘Hello World’

and that’s it

Of course that really doesn’t say much about the language’s capability but you have to admit that it’s bound to turn heads .

So why switch?

At first it was really curiosity… although I will admit that I did already have Ruby experience prior to this via the gem WATIR (don’t ask why:D) but really, at one point I did ask myself, what’s all the fuss about Ruby on Rails? So I started reading, reading… reading and then read some more until I decided that my first rails application would be the project we had for our Software Development lab subject back in college. The result? I’m in love

I’ll try sharing the project some time in the future but I have some re-writing to do   It’s currently in workprint mode… it’s full of notes, comments and rants right in the source code so.. yeah I need to clean it first .

- to be edited.  Need to sleep for now