chtml Testing

[Fyron]

I need some help testing the behavior of chtml, especially on XP systems. Note that this is highly beta (perhaps alpha) version.

chtml_2006_05_09.zip

Please download the archive and extract it into the SE4 folder. It will go into a "chtml_2006_04_16" folder.

Run it by double clicking chtml.exe and choosing option 2, to parse settings.ini. The interactive option (1) is not working at present. It is currently configured to read the stock data files and create single HTML files for them in "chtml_2006_04_16\out\". It only reads 6 of the files at present.

You should get some valid html files created in the out folder. If so, please open settings.ini and change inFileDir to point to a mod. If you wish to try TDM-Modpack, change it from:

inFileDir := ..\Data\

to:

inFileDir := ..\TDM-Modpack\Data\

It should happily overwrite any files it needs to in the out dir. For the most complete test, it might be useful to manually delete them before running chtml again, however.

Try a few mods out, see if the output makes sense for the mod (and is not consisting of empty files). Then, please report on what worked and what didn't work.

[Captain Kwok]

A couple of early comments:

The readme.txt file is kind of garbled with notepad, but works ok with Textpad.

Also, none of the formatting options seem to work. I tried choosing them by number and it kept saying it was invalid input...

The MS-dos prompt thing is cumbersome, particularly considering I haven't really used such things in the last 10 years or so.

Note I have XP Pro SP2.

[Fyron]

Probably should have mentioned that the interactive mode isn't quite upgraded yet, and the readme is reflective of that as well. Been working on making the functionality work with the settings file parsing.

Notepad doesn't interpret newline characters properly. It only likes carriage return gobbley-gook.

[Captain Kwok]

What about making it a more traditional windows program with some sort of GUI? I'd be more inclined to fudge around with it.

[Fyron]

The only user interaction is choosing some settings, which in the current implementation is best done with settings.ini. A GUI would be a lot of work (possibly more than the rest of the program) to basically replicate a text file.

[Captain Kwok]

It shouldn't be all that hard to make two text fields for input and output directories plus some radio buttons for the output options.