2013-04-02, 22:25
I'll PM you links to the source code for each of those (as well as links where you can view them live)
Forgot to mention in both cases, clicking either the image thumbnail or the green "Y" will open the image in a "lightbox" style overlay so you can see it larger... and the little image you see under the *.nfo and theme spots is a generic image I used because the way I wrote the script can't seem to display the XML format of the NFO's or play any audio, but still shows a valid representation if the file is there or not. As far as the memory issue I mentioned, I think I may have worded that wrong, the sites themselves (and source code) are extremely small, about 235Kb or so uncompressed, I meant when you view the page in your browser, at least in Chrome it sucks pretty much all the RAM it can grab so I obviously have some form of leak in the code. There's 12GB of RAM on my HTPC and when I originally started loading that page had Chrome taking over 5GB of it before I killed the process... I was able to tweak and lower that a bit but I know it's still way too high to be reasonable for most users.
And with the timezone difference... I'm an insomniac, so I'm willing to test/help whatever time of day/night you need in most cases. As long as I'm not dealing with doctors that day I have NOTHING to do but watch TV or play video games... (I hate disability)
Forgot to mention in both cases, clicking either the image thumbnail or the green "Y" will open the image in a "lightbox" style overlay so you can see it larger... and the little image you see under the *.nfo and theme spots is a generic image I used because the way I wrote the script can't seem to display the XML format of the NFO's or play any audio, but still shows a valid representation if the file is there or not. As far as the memory issue I mentioned, I think I may have worded that wrong, the sites themselves (and source code) are extremely small, about 235Kb or so uncompressed, I meant when you view the page in your browser, at least in Chrome it sucks pretty much all the RAM it can grab so I obviously have some form of leak in the code. There's 12GB of RAM on my HTPC and when I originally started loading that page had Chrome taking over 5GB of it before I killed the process... I was able to tweak and lower that a bit but I know it's still way too high to be reasonable for most users.
And with the timezone difference... I'm an insomniac, so I'm willing to test/help whatever time of day/night you need in most cases. As long as I'm not dealing with doctors that day I have NOTHING to do but watch TV or play video games... (I hate disability)