inordinatemind.com » programming

JavaScript headache and code forensics

ice5nake — Wed, 28 Mar 2012 20:06:00 +0000

Mixing modernizr with cufón produces sadness for IE8 on Windows XP. More specifically cufón 1.09i and modernizr 2.5.3 create a combination that produces weird double lettering.

I reported the issue to the cufón dev, https://github.com/sorccu/cufon/issues/239

Found the relevant issue on the modernizr project, https://github.com/Modernizr/Modernizr/issues/534

And followed it to the root issue on the html5shiv, https://github.com/aFarkas/html5shiv/issues/54

From there I went to https://github.com/aFarkas/html5shiv/commit/9aa5bcdca367fd86ec5d5b73ca4d95e032a0f502#diff-1 and figured out what exactly I would need to fix the problem.

Thinking I could ditch modernizr and just use the most up to date html5shiv at http://code.google.com/p/html5shiv/

JS Loading is Pretty Sweet

ice5nake — Tue, 06 Dec 2011 15:09:25 +0000

I’ve begun working with http://headjs.com to do JS loading. Why do JS loading? See: http://headjs.com/#theory

There is a somewhat broken, but easily fixed, WordPress plugin to use it. Drupal’s got a plugin for it here. Haven’t tried the Drupal plugin yet but it’s on my list. Even without a plugin the API seems simple and intuitive.

Learning Android Programming

ice5nake — Tue, 14 Sep 2010 13:27:42 +0000

I’ve been learning the Android SDK. My goal is to create a simple application to put on the Android Market. Also, I am hoping to get the early access to the developer’s program for the Notion Ink Adam tablet.

Android SDK has lots of pieces to it. It’s been slow going learning it. Especially since I was pretty new to Java. And especially since I was used to dynamically typed languages like Ruby and PHP. I’ve stuck it out though and I am now making good progress.

The next planned step is to start developing directly on my HTC Incredible rather than using the emulator.

Fragment Caching with Rails.

ice5nake — Wed, 02 Jul 2008 16:37:26 +0000

I’m going to stick to using string paths, as opposed to hashes, for fragment caching (storing the page in pieces basically). Especially when you have multiple parameters outside of the basic controller and action. I am using a per page parameter as well as a page parameter. Lots of cached fragments to manage in those cases.

It’s been rough disecting exactly how Rails manages cache. I had the exact same hash going to my cache, expire_fragment, read_fragment functions, but expire_fragment wasn’t working. I suspect routes are factored in there somewhere and I don’t have the time to figure it out exactly.

Lately I’ve been learning a lesson. That lesson being, it’s nice to do things entirely the correct way, but sometimes you just got to get more done.