Using a XIB file or programming it

[Shake0615]

As a general rule of thumb, is it cheaper on memory and file size to create things programmatically or using XIB files? If so, how much memory would you save if you did it one way or the other?

For example, what's the difference in processing power/memory/file size to create a button through interface builder vs. coding it completely?

Thanks!

[ranjit]

?

It all depends on how you create your objects in XCode. Nothing to do with your XIB. XIB is just to design the user interface.

If you use property(retain) for your objects, surely they are all being created and remains in memory right after the app is executed. But if you don't, and create them as needed, you should be okay.

[Shake0615]

Originally Posted by ranjit

?

It all depends on how you create your objects in XCode. Nothing to do with your XIB. XIB is just to design the user interface.

If you use property(retain) for your objects, surely they are all being created and remains in memory right after the app is executed. But if you don't, and create them as needed, you should be okay.

Well, I'm not familiar with how XIBs work. But I figured it would cost more memory to create and store the information about a button in a XIB file (I imagine it keeps all the objects in memory from beginning to end) as opposed to creating it in Xcode using NSButton and cleaning it up once I'm done with it.

If there is a difference between the two methods, I was hoping to know how marked that difference was. If there isn't, then I guess my question is pointless lol.

[jlehr]

Originally Posted by Shake0615

Well, I'm not familiar with how XIBs work. But I figured it would cost more memory to create and store the information about a button in a XIB file (I imagine it keeps all the objects in memory from beginning to end) as opposed to creating it in Xcode using NSButton and cleaning it up once I'm done with it.

If there is a difference between the two methods, I was hoping to know how marked that difference was. If there isn't, then I guess my question is pointless lol.

Nib files aren't stored in memory; they're files, so they're stored in the filesystem. Applications load nib files at runtime as needed by unarchiving their contents, which causes the objects to be allocated dynamically, just as they would if you were creating them programmatically.

The difference is that the objects loaded from a nib file already have some or all of the properties set, which in some cases can save writing and maintaining a fair amount of relatively boring code. Once the objects are in memory they're the same as any other objects, and their lifetimes will be determined by what your code does, just as with objects you allocate in code. There should be no difference in memory consumption.