making apps, making webs.

Marcus and I started up a weekly pygame sprint for a few hours on Wednesdays/Tuesdays. Using this link you can find out what time it starts in other places: http://www.worldtimeserver.com/time_converter.aspx?f=AU-VIC Germany: Tuesday 10pm UK: Tuesday 9pm US: Tuesday 4pm AU: Wednesday 6am What happened in this weeks mini sprint I collected all of the bugs and patches together onto a todo page . This took a while, so I didn't get that much work done on code things. Marcus got the font metrics patch integrated. This allows pygame access to font metrics information. To understand what font metrics are read this . Pango seems to be the preferred way forward for fonts. There are plans for pygame support of Pango too. The scrap clipboard module also got some love from Marcus. It's much more complete than the last version that's been in svn for a few months now. You can get all different types of clipboard data. I even managed to paste an image from The Gimp into my pygame

All of your web applications should have an automated backup - and restore procedure. For web applications, allow your users to back up their accounts. Luckily many web hosts have backup software enabled within their control panels (cpanel etc). So it's easy to set up automated backups from these control panels. End users should also have the option of backing up their data. Just so they can have an extra piece of mind. If they stuff something up, they can just restore from a backup. Pretty simple. An sql dump might not be the best backup format... although it's pretty good. Maybe you didn't separate your data for different users when you designed your database. So just doing a database dump might not be available. If you give them a database dump they might get other clients data. You might need to write a custom backup procedure - one which knows how your database is designed. I guess this is why most web applications fail to give end users backups - All of the u