Re: Interface Builder popularity w/ Cocoa Developers
Re: Interface Builder popularity w/ Cocoa Developers
- Subject: Re: Interface Builder popularity w/ Cocoa Developers
- From: "John H. Jenkins" <email@hidden>
- Date: Mon, 16 Jun 2008 10:13:03 -0600
On Jun 15, 2008, at 10:19 PM, j o a r wrote:
You seem to suggest that you would have to use the Carbon framework
to generate UI from code? That's absolutely not the case. Let it be
said, once and for all:
Anything that you do in IB can be done programmatically using Cocoa.
The bottom line is - just like you say - that it isn't worth it.
It's just a whole lot more work both to set it up in the first
place, and a whole lot more work to maintain it down the line.
Beyond that, the internationalization/localization approach taken in
Cocoa depends on being able to determine which localized version of a
nib to load at runtime. Since it may be necessary to rearrange
objects in a window depending on the localization (for example, right-
to-left languages such as Hebrew or Arabic will often flip the
arrangements of UI elements horizontally), and since it may be
necessary to adjust the size of various UI elements depending on the
locale (to allow for the fact that different languages may require
more or fewer words to say the same thing), if you build your UI in
your program, it means that the *programmer* is, for all practical
intents and purposes, the *localizer* as well, and you can't really
prepare a localization other than the ones the programmer has
anticipated. In general, this would be a very bad thing. One of the
great virtues of internationalization in Cocoa is that new locales can
be supported after-the-fact without the programmer having to retouch
their code.
=====
John H. Jenkins
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden