[eluser]Michael;[/eluser]
The config class as it is seems pretty easy, but at the same time overly complicated. In order to have config files grabbed by other classes as needed, is to have a bunch of different config files lying around... currently, I have 12 in the config folder of one application I am working on. Now obviously a few of them are going to be absolutely required to site in a flat file, like database and maybe a 2-3 others. But why not the option of having one config file that has all of the *required* information in it, and the rest could be stored in a variables table that items can either be retrieved from individually, or you can build a whole array of items if needed.
So - ideas, thoughts, comments, sarcastic remarks on how we might alter the existing setups to accomplish this?
Michael