By Jeff LaMarche on February 13, 2011
Well, now that Xcode 4 is GM, it has the same icon as Xcode 3.25. Ordinarily, this wouldn’t be an issue, since a GM release means you can throw out the old one and use it full-time.
Only, you may not be able to with all of your projects. Xcode 4 GM has a few issues that make it hard to go full-time with it, including a linker error that can only be worked around by turning some level of code optimization, a change that makes it hard to debug. A few of these problems impact projects I’m working on, so as a result, I have to grudgingly use Xcode 3.25 for some tasks.
Despite a small handful of problems, though, Xcode 4 is where I want to be whenever possible. Having multiple identical icons in your Dock can be a bit of a pain.
Unfortunately, I didn’t save the old Xcode 4 installers. If I had, I would have just gone and stolen the old preview icon and continued using that. Since I didn’t, I did the same thing I did for beta iOS releases and made a customized version of the app icon for Xcode 4. If you want to use it, you can download it here. To install, you just copy the .icns file into Xcode 4′s app bundle, replacing the existing one. And, no, replacing the icon file with a new one doesn’t cause problems with Xcode 4 due to code signing, though I feared it might.
This is what it looks like:
By Jeff LaMarche on February 8, 2011
Sorry for the lack of posts recently. Things have been, well… you know. Same old story. Super busy. Which is good, but it’s murder on blog post frequency.
I’ve recently had to port some OpenGL ES work I did from iOS to Android. It used to be that doing so would have been insanely painful (as opposed to just painful). I would have had to convert the Objective-C code to Java, and then maintain completely distinct sets of code that do the same exact thing. Fortunately, the Android NDK (Native Development Kit) allows you to write code for Android in C/C++. The version of the NDK supported on 2.2 still requires part of the Activity (Android’s counterpart to an iOS view controller) to be written in Java, but does allow you to call C/C++ code using JNI. In 2.3 and 3.0, you can do entire activities in C or C++.
This is a huge step forward for Android for those of us who do performance-critical work on multiple platforms, but it’s not without some pain. Debugging across the JNI bridge is… less than easy. But, being able to share code across platforms is a huge win, and being able to get native speeds in the process is teh awseome.
During these projects, I’ve been taking a lot of my 3D-related code and creating a new set of platform-agnostic C functions and types. I’ve been cleaning up and making names consistent, and placing appropriate pre-compiler macros to make sure the code compiles correctly everywhere. On iOS, the library will take advantage of the Accelerate Framework in places, but doesn’t require Accelerate to function.
I’ve chosen C because I don’t like mixing C++ and Objective-C. The object models are two different for my tastes. But I’ve also made sure to include proper ifdef’d extern statements so that you can import the MC3D header files from C++ without hassle.
I’ve dubbed this set of functions MC3D, and I’m making it open source under a simplified version of the simplified BSD license (simplified simplified BSD license?). I’ve taken out the attribution requirement, so the only requirement is that if you re-distribute the source code, you have to leave the copyright and license text intact. That’s it. Otherwise, you can use it for free in any project, commercial or otherwise, without paying anything, without attributing, and without asking (no really, you don’t need to ask).
MC3D is still very much a work in progress, and I’m only adding code to the repository that I feel is ready for public consumption. Much of what’s in MC3D has been posted here before, sometimes with different names or in slightly different form.
I have other code that I plan to add in the future, including higher-level functionality like model loading, scene management, and skeletal animation, but I won’t add anything until its both solid and platform agnostic.
Currently, documentation is very sparse, and I currently can’t offer any support or help with using it, so caveat emptor! I will gladly accept contributions, bug fixes, and new functionality back into the MC3D codeline.
Link fixed, sorry about that
By adam.wulf on February 3, 2011
By (author unknown) on January 14, 2011
By Colin Wheeler on December 29, 2010