Is there a way to receive notifications of new revs? Personally I like reading them; even though I understand very little it does give an indication of areas that are being changed / added.

Another quote: Apparently, MySQL doesn't like being asked the unsigned keyword on bit fields. It should have been smart enough to ignore them, but whatever... (install.sql)While I'm at it, minor regex simplifications. (install.php)

So one assumes that one can download those two files only and have the latest version of Wedge? (ie along with the zip I downloaded this morning[1].) And if so is there an easy was to do this as I am on hostel WiFi so downloading a Zip and uploading its contents is unfair.

You can also subscribe to the RSS feed.https://github.com/Wedge/wedge/commits/master.atomIt doesn't give you the number of line additions and deletions, though, which is a mood killer for me. I like being able to differentiate between "quick fixes" and "large commits".

Other than that, I'm planning to write some kind of script that'll use the RSS feed to get new commit IDs, then use the GitHub API to receive statistics for each of these commits, and then post them to a specific topic. This'll make a perfect candidate for a plugin, but honestly, if someone else could write it for me, I'd be thrilled... :P

So one assumes that one can download those two files only and have the latest version of Wedge?

Yes. But apparently, some servers don't play nice.I made a test install on my Wamp server, and it worked.I made a test install on wedge.org, and it worked.If it doesn't work elsewhere, it'll need fixing, but it's EXACTLY the reason I needed to go public at some point... Because there are more setups out there, and they need to be accounted for.

"If I do one at a time I'll be done in 10 years":lol: Only understood this once I looked at the change in github :)

"is there an easy was to do this (update my installation with the latest rev.s) as I am on hostel WiFi so downloading a Zip and uploading its contents is unfair."I've found that if I click on Commits it gives a list of commits, and clicking on each of these gives a list of changed files. And so I can download the latest zip and overwrite these files only :) (And I assume I have to clear the cache too.)

"is there an easy was to do this (update my installation with the latest rev.s) as I am on hostel WiFi so downloading a Zip and uploading its contents is unfair."I've found that if I click on Commits it gives a list of commits, and clicking on each of these gives a list of changed files. And so I can download the latest zip and overwrite these files only :) (And I assume I have to clear the cache too.)

Or use Github for Windows. Clone the repo then it will only download the latest changed files.

"is there an easy was to do this (update my installation with the latest rev.s) as I am on hostel WiFi so downloading a Zip and uploading its contents is unfair."I've found that if I click on Commits it gives a list of commits, and clicking on each of these gives a list of changed files. And so I can download the latest zip and overwrite these files only :) (And I assume I have to clear the cache too.)

Or use Github for Windows. Clone the repo then it will only download the latest changed files.

Thank you - yes that's what I do now, and then an FTP client synchronises what's on my PC to the web space. It's still a way away from a one-click solution but it's easier with less chance of missing changes.

Thank you - yes that's what I do now, and then an FTP client synchronises what's on my PC to the web space. It's still a way away from a one-click solution but it's easier with less chance of missing changes.

Eventually, I'll stick my finger out of my arse, and I'll write a module to automatically update files from github as long as you're using an alpha or beta install.

Then again, it'll probably come *after* I write the code to automatically update files on non-alpha versions. (Which, in this case, will only retrieve official releases.)

I don't now. For instance, with the German flag, simplifying it to only use 3 colors would bring the GIF size down to 99 bytes. After embedding and gzipping, it should be between 90 and 110 bytes. With SVG, I'm guessing it would have to be a bit more than 100 bytes just for the code itself, but it might compress much better. Still, SVG isn't supported by IE 6-8, so I don't know if it's worth dropping these to save a few bytes.

The change from PNG to GIF allowed me to save over 300 bytes per flag. Now THAT was worth it!! ;)

(BTW, I don't know if I'll keep the ability to have a PNG version around... I noticed that the board list needed a flag test as well, and it sucks. I'd probably have to store the actual extensions in the database or something, meh.)