Difference between revisions of "NSBundle"
(Introduction in layman's terms and note GS extensions) |
m (typo) |
||
(One intermediate revision by the same user not shown) | |||
Line 2: | Line 2: | ||
NSBundle is mostly used to find the executable code for a given bundle (and vice versa), to choose appropriate [[localization]]s, and to locate other resources in a bundle's directory. Currently GNUstep defines two methods in addition to those from OpenStep: <tt>bundleForLibrary</tt> and <tt>pathForLibraryResource</tt>. However, these two extensions are experimental and might change. | NSBundle is mostly used to find the executable code for a given bundle (and vice versa), to choose appropriate [[localization]]s, and to locate other resources in a bundle's directory. Currently GNUstep defines two methods in addition to those from OpenStep: <tt>bundleForLibrary</tt> and <tt>pathForLibraryResource</tt>. However, these two extensions are experimental and might change. | ||
+ | |||
+ | NSBundle inherits from [[NSObject]] and is declared in <tt>Foundation/NSBundle.h</tt>. | ||
[[Category:Foundation]] | [[Category:Foundation]] |
Latest revision as of 05:12, 9 April 2007
NSBundle is a class in Foundation for the manipulation of bundles. Bundles are specialized directories that collect related resources for an application or framework (or even an ordinary file) and present them to a user as a single, opaque file. Common resources are images, NIB or GORM interface files, localizations, and executable binaries.
NSBundle is mostly used to find the executable code for a given bundle (and vice versa), to choose appropriate localizations, and to locate other resources in a bundle's directory. Currently GNUstep defines two methods in addition to those from OpenStep: bundleForLibrary and pathForLibraryResource. However, these two extensions are experimental and might change.
NSBundle inherits from NSObject and is declared in Foundation/NSBundle.h.