sourceforge: IdeaTorrent

Written by codebiscuit the 24 Jan 11 at 10:07.

Ideally I'd just set the URLs of three other sourceforge projects that I think users of my software would be interested in. This is surely always going to be better than an automated algorithm, even if the algorithm is good I'd like to think it is not as good as my human brain!
By all means let the algorithm set three defaults if you want, but I'd like to be able to override them.

Ideally I'd just set the URLs of three other sourceforge projects that I think users of my software would be interested in. This is surely always going to be better than an automated algorithm, even if the algorithm is good I'd like to think it is not as good as my human brain! By all means let the algorithm set three defaults if you want, but I'd like to be able to override them.

Written by codebiscuit the 24 Jan 11 at 10:09.

I know that the poker game on my "Open Metronome" page is not related to my project: let me click something that says "this is not related, don't show it here again".

I know that the poker game on my "Open Metronome" page is not related to my project: let me click something that says "this is not related, don't show it here again".

Written by codebiscuit the 24 Jan 11 at 10:23.

It doesn't work. Remove it.
Alternatively, allow admins to disable it (which would hide it), in a similar manner to the way admins can disable reviews.

It doesn't work. Remove it. Alternatively, allow admins to disable it (which would hide it), in a similar manner to the way admins can disable reviews.

Written by fhaag the 2 Feb 11 at 18:45.

Let admins select and edit a list of projects they think are related. Possibly also a list of projects that are absolutely not related (can be assembled in the course of solution #2). To prevent abuse, this list is not shown directly, but the algorithm that chooses related projects does so considering the list. Like this, there's a wider base than just the one current project to allow finding common project traits.

Let admins select and edit a list of projects they think are related. Possibly also a list of projects that are absolutely not related (can be assembled in the course of solution #2). To prevent abuse, this list is not shown directly, but the algorithm that chooses related projects does so considering the list. Like this, there's a wider base than just the one current project to allow finding common project traits.

Written by rjmoerland the 26 Aug 09 at 14:00.

A radio button could be added to each screen shot entry, where the one selected would designate that particular screenshot to be the one shown on the project's summary page and in search results.

A radio button could be added to each screen shot entry, where the one selected would designate that particular screenshot to be the one shown on the project's summary page and in search results.

Written by trilarion the 27 Aug 09 at 09:04.

Put a number in front of every screenshot. Add then a combo box where you can select a number. This number indicates the primary screenshot and is displayed in the search list, on the summary page, ...

Put a number in front of every screenshot. Add then a combo box where you can select a number. This number indicates the primary screenshot and is displayed in the search list, on the summary page, ...

Written by codebiscuit the 21 Oct 09 at 20:15.

I would assume it would be a fairly easy fix: even something as simple as making the site always choose the newest, or the one that has the first filename (or alt text) alphanumerically, provided it was documented as such, would work just fine.
It could alternatively work by displaying the first (or last, anything consistent!) by "dbImageID", provided each sumbitted image was guarenteed a greater ID than the previous one barring overflows - for a maximum of 6 images, this would probably work?
Or, having some specific method of tagging the user-defined summary screen (as a seperate thing from "Other screenshots").
I'm not a web guy, however, so apologies in advance if it is all very complicated (& I can't myself suggest a patch).

I would assume it would be a fairly easy fix: even something as simple as making the site always choose the newest, or the one that has the first filename (or alt text) alphanumerically, provided it was documented as such, would work just fine. It could alternatively work by displaying the first (or last, anything consistent!) by "dbImageID", provided each sumbitted image was guarenteed a greater ID than the previous one barring overflows - for a maximum of 6 images, this would probably work? Or, having some specific method of tagging the user-defined summary screen (as a seperate thing from "Other screenshots"). I'm not a web guy, however, so apologies in advance if it is all very complicated (& I can't myself suggest a patch).