Major overhaul

As you may have noticed by now, Score Keeper has undergone a major overhaul.

If you experience any errors, please use the Feedback link in Score Keeper to notify me.

I hope to finish a writeup about the new Score Keeper and its roadmap soon - in the meantime, have fun! I hope you like it.

Clean sheets and locked games

Two small features were added to Score Keeper this evening:

1. You can now lock games if you want to prevent users from adding matches. This is useful if you have games such as “Foosball, January - March” and want to make sure users don’t add matches to the old games.
2. Score Keeper can now keep track of clean sheets (games where one team doesn’t get any points) which are called out in the events block. Enable this in the game settings.

Other than that, I upgraded Rails to 2.3.5 and fixed a bug with the caching that caused “Matches played per day” to not update “Today” to “Yesterday” and so forth until a new match was entered.

Performance improvements

This weekend I spent some quality time with Score Keeper working to improve performance.

First of all, memcached was installed and the dashboard is now cached. This lowered the execution time for that page by an order of magnitude from about 300ms on average to 25ms.

All icons are now in a single CSS sprite which is further optimized by running optipng on it. That way, all icons and the logo are in the same 7kb file which saves 10 HTTP requests.

Ruby on Rails was upgraded to the latest version 2.3.2, which saves memory and has a bunch of optimizations of its own.

Other than that, I did some small tinkering, such as moving the Google Analytics javascript below the page’s javascript, which means that e.g. table sorting is operational about 1 second faster.

A lot of code was moved around and rewritten during this process, so let me know if you discover any bugs, new or old.