I tried to add an appdb entry for FINView because it's one of the applications required by the LiMux project, and I'm trying to add links into the appdb for all apps listed on http://wiki.winehq.org/LiMuxWineKeller . It's an addon for a commercial product I don't have, so I couldn't test it. That means I had to lie to the appdb to get it to accept the entry.
Appdb maintainers, please remove the "only submit tested applications" restriction from the appdb, or at least allow people who know what they're doing to get around it.
What would the purpose of having untested applications in the appdb be? Users would search for the app and find that it shows up but then find that it doens't work. I'd prefer we simply left out untested applications to keep the signal-to-noise ratio high.
Chris
On 3/10/07, Dan Kegel dank@kegel.com wrote:
I tried to add an appdb entry for FINView because it's one of the applications required by the LiMux project, and I'm trying to add links into the appdb for all apps listed on http://wiki.winehq.org/LiMuxWineKeller . It's an addon for a commercial product I don't have, so I couldn't test it. That means I had to lie to the appdb to get it to accept the entry.
Appdb maintainers, please remove the "only submit tested applications" restriction from the appdb, or at least allow people who know what they're doing to get around it.
Chris Morgan wrote:
What would the purpose of having untested applications in the appdb be? Users would search for the app and find that it shows up but then find that it doens't work.
At which point the application would qualify as been tested, no?
Felix
On 3/10/07, Felix Nawothnig flexo@holycrap.org wrote:
Chris Morgan wrote:
What would the purpose of having untested applications in the appdb be? Users would search for the app and find that it shows up but then find that it doens't work.
At which point the application would qualify as been tested, no?
Felix
Until the test results are added we simply have a placeholder in the appdb to confuse people. If they don't find the application in the appdb they know just as much as if they had found it.
Given the huge number of windows applications we might end up with hundreds of untested applications.
Chris
Søndag 11 mars 2007 00:51, skrev Dan Kegel:
I tried to add an appdb entry for FINView because it's one of the applications required by the LiMux project, and I'm trying to add links into the appdb for all apps listed on http://wiki.winehq.org/LiMuxWineKeller . It's an addon for a commercial product I don't have, so I couldn't test it. That means I had to lie to the appdb to get it to accept the entry.
Appdb maintainers, please remove the "only submit tested applications" restriction from the appdb, or at least allow people who know what they're doing to get around it.
At least in the past, there were some applications in the database without test results. This led to users asking questions about what was wrong, or reporting them (correctly) as errors and prompting their deletion.
Finding out which applications work with Wine is the only purpose of the AppDB, and people will lose the overview if we make it a general application database. Sure, we have download browsers and links to patches etc., but that is only supplementary information.
Besides, submitting applications that no one maintains means the data will become outdated pretty soon. If people were to expect every application in the world being in the database, they would also expect the information to be up to date at all times.
Regards,
Alexander N. Sørnes
-
Alexander Nicolaysen Sørnes -
Chris Morgan -
Dan Kegel -
Felix Nawothnig