Happy Holidays!

CoffeeKit 0.1.1 is ready for download. Release notes can be found here.

I honestly never thought I’d get this out the door. I’ve been swamped with other bits of life, and I was getting really bogged down in the tooling story.

The tooling story is pretty depressing, as there really is no good/easy/popular path to IDE pickup. There are plans in the works, but I’ve decided to punt on it for now and get this in the hands of people who might have an interest (and better, usable feedback for me :) So while the tooling story is less than stellar at the moment, I hope you can see past it to what I consider to be the real interesting bits of the project - the mashup of:

• iOS Bindings: UIKit, CoreAnimation, CoreGraphics, GLKit, GameKit, StoreKit, Twitter, etc.
• Web Infrastructure: Web Workers, XmlHttpRequest, WebGL, and Typed Arrays, so far

All accessible using JavaScript.

There’s a whole CoffeeKit area to the site now, which will hopefully start looking less like the default octopress theme sometime after the holidays.

Definitely download it and let me know how it goes. If you have any questions or problems, don’t hesitate to get in touch:

• On IRC: I’m toshok on GimpNET in all the #mono channels, and I hang out in #coffeescript on Freenode.
• Twitter: either @toshok or @toshokelectric works. Or you can just add #CoffeeKit to your tweets and I’ll see them.
• Github: If you run into anything, don’t hesitate to file a github issue.
• Email: toshok at toshokelectric.com

In my last post I explained that it is important to handle memory manually for managed classes that correspond to large resources, and made some pretty vague claims as to potentially large time deltas before objects were finalized. I’ll try to clear this up a bit here.

I worked recently on reducing memory usage in a large monotouch app. Since then I’ve been looking at other ways monotouch either makes difficult or actively hampers memory management.

CoffeeKit provides a method for expressing iOS/OSX delegates in a minimal amount of user code, by dynamically creating proxy objects. This process is called “autoboxing”.

warning: these internals posts are going to be fairly heavy with the code blocks and assume a fair amount of knowledge of how javascript/coffeescript work. where things are potential unclear (or very, very cool) I’ll add a lot more text, but (hopefully) I’m not writing a book.

CoffeeKit is where I’ve been putting a lot of my energy recently. It’s a project with a rather simple aim: Let web developers take advantage of native OSX and iOS apis at the same time as they’re able to use the existing browser (and node.js) infrastructure apis they already know.

It’s time to start blogging again. I’ve been far too quiet on this front for too long, mostly because all time spent in front of the computer has been taken up with generating code, or generating posts that have to fit within 140 characters.

And now that I have an interesting and useful project in the works, expect to see a lot about it here.