Ok, if you are just joining us, this is Part 2 of the IGListKit Tutorial, RubyMotion edition. You should start with Part 1, if you are interested in the mechanics of the Swift -> RubyMotion translation of the starter app. And you really, really should read the source tutorial for IGListKit before you start, because I’m skipping over the boring parts where I can.
IGListKit popped up on my radar recently from a couple of entries in the iOS Dev Weekly newsletter. Digging further led me to the IGListKit Tutorial on Ray Wenderlich’s site (again). While these tutorials are instructive posts to read, I frequently run into frustrating, hair-pulling-out inconsistencies that make it very difficult to go ahead and use this information in RubyMotion. And, as is true of most new tutorials, it is written using Swift, instead of Objective C.
I see two different groups of businesses out there right now with Rails applications that are in dire need of maintenance.
It seems like just yesterday that I finally finished my book, Core Data in Motion. Looking back though, it’s been two years (!?!) since I finished primary writing and submitted the final chapter for my reviewers to critique.
Seems every few months, there is another weird build error that someone is attempting to track down when running
rake to build their project in RubyMotion. The context of these errors is generally unique to the project they are running in, and often surface while compiling an included gem (ie, not in your code), and so it is difficult to Google your way to an answer on Stack Overflow ;-)
About a month ago, I decided I had had enough of Squarespace and all the weirdness involved in keeping my website there.
It’s been 2.5 years since we moved out of Calgary, and down to my old home town of Lethbridge. So far, we have really enjoyed the experience of living in Lethbridge. I moved away in 1982, so it’s been quite some time since I called Lethbridge “home”. Lots has changed. And lots has stayed the same.
Recently came across a discussion on Twitter about how programming was part math and part jazz. The jazz part, of course, is about improvisation. I don’t know, maybe we are all comedians?