Re: Shipping common app frameworks.
Are your users necessarily going to have more than one of your applications installed? Remember that when you put the frameworks in a common directory, as opposed to inside the app bundle you lose the ability for an application to be used by a non-admin user, as well as the ease of a drag and drop install. Omar Qazi Hello, Galaxy! 1.310.294.1593 On May 12, 2008, at 11:53 AM, David Springer wrote: Folks, We need to ship some frameworks that are common to a few of our apps. The question, of course, is where to put these, and how to bundle them with apps so downloads, etc. are not huge and bloated. I'd like to hear other's experience with this. Do you put common frameworks in a place such as /Library/Frameworks, or do you put them in your own app support directory? How do you handle things like a drag-to-install and move-to-trash to uninstall (or can you with common frameworks)? smime.p7s Description: S/MIME cryptographic signature ___ 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 [EMAIL PROTECTED]
Re: Shipping common app frameworks.
> We need to ship some frameworks that are common to a few of our apps. > The question, of course, is where to put these, and how to bundle them > with apps so downloads, etc. are not huge and bloated. I'd like to > hear other's experience with this. Do you put common frameworks in a > place such as /Library/Frameworks, or do you put them in your own app > support directory? How do you handle things like a drag-to-install > and move-to-trash to uninstall (or can you with common frameworks)? Yes, common frameworks should be in /Library/Frameworks or ~/Library/Frameworks. It's best to use a proper installer (which handles authenticating the user, installing to various target folders, running pre- and post-flight scripts, etc. which can be important for detecting version conflicts, quitting dependent apps if they're running, and other such issues). The drag-to-install approach in an application that needs write access to folders requiring admin rights is not the best approach, IMO. -- I.S. ___ 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 [EMAIL PROTECTED]
Shipping common app frameworks.
Folks, We need to ship some frameworks that are common to a few of our apps. The question, of course, is where to put these, and how to bundle them with apps so downloads, etc. are not huge and bloated. I'd like to hear other's experience with this. Do you put common frameworks in a place such as /Library/Frameworks, or do you put them in your own app support directory? How do you handle things like a drag-to-install and move-to-trash to uninstall (or can you with common frameworks)? Thanks, Dave.S ___ 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 [EMAIL PROTECTED]
