On Feb 25, 2009, at 5:57 PM, Quinn Taylor wrote:
> > On Feb 25, 2009, at 10:30 AM, Peter Hosey wrote: > >> On Feb 25, 2009, at 10:27:15, Quinn Taylor wrote: >>> Making growlnotify hard to install doesn't do anyone a favor until/ >>> unless there actually is a "better" way. >> >> There is, which is an Installer package. The hard part of that is >> wrestling with PackageMaker. >>> > > Sorry, I guess I had interpreted the comments about "a better way" > as applying to CLI posting of notifications, rather than the install > experience. :-) Makes much more sense this way. > >> On Feb 25, 2009, at 11:10:01, Christopher Forsythe wrote: >>> What I eventually wanted was a button in the prefpane to do all the >>> right things with dropping it onto the file system, similar to what >>> textmate does (and I think subethaedit) with their cli. >> >> I'm still not a fan. It makes more sense to me to do all the >> installation in the Installer. (See also what John C. Welch has been >> saying about installers, esp. WRT remote installation.) > > I agree. The install/uninstall buttons do have a certain charm, but > the fact that they're hidden away makes it less than obvious that > they exist at all. Even if placed in the Growl pref pane, users are > apt to completely miss that it's even there. > > I think that TextMate and SubEthaEdit (which does use the same > approach) are different in that they're inherently stand-alone apps > that you can drag into /Applications, whereas Growl is already using > Installer.app to put the pref pane in the right place. If only for > that purpose, the installer is overkill, but installation for some > of the extras does require a little extra care. > > I'm with Peter—lumping all the components together in a unified > installer makes it much cleaner. Plus, users will have to at least > click past the license agreement, which (in the unlikely case of a > destructive bug) does provide a little more "we warned you" material. In retrospect I agree, unified mpkg makes sense. We should probably also cleanup whatever we can, like mail bundles in ~ and /, prefpanes in ~ and / and so forth. There's even a framework that .5 installs that we should maybe cleanup as well. Too bad people couldn't figure out framework weak-linking or we could just drop that in place as well. Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en -~----------~----~----~----~------~----~------~--~---
