Idea to cut down on Distro list

[glamdring]

I'm sorry if this is not the correct place for suggestions, but I didn't see any other place.

I'm sure everyone has realized how massive the distro list is when submitting test data. My proposed solution is to add two drop down menus, one will contain disto names e.g., "Ubuntu" and "Fedora", the second box will contain release/version e.g., "10.04" "11.2", thus cutting down on the distro list.

As it stands every distro has an entry for all the different version. So when I select PCLinuxOS only the correlating version entered by users would appear in the second drop down menu e.g., 2010 and 2011.9 would appear because those are past releases entered by PCLOS users on Wine.

[dimesio]

I'm sure everyone has realized how massive the distro list is when submitting test data. My proposed solution is to add two drop down menus, one will contain disto names e.g., "Ubuntu" and "Fedora", the second box will contain release/version e.g., "10.04" "11.2", thus cutting down on the distro list.

The problem with doing it that way is that different distros have different numbering schemes, and users would constantly be mixing them up, e.g., picking "11.04" instead of "11.4" for openSUSE.

[perryh]

"dimesio" <[email protected]> wrote:

glamdring wrote:

I'm sure everyone has realized how massive the distro list is
when submitting test data. My proposed solution is to add two
drop down menus, one will contain disto names e.g., "Ubuntu"
and "Fedora", the second box will contain release/version e.g.,
"10.04" "11.2", thus cutting down on the distro list.

The problem with doing it that way is that different distros have
different numbering schemes, and users would constantly be mixing
them up, e.g., picking "11.04" instead of "11.4" for openSUSE.

Not if the selection made in the distro box determined the set of
choices available in the release/version box.

[glamdring]

"dimesio" <[email protected]> wrote:

glamdring wrote:

I'm sure everyone has realized how massive the distro list is
when submitting test data. My proposed solution is to add two
drop down menus, one will contain disto names e.g., "Ubuntu"
and "Fedora", the second box will contain release/version e.g.,
"10.04" "11.2", thus cutting down on the distro list.

The problem with doing it that way is that different distros have
different numbering schemes, and users would constantly be mixing
them up, e.g., picking "11.04" instead of "11.4" for openSUSE.

Not if the selection made in the distro box determined the set of
choices available in the release/version box.

Yes, that is exactly what I was trying to say. Plus the release could be set just like the distro currently is, which allows users to create new ones. So if version 11 isn't in the list yet the user can add it.

To be clear selecting "Fedora" would only show release versions added to "Fedora"

Sorry for the confusion in the first post.

[dimesio]

Yes, that is exactly what I was trying to say. Plus the release could be set just like the distro currently is, which allows users to create new ones. So if version 11 isn't in the list yet the user can add it.

To be clear selecting "Fedora" would only show release versions added to "Fedora"

Sorry for the confusion in the first post.

Actually it was my fault for not reading carefully enough.

It's not a bad idea, but unless you want to submit patches yourself, the chances of it happening are slim. There's only one person working on the AppDB code. But if you really want to pursue it, file an enhancement bug. Just don't be surprised if it sits there for years, untouched.

[glamdring]

Yes, that is exactly what I was trying to say. Plus the release could be set just like the distro currently is, which allows users to create new ones. So if version 11 isn't in the list yet the user can add it.

To be clear selecting "Fedora" would only show release versions added to "Fedora"

Sorry for the confusion in the first post.

Actually it was my fault for not reading carefully enough.

It's not a bad idea, but unless you want to submit patches yourself, the chances of it happening are slim. There's only one person working on the AppDB code. But if you really want to pursue it, file an enhancement bug. Just don't be surprised if it sits there for years, untouched.

I will look into this tomorrow or at least very soon. Thank you for pointing me in the right direction!