From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Andreas Bringedal <anbring@online.no>
Cc: xconq-general@lists.sourceforge.net, xconq7 <xconq7@sources.redhat.com>
Subject: Re: [Xconq-general] Re: New Xconq Prerelease
Date: Sun, 28 Nov 2004 23:06:00 -0000 [thread overview]
Message-ID: <41A920CF.90705@phy.cmich.edu> (raw)
In-Reply-To: <000f01c4d4dc$eca5d0c0$a5f74382@Rufus>
Andreas Bringedal wrote:
> After looking closely I did find the windows version but
> what I was hoping for was was a download page that were very easy to
> understand.
> If it instead had been like this:
> Xconq 7.5 game files
> Windows version
> Mac version
> Xxx version
Well, I could split the 'xconq' package section into new
'xconq-windows', 'xconq-rpms', and 'xconq-sources' package sections when
I do another release. This is more work for me, because I would have to
create 3 file releases instead of just 1. Also, Sourceforge appears to
sort package sections alphabetically, so your 'xconq-windows' package
section would not appear until near the end of all the "gobbles". Right
now, your Windows download appears at the _top_ above all the other
files; all that a Windows illiterate must do is see the "SETUP.exe". How
hard is that?
But, I agree that the download screen looks cluttered. Blame
Sourceforge; don't blame me. Why don't you submit a feature request to
the Sourceforge people?
http://sourceforge.net/tracker/?func=add&group_id=1&atid=350001
Choose "Project: File Release System" from the "Category" menu on that page.
Just tell the Sourceforge people that you would like a big button on the
File Release System downloads page that says "Simple View". And, if
someone clicks on the "Simple View" button, it will display something in
the following format (with lots of white space and bigger letters):
package-section-name
file-release-name
=====================================================================
file1-name (Size = 1.6MB) (32-bit Windows Program)
---------------------------------------------------------------------
file2-name (Size = 1.6MB) (Source RPM)
---------------------------------------------------------------------
file3-name (Size = 1.5MB) (Gzipped Source)
...
I would suggest that you write "Simplified Downloads View" for the
"Summary" text field on their feature request page. You can put your
description (like the one I just gave you) in the "Detailed Description"
text field. As a technical note, you might also want to tell them that
you would like your view preference to be stored in a cookie, so that it
is remembered next time you visit to download a new file. When you are
finished filling in the "Detailed Description", just click the "SUBMIT"
button at the bottom of the page.
Eric
next prev parent reply other threads:[~2004-11-28 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 5:27 Eric McDonald
[not found] ` <000601c4d4a4$862ae660$b1f94382@Rufus>
2004-11-27 23:33 ` [Xconq-general] " Eric McDonald
2004-11-27 23:58 ` Andreas Bringedal
2004-11-28 0:50 ` Andreas Bringedal
2004-11-28 23:06 ` Eric McDonald [this message]
2004-11-28 23:43 ` Andreas Bringedal
2004-11-30 6:12 ` Eric McDonald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41A920CF.90705@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=anbring@online.no \
--cc=xconq-general@lists.sourceforge.net \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).