[CGI] Add sha1 to mass add page [DONE/DENIED]
Moderator: AniDB
-
- AniDB Staff
- Posts: 335
- Joined: Tue Oct 01, 2002 11:13 pm
- Location: GOTT Head Office, Planet Aineias
[CGI] Add sha1 to mass add page [DONE/DENIED]
Well the subject says it all. I know that the mass page page predates the added sha1 sums, but it would be nice for a sha1 field to be added to the mass page in the future.
-
- AniDB Staff
- Posts: 438
- Joined: Thu Apr 08, 2004 1:43 am
- Location: Portugal
i think it would be nice to add to the mass add some more things besides the sha1 sum..
regarding the bitrates for audio and video, i thought of something like this, keep the existing one which serves as a default for all the added files but in each file i would put a text box for both the audio and video bitrates that would overwrite the default values, so that imagine all but two file have a diferent rate from the default rate, you just add it on the files and it would overwrite the default.
well, thats about it, otherwise the page is okay but sha1 sum would be nice for starters, it's less one thing ppl have to add afterwords.
regarding the bitrates for audio and video, i thought of something like this, keep the existing one which serves as a default for all the added files but in each file i would put a text box for both the audio and video bitrates that would overwrite the default values, so that imagine all but two file have a diferent rate from the default rate, you just add it on the files and it would overwrite the default.
well, thats about it, otherwise the page is okay but sha1 sum would be nice for starters, it's less one thing ppl have to add afterwords.
That makes you a bean counter... ^^
In HTML, the extra form fields take up at most 150 bytes each, including formatting tags and whitespace. Pipe that through gzip and see what's left...
In the data submitted by the user, it's an additional 10-20 bytes for the field name and the content, usually 3-4 bytes for bitrates and 48 bytes for an sha1 hash. Again, pipe that through gzip and...
The one thing that does bother me a little, tho, is the number of form fields on the page. It might easily become all too cluttered, and some browsers (including Firefox, unfortunately), have a real hard time scrolling pages with too many form elements.
In HTML, the extra form fields take up at most 150 bytes each, including formatting tags and whitespace. Pipe that through gzip and see what's left...
In the data submitted by the user, it's an additional 10-20 bytes for the field name and the content, usually 3-4 bytes for bitrates and 48 bytes for an sha1 hash. Again, pipe that through gzip and...
The one thing that does bother me a little, tho, is the number of form fields on the page. It might easily become all too cluttered, and some browsers (including Firefox, unfortunately), have a real hard time scrolling pages with too many form elements.
