News for hackers. Stuff that matters.
Re:IPhone Development: Android SDK from an iPhone Developer'... by joezydeco on Wednesday March 03, 2010 @06:00PM (#1165491)
Maybe I'm in the minority, but I find UIBuilder to be awful. Unintuitive and almost impossible to grok without some prior experience or handholding.

For my first "hello world" apps I wound up coding the views entirely by hand and skipping the .xib

Re:IPhone Development: Android SDK from an iPhone Developer'... by glenra on Thursday March 04, 2010 @01:57AM (#1166357)
I'm right there with you in that minority. I think using previous Apple tools had led me to expect the interface should be "discoverable" and it wasn't. UIBuilder is, if anything, user-hostile. Plus the XCode integration is really poor.

The iPhoneRant blog reflected my experience pretty well with posts like this:

http://www.iphonerant.com/2009/06/xcode-is-flaky-interface-b...

http://www.iphonerant.com/2009/06/hahahahaha-wow.html

Quotes: "Programming the iPhone means managing a hodgepodge of view and view controllers and nav controllers and where the hell was I? It really doesn't allow your brain to just think about what the software is supposed to do. The fact that no one's come out with a good source to teach this stuff is very telling--it's unteachable. You have to slog through it, and when you get it to work, you're done. You can't necessarily explain how you got there or why it works. And it doesn't lend itself to being teachable, which is a good reason all the books on iPhone programming stink."

"The XCode environment is flaky and shit-filled. Little things add up, like the fact that you can't just select a file in the top frame and save it with command-S. No, you get a beep. Can't do that. You have to CLICK IN THE LOWER WINDOW, on the code, and then hit save. Because, otherwise you might save a few clicks and make things easy and intuitive."

I've actually got an App in the store. When I started I figured I'd do this silly little thing as a proof-of-concept and then go on to more ambitious ideas but I gave up because iPhone programming was just so unpleasant I couldn't bring myself to do it anymore.

I commented on UIBuilder here: http://blogjack.net/2009/06/why-do-iphone-development-tools-...

And on the early DRM experience here: http://blogjack.net/2008/07/iphone-20-woes.html

My hope is that one day Apple produces an Apple-worthy development environment.for iPhone OS. XCode/UIBuilder isn't it.

Re:IPhone Development: Android SDK from an iPhone Developer'... by glhaynes on Wednesday March 03, 2010 @06:15PM (#1165530)
This is commonly said by people new to Interface Builder. I don't recall hearing of a long-time Apple / NeXT dev or major app that didn't use it, though.
Re:IPhone Development: Android SDK from an iPhone Developer'... by joezydeco on Wednesday March 03, 2010 @08:20PM (#1165795)
So why hasn't IB gotten the same amount of improvements and attention as the rest of the toolchain? XCode has come a long way, as have the compilers and instruments.
Re:IPhone Development: Android SDK from an iPhone Developer'... by glhaynes on Wednesday March 03, 2010 @09:58PM (#1165991)
Oh I don't disagree with you that IB can be annoying, and to a part-time Mac programmer like myself, not as intuitive as I wish. I only meant that the full-timers generally seem to like IB (warts and all), or, even if they don't like it, they still nearly universally use it instead of doing all their layout in code.

The same scenario has repeated itself for many years: a newbie gets annoyed at IB and says "I'm just gonna do it all in code!" and all the graybeards say "ur doin it rong."

Re:IPhone Development: Android SDK from an iPhone Developer'... by joezydeco on Thursday March 04, 2010 @08:39AM (#1166852)
I certainly wouldn't embark on a long-term OSX/iPhone project without mastering IB.

It's obvious that your UI is easier to modify and update using IB than hacking it in and out of the view controller code.

Back to the original thread, I do give a little credit to Android to having the option of UI editing done inside of Eclipse. It's not perfect, it's a little hacky, but the concept of slapping down a UI element like a button, naming it, and then having it automatically compile and show up in the editor autocomplete is a powerful thing. The first time it happened it honestly was a nice surprise.

Re:IPhone Development: Android SDK from an iPhone Developer'... by alextgordon on Wednesday March 03, 2010 @06:46PM (#1165609)
I can understand this. Interface Builder is designed to transparently map to the underlying Cocoa calls. It doesn't introduce any new abstractions that aren't already present in Cocoa.

While this is a great feature for reasoning about your xibs, it can probably seem unnecessarily confusing to someone new to Cocoa.