There was some discussion on the latest announcement about the model checker. I thought I'd move it here with some specific ideas
1. Serve the checker as a normal webpage that displays instead of downloading (ie. without content-disposition:attachment). It's cool that you can download the .html and use it offline, but it shouldn't be necessary. This would greatly decrease the friction in actually opening the checker. Also using it online ensures you're always on a up-to-date version.
2. Allow the checker tool to accept zip files and check the contents by using a JS zip library. I think I posted a mockup for this when the checker was first announced. This would allow the checker to operate on the same .zip that you upload, which would allow checking image paths and also enable...
3. Add a button to run the checker on the zip on the model upload page. It would still run client-side, not server-side. It could also display a simple pass/fail, referring to the checker page in case of failure for the full report.
1. Serve the checker as a normal webpage that displays instead of downloading (ie. without content-disposition:attachment). It's cool that you can download the .html and use it offline, but it shouldn't be necessary. This would greatly decrease the friction in actually opening the checker. Also using it online ensures you're always on a up-to-date version.
2. Allow the checker tool to accept zip files and check the contents by using a JS zip library. I think I posted a mockup for this when the checker was first announced. This would allow the checker to operate on the same .zip that you upload, which would allow checking image paths and also enable...
3. Add a button to run the checker on the zip on the model upload page. It would still run client-side, not server-side. It could also display a simple pass/fail, referring to the checker page in case of failure for the full report.