On 6/12/15, 4:31 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >We already distribute the binaries here [1], wouldn’t the simple answer >be to package those up in an archive and include the required NOTICE and >LICENSE files just as we do with the source? Do you mean, instead of an EXE and DMG, it would be tar.gz and zip with the EXE and DMG and L & N inside? That doesn’t seem all that convenient to me. >Generally the LICENSE and NOTICE files are also placed in the dist >directory outside of the binary / archives so people can look at the >license before downloading. Would also require making minor changes to >the installer download page [3]. I don’t think we’ve been doing that. >I guess the main issue here is the installer AIR auto update feature - do >we know how many people take advantage of that as opposed to just >downloading the installer directly? Google stats seem to indicate a high >proportion of people go to the page (250,000+ hits). Just out of interest >the track installer pages has been hit 130,000 times. > >Having links in the GUI also sounds helpful, but those files could change >and they may get out of sync between versions of the application. A >solution would be to include the release version number in the path to >the files. > >We could also add the files to the AIR distribution and packed them up >(this has instructions on how, look for assets [2]) but as discussed it's >not easily discoverable. AFAICT, the main issue is the user experience. You go to our page and click on the badge and then the Installer shows up. No place to expose L & N along that sequence. Or the auto-update kicks in. Roy said to bake it into the EXE or try About box. To me the disclaimer button can serve the same purpose as the About box. We could also just add an About box or another appropriately labelled button that pops up L & N.
