Luke-Jr wrote:All the code assumes no 'category' is "".
a) code follows design, design follows the requirements. Not the other way round.
b) what "All the code"? sortresources.py and gParser.cpp use an XML library that respects the DTD and automagically inserts the defaults, whatever they may be.
Luke-Jr wrote:Unsorted, not sorted as "unsorted". Unsorted stuff just doesn't go into a category.
Aha, interesting. So you have a desk drawer for office supplies, one for blank paper, one with electronic gadgets, one for manuals, one for CDs. And all the stuff that does not fit into a category you already have goes to your desk. Or the floor.
Luke-Jr wrote:...but categorizing it as "unsorted' doesn't do much useful.
Another one of those completely out-of-the-air proclamations. It does help to keep the user's main directory clean. Yes, we don't *have* to help our users to get at least a bit organized, but I *want* to.
Now, Luke, I'd like to say the following and I hope it does not arrive to rude: I don't consider convincing you that something is a good idea to be mandatory for actually doing it. See, with every other team member, I know that the amount of work he puts into arguing against something is directly proportional to the importance times the perceived badness of the idea. And the constant of proportionality is moderate; if anyone else argues for one forum page against, say, dropping support for OSX, I know it is really important and that he thinks it's a bad idea of the bungee jumping without cord caliber. You, however, can fight for pages and pages against changing the default color of those little up and down arrows that appear in the menus to yellow. Maybe all those little things really are that important to you, maybe you just have fun arguing, but your constant kicking and screaming only achieved one thing: I don't trust your judgement. First, not your judgement of importance, and that casts a shadow over the rest.
Release process is rolling. Sources are tagged, builds are building. Upload probably tomorrow. Source tarball attached.
You do not have the required permissions to view the files attached to this post.
If a user with "obsolete" libxml builds the game, the DTD's won't be downloaded, so if we want old maps (and OLD here means using the beta3 dtd or earlier) to continue to work there, we have to include the old dtds exactly where the code wants them to be. Faced with the choice of extended compatibility vs. a tidy root resource directory, I choose the compatibility.
