Berg wrote:
Your reply again does not reflect the topic you are replying to you claim knowledge about the conversion of csv to ini yet all you have input to this thread is "it will make the mod downloads bigger" .
No, that's not what I said. Learn to read. I said that THIS new effort put into csv to ini conversion just cancel any argued advantage the .ini had (easier to read than .csv UNLESS we spend time on some reading tools) and therefore, the only effect remaining from that conversion is bigger files.
Your claim to have hosted thousands of game is total crap going by the stats i have made up out of thin air like you often do your game have total 0.005 of total games played on the net.
Your not helping!
You could have used the header of the CSV to identify the columns. Most files already had an header.
Cybersphinx, what was the problem with opening them into a spreadsheet editor ? It was easy enough to read there. It was possible to compare weapons over one another there. Now with an .ini file, it's actually harder; We'll need to scroll up and down to do so.
Iluvalar wrote:You could have used the header of the CSV to identify the columns. Most files already had an header.
Cybersphinx, what was the problem with opening them into a spreadsheet editor ? It was easy enough to read there. It was possible to compare weapons over one another there. Now with an .ini file, it's actually harder; We'll need to scroll up and down to do so.
Iluvalar wrote:You could have used the header of the CSV to identify the columns. Most files already had an header.
NoQ wrote:I didn't like the idea of trying to achieve less than one line of code per ini file field, as in some unpredictable places we could really use arbitrary flexibility, such as complicated guessing of new field values depending on multiple other field values from different files.
Not only file format has changed. Some fields were added, some were renamed, some were removed. Providing code for exceptions to this routine only will lead to a much more complicated code.
Let's see if Duha comes up with anything though (:
I guess i'd do it my way as it's currently going very quickly (10 minutes per file convertor, until i get to research, where, thanks to Duha, we already have a code to merge).
Also i renamed the repo and thrown more stuff into it (including a tool for checking correctness of conversion by comparing ini files), see also.
NoQ wrote:I guess i'd do it my way as it's currently going very quickly (10 minutes per file convertor, until i get to research, where, thanks to Duha, we already have a code to merge).
Also i renamed the repo and thrown more stuff into it (including a tool for checking correctness of conversion by comparing ini files), see also.
As you wish.
I think you can add me to you repo. I will move all my tools to it as separate folder.
I am prefer to use python2 (I am coding on it at work, And it still more common now.) But can convert libs to work with ini to work with both versions.
Bump this, i think i accidentally finished the upgrade support.
The convertor is mostly functional.
Probably some stuff in other files has changed since last time i checked it.
P.S. Just curious: guys, what's going on in the repo? >_<
validating propulsionsounds.ini(g:\warzone2100\data\base\stats\propulsionsounds.ini) ... OK
validating research_cam1.ini(g:\warzone2100\data\base\stats\research_cam1.ini) ... Failed. Has errors or warnings in 12 sections
CAM1WEAPONS
researchPower use default value(0)
researchPoints use default value(0)
R-Struc-Factory-Cyborg-Upgrade01
has additional keys ['resultFunctions']
ADVANCEDRESEARCH
researchPower use default value(0)
researchPoints use default value(0)
R-Struc-Factory-Cyborg-Upgrade03
has additional keys ['resultFunctions']
...