Also I was testing the static website on an old iphone. It detected "ios" correctly and showed the downloads for "Unix-like systems". This is kind of wrong because it could make people think that there is a version for Iphone (many people barely — if at all — understand what is ios, Unix, Windows, etc.). I think that the detection algorithm should be like this: 1/ if detected: show the downloads for the detected system (that's already done); 2/ if detected and we know this is not supported/available (so we can prepare a list of OSes), show a proper message "GIMP is not supported on this OS, sorry" and below this, the "Show downloads for GNU/Linux | OS X | Microsoft Windows | All" message, and that's all. This step allows to not misdirect the user into thinking we have support for one's platform, in particular I am thinking of all the smartphone OSes (iphone, Android, FirefoxOS, etc.). 3/ When detection fails or results into a system we have not planned, just show a relevant message "We cannot recognize your system in our list of supported systems" and below the list of supported systems, and all the downloads. Jehan On Tue, Oct 6, 2015 at 12:47 PM, Elle Stone <ellestone@xxxxxxxxxxxxxxxxxxxx> wrote: > On 10/05/2015 09:37 PM, Jehan Pagès wrote: >> >> Hi, >> >> 1/ Is it possible to force the download page at least to be https? >> There are some companies which provides free certificates with root CA >> in all mainstream browsers. >> >> This would be a prerequisite to pretend to provide safe download. For >> instance I see the page provides checksums, which is good but is half >> meaningless if not provided through a secure channel like https (half >> because it still allows download corruption check, but not malevolent >> corruption integrity check). > > > Also regarding the download page, checksums are nice, but many users won't > know why they are important or how to use them. Step by step instructions > (or a link to same) would be nice. Probably different instructions would be > needed for Linux, Windows, and Mac users. > > I don't understand the point of the long list of tar.bz2 files. They almost > look like they should be links. > > It would be nice to see a link to Partha's website for Windows and Mac > users. Leastways I always refer Windows users to Partha's builds. > > There doesn't seem to be enough visual indication of when the > "topic/subtopic" on the page has changed. Studying the contents, obviously > there's a well-thought-out underlying outline/organization. But visually > it's not obvious (well, not obvious to me anyway) where the major breaks > are. > > Elle > > > _______________________________________________ > gimp-developer-list mailing list > List address: gimp-developer-list@xxxxxxxxx > List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
