> Actually, reading the docs for +loadNibNamed:owner:, I think it is even > easier (but you'll want to test it). The owner is used to determine where > to look for the NIB. > > If you were to create a subclass of NSApplication that lives within the > framework that has your generic MainMenu.nib and then set the application > class of your application to that subclass, then the standard means of > bringing up Cocoa -- i.e. the call to NSApplicationMain() -- should "just > work". >
Cool, I have some of this already in place, so now I know where to build from there. > That is, clients of your framework should be able to: > > - create a new Cocoa application project > > - delete MainMenu.nib > > - set the application class to your custom NSApplication subclass > > - link against your framework > The only difference is that by and large they'd be building a C++ app - the framework is C++ with the Mac specific parts implemented in ObjeciveC++ and Cocoa. So they wouldn't even need to delete the MainMenu.nib, since it wouldn't exist. I have project templates to create the skeleton project and properly link to my framework. Thanks !! Cheers Jim _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
