@Feedback - Nice catch. The parens are absolutely necessary. . . . Fixed in repo for you to test.
@Alerum - I would recommend updating release version numbers in files as part of the release part. Actually, we'd avoid doing releases until 1.0 and force people to use SVN to save some effort. The other benefit is that people are then always testing the latest as long as they update. Your call since you've been doing the releases.
The job is awesome so far! And it's only about 4 miles from my apartment. Hopefully I can get off my lazy ass and start biking like I did when I lived in SF.
@Ruff - That looks very cool. My first thought is to not put the scheme-per-era into the options screen, forcing people to modify the INI if they want that, simply because it sounds like a LOT of options. How are the options set for a single era? For example, how do you choose which format to display? I'm talking about the code here. Is it a bunch of booleans, or a format string or an int code?
For example, if it's a bunch of individual options, from your post it looks like you'd have.something like this:
Code:
o Include Civilization Name
o Include Unit Type
o Number before Unit Type
o Separate with Spaces
Number format: Decimal (1 2 3), Roman (I II III), Ordinal (1st 2nd 3rd) [dropdown menu]
But this of course only covers what you showed. You listed a lot more mods with different variations. The options screen could easily explode.
@Cammagno - What I meant about having building classes as addable column sets in CDA's customize screen is to make it easier to make your pages. For example, to make the religious building screens, you have to add each building to a screen. If someone makes a mod that adds a new religion, your page would have to be updated.
Instead, when making your page you'd add one column called "Religious Buildings" which would, when displayed, add all existing religious buildings as separate columns. Mods with new religions would work out-of-the-box. This is a lot more work than just putting in icons for headers, so it'll have to wait. I'll see about bumping up the priority of that.
@All - I'm trying to as much as possible make sure each task I do exists as a task in SF.net before starting it. This does a couple things: others can pick up tasks and prioritize them. As well, we'll all have a better idea of what each of us is doing. Don't go too fine-scale and make a bunch of work for yourselves. Just put in a high-level task when you think of it. This also helps me to not forget ideas I had earlier.
It's fixed and in the repo.
