http://bugs.winehq.org/show_bug.cgi?id=15477
Summary: Test.winehq.org should allow comparing selections side by side Product: WineHQ.org Version: unspecified Platform: All URL: http://test.winehq.org/data/ OS/Version: All Status: NEW Keywords: source Severity: enhancement Priority: P2 Component: www-unknown AssignedTo: wine-bugs@winehq.org ReportedBy: austinenglish@gmail.com
Currently, on test.winehq.org, you can only view two test results side by side if they're from the same OS version. It would be great to be able to select two results and compare them side by side. That way, one could compare the same machine when run under wine and windows, for instance.
http://bugs.winehq.org/show_bug.cgi?id=15477
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|All |Other OS/Version|All |other
--- Comment #1 from Austin English austinenglish@gmail.com 2012-02-23 15:19:53 CST --- Removing deprecated 'All' Platform/OS.
http://bugs.winehq.org/show_bug.cgi?id=15477
Helen Hernandez lilhomiefoo@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lilhomiefoo@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=15477
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fgouget@codeweavers.com
--- Comment #2 from François Gouget fgouget@codeweavers.com --- This is not to say that this is a bad idea but this will essentially require a total rewrite of the test.winehq.org site.
If I remember correctly everything under data/ is static pages currently. When a new report arrives a couple of scripts are run and generate pages for the new report and rebuild a few indexes.
Generating static pages for any two pair of reports for the current 30+ reports would cause an explosion in the number of indexes to generate (worse if more than two reports can be compared) and would most likely not be workable. The solution is to generate the pages dynamically... from page fragments? From a database?
Volunteers?