DrunkenBlog has some comparisons of current Mac apps to their older NeXT incarnations. You probably noticed some similarities if you watched the video of Steve Jobs demoing NextSTEP 3.0. But more interesting is what commentor Rory Prior has to say about Interface Builder:
<rant>What’s annoying from a developers perspective is that Interface Builder is getting so long in the tooth. It lacks some really necessary basic features and still requires that you manually inform it of any changes to your classes made in Xcode or vice versa. It doesn’t provide any features to deal with maintaining localised nib files, it has spotty support for contextual menus, and generally makes editing complex component layouts (especially nested layouts) a complete nightmare. A lot of work which should be doable in a few clicks ends up having to be done programatically, which is time consuming to say the least and adds the potential for more bugs.</rant>
Interface Builder was ahead of its time. And, yes, the ability to set outlets and actions is still cool. But aside from adding support for layout guides and bindings, it doesn’t seem to have changed much. It could even learn a few things from PowerPlant Constructor, circa 1996. The last time I complained about Apple’s developer tools, it wasn’t long before they announced Xcode. So hopefully there’s already a project underway.
Also, I’d love for someone to really make localization easy—as it, in theory, should be. I’ve tried (I think) all the third-party tools that help in localizing nibs and strings files. Maybe I’m just weird, but all of them seem cumbersome to me, and some of them don’t even work reliably. Perhaps the design and documentation of nib files are partially to blame. Anyway, at present, I’m using a collection of scripts and Makefiles to help with localization. I wonder how many other developers have rolled their own.
Stay up-to-date by subscribing to the Comments RSS Feed for this post.