configure
has become a bit of a monster, as it has monolithically grown over the ages. The reason it grew rather than being sensibly extended was simply an attempt to maintain it independent of the
lib
directory. The code is a mess, and needs splitting up and restructuring to support modern demands, such as pluggable checkers.
CC
It should also be made friendlier for beginners. When you start up configure, you will get a lot of errors and warnings, while most of the time you should just click on Next. A wizard-like approach would be better.
AC
That wasn't the main thrust of what I am doing, but it is certainly worth looking at.
CC
First thing i did was to require a button press to see EXPERT settings.
CC
Removed "Being worked on" status because of empty "Waiting for" field.
CC
Improved the reporting of missing modules to give some help; and refined the EXPERT so that if there is an error in an expert setting it shows in a normal view.
CC
Improved the code to avoid warning
CC
non
SMART entry that hasn't been used in a while - closering.
--
SvenDowideit - 31 Jul 2008