site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On Feb 13, 2007, at 9:47 AM, John Daniel wrote: <snip> - Luke _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... Recently, I have noticed a nice trick some people are doing. They are putting a symlink to /Applications on the installer disk image with a background image consisting of an arrow moving the app to the installer link. Given this little trick and my PackageMaker failures, I am strongly considering going back to a drag-n-drop installer for simple Application installations. I read somewhere that Apple recommends that method. Actually, it depends. Apple's recommendations for package distribution are not that cut and dry. The sort of distribution mechanism you should be using depends on three things: [1] the complexity of the install you're performing [2] your desire to present the user with addition information or plugins during the installation [3] the computer-savvy level you expect of your customers So for non-complex projects (e.g., a self-contained application), where you don't need or want to display a read-me, license agreement (yes, that functionality is available in disk images as well), summary panel, or use installer plugins, and where you expect users will have a good understanding of how to use the file system, then a drag and drop installer is an appropriate avenue to consider. For other situations, you may need/prefer to use an installer package, if only to hold users' hands through the installation process. Installation is an intimidating process for a lot of novice users. Using the Installer as opposed to asking them to drag and drop an icon can be somewhat reassuring. This email sent to site_archiver@lists.apple.com