Nibless Tutorials
Quote from Forum Archives on September 5, 2011, 1:45 pmPosted by: fblistserve <fblistserve@...>
Steve’s reasons for picking nibless tutorials are understandable. There are, however, good reasons for considering the use of nibs such as:(1) ( At least for me ) it is easier to lay out the controls in a window in IB than it is in code.
(2) Less code for the programmer to write and maintain. Although nib connections can be complex
(3) Apple recommends using nibs whenever possible
(4) Most developers use nibs, so the pool of example resources is larger if apps use a nib
(5) Using Xcode ( which presumably one is doing if using Cocoa nibs ) allows automatic indentation of C/Objective-C code that FB doesn’t provide.
(6) Internationalization for the UI elements is nicely isolated in the nib and makes it easier to send to someone else for translation.Pluses for using nibless:
(1) FB compatible because FB doesn’t work with Cocoa nibs
(2) Doesn’t require learning Xcode
(3) Insulated from Apple’s nib changes ( i.e. there is no conversion path from Carbon nib to Cocoa nib )Another item for consideration: most developer’s apps have 50 to 100 source files and the Xcode/FB project manager is vital. I haven’t seen( and might test to see how it works ) an FB project that is 100% Objective-C.
Brian S
Posted by: fblistserve <fblistserve@...>
(1) ( At least for me ) it is easier to lay out the controls in a window in IB than it is in code.
(2) Less code for the programmer to write and maintain. Although nib connections can be complex
(3) Apple recommends using nibs whenever possible
(4) Most developers use nibs, so the pool of example resources is larger if apps use a nib
(5) Using Xcode ( which presumably one is doing if using Cocoa nibs ) allows automatic indentation of C/Objective-C code that FB doesn’t provide.
(6) Internationalization for the UI elements is nicely isolated in the nib and makes it easier to send to someone else for translation.
Pluses for using nibless:
(1) FB compatible because FB doesn’t work with Cocoa nibs
(2) Doesn’t require learning Xcode
(3) Insulated from Apple’s nib changes ( i.e. there is no conversion path from Carbon nib to Cocoa nib )
Another item for consideration: most developer’s apps have 50 to 100 source files and the Xcode/FB project manager is vital. I haven’t seen( and might test to see how it works ) an FB project that is 100% Objective-C.
Brian S