On May 14, 2008, at 10:58 AM, I. Savant wrote:
The issue could also be addressed from the other direction. How
far behind
the scenes do you want to go? Should one program only with structs
and C
functions because polymorphism and dynamic binding do things for
you "behind
the scenes"?
I had started to say much the sam thing (only was using assembly as
my extreme example) but decided against it. :-) Very valid point,
though.
Also, when you support localization, you really need to use NIBs.
Different languages can easily require different layouts, due to
string lengths (German UI text tends to be _much_ longer often
requiring serious re-do of layouts), cultural norms (Left to Right vs
Right to Left), etc.... If you do everything in code, you're going to
have to figure out what the current locale/language is, map it to what
languages you support, and then do your layout from there. By using
NIBs, you can just have a different layout with a differently
localization and the system takes care of everything else.
Glenn Andreas [EMAIL PROTECTED]
<http://www.gandreas.com/> wicked fun!
m.o.t.e.s. | minute object twisted environment simulation
_______________________________________________
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]
