Re: Conf: argue !

Jean-Christophe Michel schrieb:
> Manuel Holtgrewe wrote:
> 
>>>> Good point. We could make configuration values "translateable" and 
>>>> support @TOKEN@ style tokens.
>>>
>>>
>>> Very complex imo. And we won't be able to use conf for translation, 
>>> since translation must work before conf is parsed ;p
>>> Raw is good, or we need to add a simple way to tell "replace this php 
>>> constant by its value at runtime".
>>
>>
>> Okay, so we allow this, too. Then, we'd have to tag this somehow. 
> 
> 
> 
> In fact I wonder wether we need sthg more than BC_BASE_URL prefix when 
> using "raw" type. Seems to be the case in berkeleymedia, in two sites I 
> have here in progress. If it's confirmed, then a conf type "url" 
> automatically prefixed by BC_BASE_URL would be enough. This would be 
> better, so no php code would be stored in db ;-)

Hm, what about having @@FOO@@ token replacment in configuration values. 
Conf would be passed a "translation" array that has the token keys as 
keys and the values to translate to as values.


Manuel