Exception in thread "Animation Thread" file:/*/.rvm/gems/jruby-1.4.0/gems/ruby-processing-1.0.8/lib/core/jruby-complete.jar!/META-INF/jruby.home/lib/ruby/site_ruby/shared/jruby/openssl/autoloads/ssl.rb:8: OpenSSL::SSL requires the jruby-openssl gem (LoadError)

After manually installing and removing the jruby-openssl gem, it still didnt fix the issue. As it turns out, the latest version, 0.0.6 wasn’t playing nice. So gem install jruby-openssl -v=0.0.3 did the trick. Just in case someone out there comes across similar issue. Also, since Ruby-processing requires rubygems to be installed as jruby gem, I decided to use rvm and installed jruby from it and installed the processing library and gems in that jruby environment. That way you won’t have to do some custom stuff for loading gems as mentioned here:

http://wiki.github.com/jashkenas/ruby-processing/using-rubygems

Quick Update: After digging into the source code, I realized I could force it to use system jruby instead of the bundled one that comes with ruby-processing using –jruby flag. And that also fixed the jruby-openssl issue and dont have to use old version to make it work.

1. Gluing: I must admit, I had a really hard time getting this rubber to stick in, i used the same glue that i have been using all this time, tibar clean extra. The problem was the rubber had a distinct semi-dome shape when I took it out of the packaging, (the dome shape that super glued rubbers have). And that was even before applying any glue to it yet. I also made the mistake of not applying enough pressure on it after gluing and attaching to blade I guess and the internal tension of the rubber took over, I went to the play next day and saw part of the rubber had already come off. Now its better after regluing and putting it under books for few days. Here’s how it looks now
2. Looping:   I felt this rubber definitely has more kick to it, compared to the Sinus. Looping, especially over the table was pretty easy and forgiving, it has a lower throw than tenergy 05 and I got used to it within minutues really. Since I was using 2.0 version I can’t say it was faster than tenergy05 for sure but it definitely felt fast. I think it has close enough spin that tenergy 05 generates, not higher though.
3. Serves: My serves were generating pretty good amount of spin whenever I wanted to, again, I wouldn’t say more than what tenergy05 was doing though.
4. Pushes: pushing/over the drops were pretty consistent as well
5. Blocking: I felt this is one dept where I liked it better than tenergy, because of lower throw blocking was more easier and consistent.
6. Overall: I think this is a pretty decent rubber for offensive game, but doesn’t warrant the price tag it carries. Tenergy series was quite pricy at first too and came down a bit later…hopefully tibhar will do the same..but for those who doesn’t like the throw of tenergy but want a similar spin and speed, I would say this rubber is definitely worth a try.

Recaptcha is not defined

So comparing what could be different between my dev environment and the staging environment, I saw the portion of the app where recaptcha was failed a secure page. So the fix is rather simple:


<%= captcha_tags(:ssl => true) %>


Furthermore, just to be on safe side, in other portions of the apps as well I was calling this captcha. So i added a helper method like this:


def recaptcha_tags_helper(options = {})
options.merge!(:ssl => true) if request.ssl?
recaptcha_tags(options)
end


UIImageView *image = [self findImage:touchLocation];

image.methods

Then I recall this is not ruby, Of course, there’s the quick ‘Jump to definition’ feature of Xcode that helps a lot.

As far as the convention quirks goes, it took me a while to whether use BOOL values as YES/NO or TRUE/FALSE or true/false. I switched back and forth for a while going by forums and what not, I was doing things like:

valid_move = YES

if valid_move == YES

Until I found a sample code from ADC, and they use it like:

valid_move = YES

if (valid_move) //How convenient, why not just set value as TRUE, I still don’t get the YES/NO macros for BOOL. Actual value stored is either 0 or 1 of course. Oh well, if it’s coming from sample code, I might as well follow the same convention. The challenge so far has been just getting used to the syntax and getting used to convention more than anything and also brush up on C pointers.

Although there are few blogs/tuts on iphone sdk and objective-C, I think the sample codes from ADC are the best source to learn what the SDK has to offer and how to use all the libraries. Besides getting hand of coding style, convention, just running the sample codes locally gives a better understanding. I was tempted to buy a iPhone app book from pragmatic programmer’s but decided not to. The ADC guidelines, code samples, floating tuts and my objective-C book should keep me busy for a while.