Difference between revisions of "XIB"
Jump to navigation
Jump to search
m |
m |
||
| Line 1: | Line 1: | ||
| − | As of MacOS 10.3 Apple moved away from the binary encoded nib files, and towards the xml encoded XIB files, for their interface definitions | + | As of MacOS 10.3 Apple moved away from the binary encoded nib files, and towards the xml encoded XIB files, for their interface definitions. |
The xib file format is actually quite easy to understand, it is the responsability of the object encodeing and decoding, it to insure that it's attributes are read correctly. | The xib file format is actually quite easy to understand, it is the responsability of the object encodeing and decoding, it to insure that it's attributes are read correctly. | ||
| Line 7: | Line 7: | ||
Todo figure out how "</bytes>" is escaped when encoding a byte stream. | Todo figure out how "</bytes>" is escaped when encoding a byte stream. | ||
| + | |||
| + | ==See Also== | ||
| + | [http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/KeyValueCoding/Articles/Overview.html KVC] - Encoded objects must be KVC complient | ||
Revision as of 21:40, 16 July 2012
As of MacOS 10.3 Apple moved away from the binary encoded nib files, and towards the xml encoded XIB files, for their interface definitions.
The xib file format is actually quite easy to understand, it is the responsability of the object encodeing and decoding, it to insure that it's attributes are read correctly.
Here is a commented example of a XIB file. For easy reading open it in a syntax highliting editor using XML highlighting.
Todo figure out how "</bytes>" is escaped when encoding a byte stream.
See Also
KVC - Encoded objects must be KVC complient