On 07/10/2012, at 7:05 AM, koko <k...@highrolls.net> wrote: > > On Oct 6, 2012, at 11:01 AM, Seth Willits wrote: > >> use a framework to keep the images bundled with the library > > Does the Framework Bundle behave as an App Bundle, i.e. is Bundle a Bundle no > matter what?
A framework is not the same thing as a static library, so what do you want? A static library is just code that ends up as part of your app, just like any other source code. A framework has its own bundle, which can be contained within an application's bundle. The framework's resources can be part of the framework bundle rather than the app's bundle (and will usually make sense to organise that way). Frameworks aren't hard to make but they bring some downsides, including greater complexity, potential for namespace collisions, etc. Unless you have a truly reusable piece of code that finds many different applications, there's probably little reason to make a framework. --Graham _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
