Should views be created using NIB or code on the iPhone?

Question

Is there any performance, development flaws, or advantages when developing views using Interface Builder?

Answer 1

Often you want to use Interface Builder; There are several reasons why you will want to do this through the programming interfaces:

• this is a more acceptable way to create user interfaces because of its simplicity and visual advantages that you cannot achieve simply with simple code.
• iPhone , .., Apple , iPhone.

, , Interface Builder, - , - , n UIImageView - , Interface Builder. , , .

, NIBs/XIB , NIB, ( , ), . , , , NIB, NIB, , NIB, .

, - Interface Builder, , , Interface Builder.

Answer 2

, , . - , , , ( , ).

Answer 3

, , , iPhone. , , - . , .

GUI UIViewControllers , MVC. loadView, , , .

: GUI, loadView UIViewController.

Answer 4

. 11 - nib * (# locales) - ( 10 ).

Answer 5

, , XIB . iPhone, , XIB, Objective-C.

http://arstechnica.com/apple/guides/2009/04/iphone-dev-convert-xib-files-to-objective-c.ars

Builder !:)

, , .

Answer 6

Never look at generating NIB code with a tool. But look at the Apple Note.

Note. Although you can create an Objective-C application without using nib files, this is very rare and not recommended. Depending on your application, avoiding the use of nib files, you may need to override the large scale wireframe behavior to achieve the same results you would get with a nib file.