>One example of my opinion is that I prefer tools that produce code or some >file that can be edited later if you wish to tweak things. The tool >BasConfig (for creating Config Blocks for SB programming) is OK to create a >Config Block, but it does not allow you to edit a definition and expand on >it (say, adding another Config Item). I wrote FileConfig to get around >this. The user creates a definition file for the Config Block (using an >editor). The Config Block definition is run through FileConfig and out >pops a new Config Block (binary file). You need to add another Item? Edit >the file, run it through FileConfig and, bingo, a new item is added. With >BasConfig you have to start from scratch each time. This can add up if you >have 20-50 Config items.
Absolutely. BasConfig is OK for small level 1 config blocks or blocks you know will never change. Is your FileCOnfig able to create level 2 config blocks now, Tim? -- Dilwyn Jones [EMAIL PROTECTED] http://www.soft.net.uk/dj/index.html
