It's snowing
In Seattle ... in March.
The iPhone SDK has the Interface Builder now ... this will be great for making already-easy-to-create UIs even easier on the iPhone.
With the proper reading material, two hours is no problem. Two days, I could maybe do on a bet with a good Dostoyevsky novel. But two years?
Here is the complete menu from last night's meal at Disney's Victoria & Albert's restaurant:
I was having problems with code completion in XCode (iPhone dev platform), even though I fixed the obvious problem of it not being turned on by default. It seemed to still not work like I expected (that expectation was basically that it should work just like Visual Studio, of course). Well, it doesn't, and it still feels inferior, but at least I've figured out the "trick" (insofar as I don't see it immediately in the docs). You have to press Control-Period to force the autocomplete to happen (and to cycle through the list if it has already triggered but is stuck on an entry you don't want). Pressing Control-Slash (which was in the docs) takes you to each param in the param list.
Well, after playing with the iPhone SDK for a few days, it's going slowly, for two reasons. The first: Apple didn't include a visual designer, so there is no way to build an interface via drag-and-drop. This is planned (and they demo'ed it), so at leat this will be possible in the future, but it is a tough thing not to have for those of us who are new to building UIs on a Mac OS. The exclusion of this piece makes a little sense in that it was the only piece of the SDK that was really tied heavily to the iPhone other than the simulator, which you must have, so they probably just ran out of time and made the right call. Second, and way more problematic, is Objective-C. I kind of "get" Objective-C in that it is basically a set of macros on top of C to help you get some object-oriented features, but man, is it hard to read for someone who knows C++, C#, and Java. Objective-C definitely took an evolutionary branch off of C that is far different from those other languages and feels like it is stuck in the early COM era of Windows C/C++. And it is far less productivity-enhancing than C# or Java. Oh well ... I thought I was done learning new languages, so much for that!
Not only did Apple knock the ball out of the park with their SDK (and Exchange Active Sync) announcement today, they drove to where the ball finally landed, ground it up, stuck it in a rocket, and shot it to the moon.
Apple released the iPhone SDK today -- but people won't be able to run applications written with it until June, when the next firmware release comes out (and it will take that long to set up the iTunes store for it). That gives everybody about three months of catch-up time to write iPhone apps (sucks for those who were hoping to be first out the door the day after the SDK shipped)... not sure that's enough time, but I'm going to give it a try, *if* I can get my hands on the SDK (I got a clearance code for it, but their download servers are overwhelmed at the moment).