That's an interesting question. We use IB where we can on the iPhone
and frankly we can use it a lot. Most of Apple's samples were redone
to use IB when IB for iPhone became usable. Yes, there are many
reasons to do things in code, but there are many to use IB. Its a
balance. Using IB cuts down the amount of work dramatically. We have a
very big iPhone product that we've been working on *since March* and
we still have a ways to go. We had to do everything by code at first -
and I'm personally used to doing that on Windows because all the GUI
designers there are horrible - but once we got IB working it
accelerated our development in many areas.
So its a balance - code and IB. There are plenty of areas where
frankly code is better on the iPhone. But there are many that people
are just not using IB because they are being obstinate.
One thing I think many newbies try to avoid IB for is simply because
they don't "get" Cocoa dev very well. They are used to Win32 or .NET
generating everything in code because "thats how its done". And yes,
even in .NET expert devs tend to generate the UI in code because
that's really all the .NET UI builders do.
On Nov 17, 2008, at 4:25 PM, Brian Stern wrote:
On Nov 17, 2008, at 4:59 PM, Kyle Sluder wrote:
Why does everyone new to the platform want to immediately discard IB?
It is the correct (yes, "correct", not "preferred", not "easiest",
but
*correct*) way to implement your interface.
I can tell you that the majority of iPhone developers are refusing
to use IB. The reasons I usually see are
It's one more thing to learn.
It's not as good as GUI builders on other platforms.
Generating a UI in code gives more control.
For a long time IB was buggy and incomplete for iPhone development
so developers got used to generating their UIs without it.
In addition:
The UI's on iPhone tend to be simpler and have fewer different views
so whatever savings in time there might be with IB are not so
pronounced.
Apple examples tend to not use IB. For instance there are no Apple
examples for UITableView that use IB. The UICatalog example app,
which demonstrates every UI element, is almost completely done in
code. IMO, there's no excuse for this.
Certain aspects of the UI must be done in code because things aren't
revealed in IB or simply can't be done there.
Apple spending months diddling over its NDA meant that most iPhone
developers found non-Apple forums to discuss iPhone development so
any guidance that Apple might have had over how to write proper apps
has been very late in coming.
I do use IB for a lot of my UI on iPhone but quite a bit of it is in
code also.
--
Brian Stern
[EMAIL PROTECTED]
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/alex%40webis.net
This email sent to [EMAIL PROTECTED]
Alex Kac - President and Founder
Web Information Solutions, Inc.
"You cannot build a reputation on what you intend to do."
-- Liz Smith
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
