1) Hmm.. I can see the need, but I can also see the danger.
I guess if we add the interface, we'd also be able to filter and control what input is given, which should help reduce the danger, but it would need some heavy checking for ranges, and recommended values, etc..
Can also have it hide or grey-out the variables that don't apply with the current settings.
2) I was already thinking of reworking it so that the DA binaries know what each setting's KB/versions page is, and has an included text description.. so I don't need to manage that other id=284 page.
Perhaps linked into the skin language packs, in the en/internal directory.
3) Another thought.. was to add a new column in the versions system database.. where I'd simply store the directadmin.conf variable.. although searching for "directadmin.conf variablename=" would also get you fairly close to all the results.
----
In any case, I'm still leaning towards #2... which would make adding it to the GUI much easier.. either way would need to create a new variable system first, then just fill it in for each of the many variables (which is a project in itself)
Thoughts are welcome.
John