Readers may recall me publishing a tool called Cycles Render Time Calculator (or CRTC for short) a while back. It was but a small little thing I wrote with the help of Rioforce to help us figure out approximately how long it would take to render his animations. Since then I have made minor updates to it but never really did anything with it (too many variables to create an accurate time, yada yada yada).
As I said, both versions contain a brand new, greatly improved code base following a practice explained on Codecademy a D.R.Y (Don’t Repeat Yourself), more concise messages for input fields, and overall a nicer UX. The website does not contain the General Animation mode like the original Python version does, but it wasn’t really necessary to add. I have thoroughly tested the website across many browsers, both Desktop and Mobile, to ensure it all works. Desktop browsers work the best, with Mobile Opera and Mobile Chrome doing poorly. Apologies for the not-properly-centered text. I tried to fix it but it always came out worse, and when I went back this morning to try again, the site on which a person who suggested a fix has an error so I can’t view the chat logs. 😦
Another major difference between the Website and the Python version is a different open-source license. While the Python version is under the GPLv3, the website is licensed under The MIT License (the first time I have used that license). Further more, I have made use of the CSS Browser Selector library, originally created by Rafael Lima and licensed under the
CC BY 2.5.
The website is hosted using GitHub Pages, which allows for static elements. Since CRTC was already on GitHub, I figured I would go ahead and make use of it to host the site.
P.S. 27 DAYS UNTIL MY FIRST SEMESTER OF COLLEGE ENDS!!! 😀