accessing resources on bundles [duplicate] - iphone

Question

This question already has answers here:
Packaging a Bundle with a static library
(3 answers)
Closed 9 years ago.
I have created a subproject as a static library and added a bundle to it, so I can wrap the project and resources that will be used by all programs using that library.
I have followed the instructions here.
http://www.galloway.me.uk/tutorials/ios-library-with-resources/
It is working fine, except when I have to work with resources like images and other files.
I thought that by importing a library and its resources to another project I could access them easily but this is not the case.
Every time I have to access a resource file on library's bundle I have to use this:
NSBundle *bundle = [NSBundle bundleWithURL:[[NSBundle mainBundle] URLForResource:#"MyLibraryBundle" withExtension:#"bundle"]];
path = [bundle pathForResource:#"readme" ofType:"txt"];
but if the resource is on the main program I have to use [NSBundle mainBundle] instead.
This is creating a very complex logic because I may have more than one subproject and I will have to create zillions of variations.
Is there a way to make a way the app can find the resource whatever it is using a simple syntax or am I missing something?

Answer 1

Factor your resource accesses into a separate class. For example, something like this might work for you:
#interface CSResourceManager
+ (NSString *)pathForResource:(NSString *)resource ofType:(NSString *)type;
#end
#implementation CSResourceManager
+ (NSArray *)resourceBundles
{
NSBundle *mainBundle = [NSBundle mainBundle];
NSURL *libraryBundleURL = [mainBundle URLForResource:#"MyLibraryBundle" withExtension:#"bundle"];
NSBundle *libraryBundle = [NSBundle bundleWithURL:libraryBundleURL];
// Add more bundles here and/or cache as necessary
return #[ libraryBundle, mainBundle ];
}
+ (NSString *)pathForResource:(NSString *)resource ofType:(NSString *)type
{
NSString *path = nil;
for (NSBundle *bundle in [self resourceBundles]) {
if ((path = [[self resourceBundle] pathForResource:resource ofType:type])) {
break;
}
}
return path;
}
#end
If locating the resource bundle every time is too slow, you may want to cache it, i.e. using a static variable.
To use this, you would now just have to write:
NSString *path = [CSResourceManager pathForResource:#"readme" ofType:#"txt"];
In addition to making your code easier to write, using a class like this will also make it easier to maintain (for example, if you want to change the name of the resource bundle, add additional resource storage locations or fallbacks, etc.).
Update #1: see modified code above to support a "search path" of sorts for locating resources.
Update #2: additional ideas for managing resources:
An alternative to using bundles at all would be to have your subprojects share a naming convention for resource files, essentially flattening the namespace. For example, prefix each resource file with the name of the library it's associated with.