Hello all, I'm new to the list and somewhat new to OSX (not iphone!) development. I spent ten years most of my time in java so it was a hurdle..
I am currently developing an app (APP-A) which does PDF manipulation. I have a second app (APP-B), that provides a PDF Viewer which is older. APP-A depends on APP-B as it uses APP-B for viewing manipulated PDFs. APP-B is independent from APP-A. I could put both apps into Applications. But if a User don't know what APP-B is for as he might only wan't APP-A but didn't see the dependency, he might delete APP-B and APP-A cannot work properly anymore. To solve this I put APP-B into the resources of APP-A, and it works to launch the app from this directory. I have not found any documentation from apple or mailing-lists if this is unwanted, problematic or somewhat evil!? The launchd finds the 'hidden' APP-B and behaves as expected... Is this allowed and recommendable, or how could I solve this alternatively and I don't want to merge the apps!? best, Alex_______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
