New HoF brain storm

[WraithLord]

I don't want full blown DB.
I want a human readable, none XML, text file. I'll implement data access and logic myself.

[WraithLord]

That's the format, ex:
[
Winner: Jazzepi
Game: Epiphany
Game Link: http://www.shrapnelcommunity.com/thr...b=5&o=&fpart=1
Players: 11
Nation: LA T'ien Ch'i
Mods: Well guarded neutral Emor citadels as VPs
Era: Late
]

[
Winner: Calmon
Game: the Quick and the Dead
Game Link: unknown
Players: unknown
Nation: LA Ermor
Mods: unknown
Era: unknown
]

The parser is almost ready. It doesn't care much for white spaces and it's flexible so I can adapt it quickly to changes.
I'm using Python btw, Perl would've got the job done faster but I wanted a tidy OO program and not a quick and dirty perl voodoo.

[Hadrian_II]

Originally Posted by WraithLord

I don't want full blown DB.
I want a human readable, none XML, text file. I'll implement data access and logic myself.

whats wrong with XML? i think there are free XML libs out for every programming language. If you use XML you dont have to write a custom parser for a custom format (what in my opinion just sounds like unnecessary work).

Originally Posted by WraithLord

However you see it there's just no way to avoid manually building the DB. If I get help in this it will cut the time to completion by half. Otherwise my plan is to complete the report gen. engine and then get to manually feeding the DB. It's not that bad, mind you, most of the posts are compatible with my parser (just add [ and ] lines with simple awk/sed script or by hand), so it's down to copy/paste.

Why not create a simple web form, and fill the db with the input. I suppose it is not harder for players to report victory to a webpage, than to a forum post.

[WraithLord]

KISS.

I don't want XML. I personally don't care much for it. It has it's uses of course but IMO it's useful for higher caliber projects, like defining protocols or modeling etc. For simple game report DB it's a bit more than what's required.

Of course both your ideas can work. They'll require a bit more work than what I had in mind that's all. If anyone wants to bring to the table an end product that does the DB/report generation magic then I'm all for that. Go for it

For now I'll stick with my plan. It's simple to fill (no change to current report). Simple to copy to DB. Simple to export. yata yata.

I appreciate and respect the advice given but I'm not convinced. It's a very small use case and I don't see any need to go overboard.

I want to bring to discussion another aspect. Not technical.
I don't think the current ranking system makes much sense in the way it factors wins against magnitude.
Ex:
player A won 3 games of 6 players each.
player B won 2 games of 20 players each.
The current system would put A above B. I don't think it makes sense. Player B has won much bigger games, defeated more opponents and invested much more time. Am I missing something here?