I'm an Electrical Engineer who writes software for a living and likes to play with iOS, Django, and high voltage. I know around 10 languages, 3 fluent, and (not the same) 3 spoken.
UPDATE: NEWGUIDE NEWGUIDE NEWGUIDE!
Vital iPhone stats for this post:
iPhone version: 3G (should work with 2G and 3GS)
iPhone OS version: 3.0 (rock the hizzouse!)
Jailbreak status: Jailbroken using Pwnage Tool.
The Goal: Get live on-device XCode debugging without being a paying ADC member. This time OS 3.0 style.
UPDATE 7/11/09: Procedure working great: post here. Everyone’s getting antsy about on-device debugging with SDK…
Get them while they’re hot! http://www.iphone3g-mods.com/ (coral) has a great list of download links for…
Here’s a quick tip I picked up via the Stanford CS193P iPhone Programming (coral) course. Normally, to switch between device and simulator debugging requires going to the Project > Set Active SDK menu. Since I switch between said active SDKs almost every other build at points, the whole menu thing gets annoying. Luckily, it’s easy to put this drop-down menu in your toolbar in Xcode.
If you haven’t heard about Stanford’s iPhone development course (coral), then I’m not sure where you’ve been. It’s certainly had enough publicity that it needs no more introduction from me, but I figure that I might as well lavish it with my praises too.
I may use this blog to post mainly iPhone or software related articles, but I am an electrical engineering student, and as an EE, I love me some good, clean hardware. Therefore, when my favorite pair of earbuds kicked the bucket the other day, my first thought went to the in-box iPhone headset and, more importantly, how much those earbuds suck. My favorite bang-for-the-buck earbuds EVER are Skullcandy Full Metal Jackets, primarily because I got them at TJ Maxx for $25. In general though, they have silicone pads that seal out sound, instead of the hyper uncomfortable iPod earbuds that fall out and sound like crap. I was super bummed when my FMJs broke, but luckily, the part that broke was on the plug end of the earphones. That is, both earbuds themselves still work fine, only the plug is dead. My thought was to cut the crappy iPhone buds off their cable (which includes a microphone and remote button) and graft on my beloved FMJs.
If you’re beginning to learn Objective-C like I am, things like this aren’t immediately obvious. I was trying to fool around with creating my own class, and I kept getting this warning
warning: no '-blah blah blah' method found along with an accompanying
warning: 'ClassName' may not respond to '-blah blah blah'
The really annoying part was that, despite these warnings, the code still worked just fine. Turns out, my issue was that I had this method in my class implementation (PolygonShape.m):
I’ve been having this really annoying error lately ever since that carrier update that Apple released to add support for AT&T’s new microcells. The exact message is this: