site_archiver@lists.apple.com Delivered-To: Installer-dev@lists.apple.com What Stéphane said. Also, I filed the following bug feature request: bool YesNoDialog(string question, bool defaultIfSilent) On May 11, 2007, at 5:30 PM, Peter Bierman wrote: _______________________________________________ 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... #5199577 - add simple dialog api for user input callable during installer scripts Summary: In certain cases, it would be useful to receive user input or display an alert dialog during the Apple Installer script phases (preflight, postflight, etc.). Since there is currently no built-in method to do so, this can lead to a poorer user experience and poor practices during installer authoring. A supported API for dialogs during scripting phases would lead to a better user experience and could enforce best practices. Notes: One such example where a dialog API would be useful is when launching a third-party installer from a script. A requirement from the third- party is that their application binaries cannot be repackaged so the installer must be launched. If the user cancels the third-party installer, then it might be useful to display an, "Are you sure? The third-party install is required to continue." dialog. A general use- case is a runtime error that cannot be detected before preflight (where an installer plugin may be used), which you want to give the end-user a chance to recover from that error. Current workarounds might include displaying an AppleScript dialog or creating a custom application just for that dialog. Neither workaround is ideal. Unless the installer developer has the foresight to special-case command-line installs, these dialogs would appear. In addition, it creates added complexity to create a dialog one might expect from a simple function call. Pseudocode for such a function signature might look like this: where defaultIfSilent is the value returned if the installer is run from the command-line. Moreoever, since defaultIfSilent is required, it enforces the best-practice of designing for a command-line install. What's "Klingon UI input"? This email sent to site_archiver@lists.apple.com