Boxer

Developer diary: plans and progress reports.

Bombs away Sunday 13th December 2009

That's right boys and girls, the sourcecode for Boxer 1.0 alpha is now available on Bitbucket. There's also a ready-to-roll universal binary too, if you're squeamish about building stuff yourself. Check out the previous blog post for an idea of what's new in Boxer 1.0.

What you will need:

How to build it:

How to run it:

Caveats:

As always, give it a try and tell me what you think in the comments!

Commentary

  1. Excellent - I can play Harvester! :)

    Many thanks!

  2. Congrats on the release!

  3. Kudos!

  4. Two things;

    http://boxerapp.com/contact/ is a 404

    Have you considered using code.google.com for issue tracking? I'd love to know where a list of outstanding bugs were so that I could, plausibly, help fix 'em.

  5. Thanks for pointing out the broken link Chris, fixed it now.

    Bitbucket has issue tracking of its own, and I'd prefer to use that to keep everything in one place. There's no tickets for known bugs yet, because I've been too busy fixing them to document them ;) But in the coming days I'll add some tickets for large-scale bugs (the kind it takes longer to fix than to document, that is).

  6. Can 0.8x and 1.0 coexist? Or does install of 1.0 overwrite 0.8x?

  7. They can coexist fine - Boxer 1.0 does not even share settings with Boxer 0.8x. As mentioned in the post though, OS X can be very picky about which version of an application is associated with filetypes: I have found that OS X frequently refuses to re-associate all gameboxes with Boxer 1.0 when I tell it to, instead reverting to Boxer 0.8x. This can make it tricky to use them both side-by-side if you want one particular version to be the 'preferred' one.

  8. Really, really, really awesome job. Period.

  9. Here's another issue (sorry to be a pest): BGHUDAppKitPlugin.ibplugin doesn't load in Snow Leopard's interface builder (which seems odd; don't you use SL?) due to an architecture mismatch. Where can I dig up a replacement?

  10. Or, never mind; I found the plugin (and am downloading it) so I hope that'll be all I need.

  11. Hi Chris, that is very weird - what CPU are you running on? Anyway, it'll be fine to just download the framework and doubleclick the plugin in that to register it. (Just don't go as far as copying the downloaded framework over the copy that Boxer uses, as it's been customised a bit.)

  12. $ uname -a Darwin void.local 10.2.0 Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386 i386

    2.4 GHz Intel Core 2 Duo

    I built the IBPlugin myself and it works fine now.

    Now to see if I can figure out how Cocoa works. Coming from C/Java/Python, this Cocoa/IB thing is just bloody confusing.

Design by 40watt.