[geeklog-devtalk] geeklog-devel digest, Vol 1 #398 - 2 msgs

[geeklog-devel-request at lists.geeklog.net]

Send geeklog-devel mailing list submissions to
	geeklog-devel at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.geeklog.net/listinfo/geeklog-devel
or, via email, send a message with subject or body 'help' to
	geeklog-devel-request at lists.geeklog.net

You can reach the person managing the list at
	geeklog-devel-admin at lists.geeklog.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of geeklog-devel digest..."


Today's Topics:

   1. Minor suggestion for Geeklog (Tom Willett)
   2. Re: Minor suggestion for Geeklog (Vincent Furia)

--__--__--

Message: 1
From: "Tom Willett" <tomw at pigstye.net>
To: geeklog-devel at lists.geeklog.net
Date: Sat, 25 Sep 2004 00:51:45 +0000
Subject: [geeklog-devel] Minor suggestion for Geeklog
Reply-To: geeklog-devel at lists.geeklog.net

I would like to make a minor suggestion that would make upgrades much easier 
and perhaps could avert a lot of install problems.

Have two configuration files.  One the normal config.php we are all familiar 
with.  The person installing geeklog should never make changes to this file.  
The other configuration file would contain things that must be changed and 
only the configuration options the installer wanted/needed to change.

Then the last thing in the normal config.php would be to include the 
site.config.php file.  The changes in the site.config file would override the 
normal config.php and everything would be good.  This has several advantages.

To upgrade, normally only minor or no changes would be required to the site 
config file and the normal config.php would be replaced.  No editing required.

Most of the paths, which people change when they shouldn't, would remain 
untouched in the normal config.php.  It would remove some of the temptation 
to mess with them.

This would only require the creation of a minimal site.config.php (name it 
something like site.config.php.example to prevent its overwriting the real 
site.config.ph) and the include in the normal config.php.  Of course you need 
to place warnings in the config.php to not make any changes in this file.

The same idea will work with language files and avert the problem of 
incomplete language files.  Always read the english file and then just 
overlay it with another language file if wanted.  Quick changes to the 
english file can be made and distributed and it will not break the others.  
This would only require some simple logic changes in the includes.


A minor change that would make things more robust.

--
Tom Willett
tomw at pigstye.net


--__--__--

Message: 2
Date: Fri, 24 Sep 2004 23:32:52 -0400
From: Vincent Furia <vfuria at gmail.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] Minor suggestion for Geeklog
Reply-To: geeklog-devel at lists.geeklog.net

I agree with Tom.  At least for config.php.  I'd like to see how big
an impact in performance there would be before we implemented
something like this for languages.

-Vinny

On Sat, 25 Sep 2004 00:51:45 +0000, Tom Willett <tomw at pigstye.net> wrote:

> I would like to make a minor suggestion that would make upgrades much easier

> and perhaps could avert a lot of install problems.

> 

> Have two configuration files.  One the normal config.php we are all familiar

> with.  The person installing geeklog should never make changes to this file.

> The other configuration file would contain things that must be changed and

> only the configuration options the installer wanted/needed to change.

> 

> Then the last thing in the normal config.php would be to include the

> site.config.php file.  The changes in the site.config file would override the

> normal config.php and everything would be good.  This has several advantages.

> 

> To upgrade, normally only minor or no changes would be required to the site

> config file and the normal config.php would be replaced.  No editing required.

> 

> Most of the paths, which people change when they shouldn't, would remain

> untouched in the normal config.php.  It would remove some of the temptation

> to mess with them.

> 

> This would only require the creation of a minimal site.config.php (name it

> something like site.config.php.example to prevent its overwriting the real

> site.config.ph) and the include in the normal config.php.  Of course you need

> to place warnings in the config.php to not make any changes in this file.

> 

> The same idea will work with language files and avert the problem of

> incomplete language files.  Always read the english file and then just

> overlay it with another language file if wanted.  Quick changes to the

> english file can be made and distributed and it will not break the others.

> This would only require some simple logic changes in the includes.

> 

> A minor change that would make things more robust.

> 

> --

> Tom Willett

> tomw at pigstye.net

> 

> _______________________________________________

> geeklog-devel mailing list

> geeklog-devel at lists.geeklog.net

> http://lists.geeklog.net/listinfo/geeklog-devel

>



--__--__--

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel


End of geeklog-devel Digest