Page 5 of 5
Re: need help reading .ini file
Posted: 26 Oct 2013, 20:04
by Per
Yes, names.txt should slowly be phased out of existence. Patches to add names to .ini files that are missing them, and removing unused names from names.txt would be most welcome.
Re: need help reading .ini file
Posted: 27 Oct 2013, 01:58
by Duha
crab_ wrote:Hello.
I can turn names of cyborgs from names.txt into templates.ini, if someone will write codes it in hardcode
First step is to make patch for ini files and attach it to ticket in track. If you want to do it do it or I can do it.
Per wrote:Yes, names.txt should slowly be phased out of existence. Patches to add names to .ini files that are missing them, and removing unused names from names.txt would be most welcome.
I make pull request with little phase
After move of templates I will make some hand clean.
*.po files has a lot of entries to names (#: data/base/messages/strings/names.txt:783) may be we should delete this comments?
Re: need help reading .ini file
Posted: 27 Oct 2013, 02:22
by cybersphinx
Duha wrote:*.po files has a lot of entries to names (#: data/base/messages/strings/names.txt:783) may be we should delete this comments?
Those will be automatically removed once the files get refreshed for master/3.2.
Re: need help reading .ini file
Posted: 29 Oct 2013, 22:32
by Duha
Per wrote:Yes, names.txt should slowly be phased out of existence. Patches to add names to .ini files that are missing them, and removing unused names from names.txt would be most welcome.
Do you plan to accept pull request with remove default values?
https://github.com/Warzone2100/warzone2100/pull/44
Re: need help reading .ini file
Posted: 29 Oct 2013, 23:38
by Per
I think that has already been merged as part of
https://github.com/Warzone2100/warzone2100/pull/43 ?
You should squash and clean your pull requests, I think. Or post changes as a patch on the bug tracker. When a pull request says "Cjkjvfnby wants to merge 45 commits into Warzone2100:master", I become rather hesitant to merge it...
Re: need help reading .ini file
Posted: 30 Oct 2013, 09:00
by Duha
Not this is another part.
You should squash and clean your pull requests, I think. Or post changes as a patch on the bug tracker. When a pull request says "Cjkjvfnby wants to merge 45 commits into Warzone2100:master", I become rather hesitant to merge it...
Pull request are pretty if they are just from master. After merging into it updates from master they are became a mess. Only 21 commit of pull request belongs to this branch other are taken from master.
Please reject github pull request. I have done track ticket #4100
Re: need help reading .ini file
Posted: 11 Nov 2013, 01:46
by Duha
I think about sorting ini files.
two phases of sorting:
1. sort by ID (ZNULL* first others by abc).
2. sort keys in same order as they described in header.
reason:
1. little improvement of readability
2. my tools for work with ini files does not support order. Adding new field convert patch to real mess.
I create patch with moving names to templates (ini files only) (#4106)
Ticket with removing default values is still waiting (#4100)
PS. Looks like ticket where per is author broken for me:
{9} Commits per author
Re: need help reading .ini file
Posted: 13 Nov 2013, 00:51
by Duha
How did pie files resolved for mods?
base + modpies or base + mp + modpies?
Re: need help reading .ini file
Posted: 13 Nov 2013, 19:26
by NoQ
There's single physfs instance, which first gets populated from base, then, if we are playing skirmish or multiplayer, mp gets written over it. Whatever files are present after that are used.
There's nothing special about PIE files in this process.
Re: need help reading .ini file
Posted: 21 Nov 2013, 14:53
by crab_
Hello.
What you think about idea: add 'description' field to each component in game?
This description can be shown in unit design screen
Re: need help reading .ini file
Posted: 27 Nov 2013, 11:43
by Duha
crab_ wrote:Hello.
What you think about idea: add 'description' field to each component in game?
This description can be shown in unit design screen
It is possible to make description based on component type.