2. Summary
  3. Files
  4. Support
  5. Report Spam
  6. Create account
  7. Log in
 
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas
Idea #733: Default downloads based on system architecture

Written by ren3gade the 18 Jul 10 at 00:19. Category: File Release System. Related project: Nothing/Others. Status: New
Rationale
For a project with both 32- and 64-bit releases, only one may be specified as the "Default Download" for any given platform. If a 32-bit file is chosen as default, then many 64-bit users will likely end up downloading the 32-bit release (and vice-versa for 64-bit, but with more severe consequences to 32-bit users).

This problem is evident in everyday use, as downloads stats confirm that 64-bit releases for my project are rarely ever downloaded, despite many users being on 64-bit systems. Given that the number of 32- and 64-bit users are still near parity, this issue is very relevant. Keep in mind the average user workflow at SourceForge proceeds as so:
1. Arrive at project page -> 2. Click big green button
And so most are either unwilling to sift through other files or unaware that they even exist.

16
votes
up equal down
Solution #1: Default downloads based on system architecture
Written by ren3gade the 18 Jul 10 at 00:19.
A Default Download option should exist to differentiate by system architecture in addition to platform. For example, the current default download options by operating systems could be grouped into two headings by architecture:
32-bit
[ ] Linux
[ ] Windows
...
[ ] All Others

64-bit
[ ] Linux
[ ] Windows
...
[ ] All Others

Like the operating system, architecture information is usually available from the User Agent string, and in the cases where it isn't it, the default should be 32-bit.
-5
votes
up equal down
Solution #2: Offer user a choice between 32/64-bit release
Written by ren3gade the 19 Jul 10 at 14:03.
In or near the vicinity of the default "Download Now" button, the user can be given a choice between 32/64-bit releases (if the project offers different releases for architecture).

For example:
----------------------------
| Download Now!
| 32-bit: foobar.tar.gz
| 64-bit: foobar.tar.gz
---------------------------

Another example:
| Download Now! (32-bit) | OR | Download Now! (64-bit) | OR | View All Files |

Something to the effect. This makes the choice between architecture explicit to the user.
8
votes
up equal down
Solution #3: Allow the button to point to a group of files in the most recent release
Written by nanotube the 19 Jul 10 at 14:19.
There's no end to what kind of 'special' things users may want to detect for the download now button. Here we have the 32/64bit... someone else may want to detect .deb vs .rpm based linux distros, someone else might want detection of winxp vs win7, someone else who has a browser addon might want browser detection...

All that would just add clunk to the code, and you'll never please everybody.

Instead, it should just be possible to have a 'group' of files (say... a directory, or an otherwise-marked group of files belonging to a release) marked as the most recent release, and have the download button point to that. That way, users can select whatever file fits their needs easily, and solve the problem once and for all.
9
votes
up equal down
Solution #4: Allow the download button to point to a URL
Written by nanotube the 19 Jul 10 at 14:51.
The project admins would create a 'download' page, with whatever explanatory information they want, and with whatever links they want, and then link the green download button to that page.

That way... nobody complains - since they can either (a) run their own autodetection code, or (b) list and link the files in the release along with their descriptions and what architectures they are for, etc.
3
votes
up equal down
Solution #5: Allow admins to choose the function of the green download button.
Written by squalldesu the 22 Jul 10 at 13:41.
Admins could choose to link the download button to the files related to the auto-detected platform, like is done now, or they could choose to link it to a customized "download page" as stated above. This way they could set up their own selection of default downloads for each system, platform, architecture, etc. if they wanted.
0
votes
up equal down
Solution #6: Customizable Drop-Down Menu Beside or Replacing Green Button
Written by antumdeluge the 4 Aug 10 at 11:38.
Have an optional drop-down menu where admins can list downloads for specific os/architecture. The admins should be able to manually specify (e.g. type in themselves as opposed to selecting from a list) the os/arch.

Propose your solution


Duplicates


Comments
jengelh wrote on the 25 Jul 10 at 16:02
Solution 1 may not always work, esp. if browsers don't send that sort of identification. S5 is ok!

jengelh wrote on the 25 Jul 10 at 16:04
Er, S3.


Post your comment
Syndicate content

© 2013 SourceForge. All Rights Reserved. SourceForge is a Dice Holdings, Inc. company   Terms of Use - Privacy Policy - Cookies/Opt Out