site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On Jan 13, 2006, at 12:22 AM, Rob Keniger wrote: On 13/01/2006, at 8:44, Robert Simutis wrote: - Luke - rob.keniger _______________________________________________ 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/luke%40apple.com _______________________________________________ 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... I need to produce installers via PackageMaker which are capable of closing all open foreground applications (aside from the Finder, the Dock, and the Installer.app itself, of course), similar to the option available in Installer VISE. The applications should all prompt the user to save and come to the foreground in succession. (I have a stopgap measure which uses the <installer-check> to look for open apps via the JavaScript functions available in 10.4 installers, and if any are open it blocks the install, but this really isn't good for the user experience.) Is there a reliable way to close open applications with a relatively low amount of code, or is there a flag in the .dist scripts that I've missed in the docs that can do this? Do you really, really need to do this? As a user this would have to be one of the most annoying behaviours an installer can implement. It is incredibly intrusive and your users will hate you for it. Why not simply use the installer option to force a restart at the end of the installation if you need to install shared components? Depending on what is being installed, quitting certain applications before an install can be essential. Certainly it may not be necessary to quit all applications when installing the latest version of your application and its associated framework -- TextEdit can probably remain open during the install with no ill side-effects, for example. But you wouldn't want to leave MyApp.app version 1 running while installing MyApp.app version 2. Consider quitting only essential applications via an Installer Plug- In, and provide UI to alert the user to what you're doing before you do it. i.e., provide a "Quit Application" button in your Installer Plug-In, so that if users come to that pane and decide "I'd rather finish up the current session in my app and install this later" rather than having the app be shut down on them by the Installer with no warning. This email sent to luke@apple.com This email sent to site_archiver@lists.apple.com