Re: [Phpwiki-talk] index.php vs config.php

[Jeff D. <da...@da...>]

> A proposal:

It sounds like a decent one.

A few not particularly germaine comments:

> Config applications:
> n) more options, such as a plugin to a web management app (webmin), a 
> GUI app (Gnome or KDE), or perhaps a ncurses app.

Just in case you're seriously considering writing something like that:
keep in mind that (I think) the way to go is to use a scripting-type
language (e.g. python or perl) with GUI (or curses) bindings.  Development
is
much easier (IMHO), and the result is (or can be) much more portable
(easily).  (A fair amount of our user base seems to be Windows based...)
(Or one could use Java... which makes it, in theory (haha), automatically
portable...)


> class valid_bool{
...
> 	is_valid($new){
> 		if(is_bool($new)){
> 			$this->new = $new;
> 			return true;
> 		}
> 	}

Since it changes the state of the valid_bool object,
is_valid is a BAD, BAD method name.  (Should be,
maybe, set_new(), or set_new_checked() or something
like that.)

> ... thus config-valid.php would be the authoritative source.
> 
> Configurator.php and cli-config.php would just know how to use the tools
> 
> presented by config-valid.php and generate an interface.

Seems good.  "One authoritative source" is a good goal.
And if it's in PHP (rather than something we have to parse)
life will be easier.  (Until you want to write the fancy GUI
C/perl code...)