• Using msysgit in Cygwin

    Cygwin sucks. Badly. Particularly on Windows 7, where it’s plagued by the infamous rebaseall bug. As if that weren’t enough cygwin’s git port is terribly slow, and so rather frustrating to use.

    Luckily, msysgit offers a fast, well-supported, drop-in replacement version of git for Windows, complete with a nice, clean installer, that fits much better into the Windows ecosystem.

    But, alas, it’s not without it’s issues, and so here I’m trying to collect what little tidbits I’m learning as I make the transition.

    Using Pageant as your ssh-agent

    Set the environment variable GIT_SSH to:

    "<path to putty>\plink.exe"
    

    And include the quotes! This is related to an issue in git-svn that I’ll mention later.

    Merge Tools

    You need to grab the entire folder and drop it into \libexec\git-core if you want any of the mergetools to work. These weren't in my 1.7.7 installed folder, which I suspect is a bug. Later or earlier versions may address this.

    To use kdiff3 as a mergetool, run:

    git config --global mergetool.kdiff3.path <path to kdiff3.exe>
    git config --global merge.tool kdiff3
    

    Git-SVN Gotchas

    There’s a bug in git-svn with mergeinfo that can bite you in any version past 1.6.5.7. To get around it, download the 1.6.5.7 tag from here.

    Grab git-svn.perl, and replace your copy of git-svn in:

    <program files>\Git\libexec\git-core
    

    But note! This version of git-svn has a bug in it where GIT_SSH has to have quotes around it, lest things go all pear-shaped.

    Lingering Issues

    If you’re using a cygwin shell (like rxvt), git won’t honour the pager settings, as it can never figure out that it’s running in an interactive terminal. Naturally you can just pipe to your favourite pager by hand, but it’s tricky to get back into that habit.

  • Hacking the Playbook - Redux

    Well, I know I said I was gonna write some posts on the Playbook as I begin developing for it. Unfortunately, there are a number of things which have deeply turned me off of the prospect…

    Incomplete APIs

    Yes, I understand the device isn’t ready yet. I understand the simulators are in beta, and the SDKs are being completed. But the startling omissions in the current APIs make me seriously wonder about the device and the BB developers:

    1. No text box control. There’s a text field, but no multi-line control. So much for a note taking application or anything similar.
    2. No date picker. Seriously. Wow.
    3. No localization support. This is supposed to be an enterprise-level device, and it doesn’t have a localization API yet??
    4. No rotation support. Just… unbelievable. This is a tablet, ffs. How can they not have landscape/portrait mode available? Hell, apparently no one has even seen a sample Blackberry app that does portrait mode.
    5. No webkit engine API. They’re “working on it”, apparently. The device is supposed to be out in a month. I mean, really…

    Meanwhile, the simulator doesn’t support things like:

    1. The camera API
    2. The multimedia API (you know, the thing that, to quote, is supposed to “differentiate” this device from others on the market).

    It’s really quite stunning to me, and makes me wonder what other omissions there are in the application stack.

    App World Application Blackholed

    I applied for App World three weeks ago. And nothing. Apparently my application is being “reviewed”. Well, I ain’t spending time writing code if I’m not even sure I’ll be able to submit the thing.

    Ridiculous App World Fees

    Yes, the current submission fees have been waived, but it’ll be $20 per submission to App World once the promotion is over. That means every failed submission, every update, is gonna cost $20. It’s ridiculous.

    Unprofessional Webinars

    The webinars BB posted were, frankly, terrible. The BB consultant running them is brutal, the material is superficial at best, his delivery is moronic, repetative, and frankly, boring… they’re just bad. Meanwhile, they’re full of glaring holes, bad examples, and don’t get me started on the marketspeak.

    Meanwhile, every other question seems to highlight another gap in the SDK or simulator… the number of times I heard “we’re still working on a story for that” was impressive, to say the least.

    In Conclusion

    Everything I’ve seen suggests this device is half-baked at best. Incomplete APIs, crappy presentations, an application process that seems to have stalled out on me, and a fee structure that seems designed to turn away smaller developers… for a $500 device, it really doesn’t seem to be worth the aggravation.