it may have been effective in 2000 something, but using .txt files as a way to input data is incredibly clunky, .txt files are not meant to be used this way.
Using .json files would be a far better alternative, as it is a far more structured way to input parameters that would likely lead to less issues.
We would still need to support .txt files as a way to input parameters as it is the only way that the executable form of 3pg is being used right now. However, once a way to parse .json files to input parameters has been implemented, it should be simple enough to create functionality that converts existing .txt input parameter files to .json.
NOTE this is not a particularly high priority, and is not necessary if it's not a feature that people do not want.
it may have been effective in 2000 something, but using .txt files as a way to input data is incredibly clunky, .txt files are not meant to be used this way.
Using .json files would be a far better alternative, as it is a far more structured way to input parameters that would likely lead to less issues.
We would still need to support .txt files as a way to input parameters as it is the only way that the executable form of 3pg is being used right now. However, once a way to parse .json files to input parameters has been implemented, it should be simple enough to create functionality that converts existing .txt input parameter files to .json.
NOTE this is not a particularly high priority, and is not necessary if it's not a feature that people do not want.