Re: [Components] ezcConfiguration and multiple configuration files having the same name

2009-03-31 Thread Derick Rethans 
On Mon, 30 Mar 2009, Thomas, Maxime wrote:
 
 On Mon, 30 Mar 2009, Derick Rethans wrote:
 
  On Tue, 24 Mar 2009, Derick Rethans wrote:
 
   This could be broken caching, would you care to file a report so 
   that we can track this? I'll have a look at it then.
  
  I've had a look at the issue (and code now) and realized that this is 
  not a bug. If you init the manager, it re-sets the previous 
  configuration. This is what it is supposed to do.
  
  Are you trying to setup some kind of fallback mechanism here? If so, we 
  don't support that yet, but it sounds like a good addition.

 Yes, I guess it's my ez coloration...
 
 By the way, you explain me that if I reset the manager with a new init 
 call, I'm able to reach new settings of the new set configuration.
 
 But it's not working; I can't access settings on the new configuration 
 once it has been initialized.

I just checked that, and you're right. However, we provide the -reset() 
method to fix this, which can be a workaround. I however have 
addressed the issue in in SVN. I also added an issue for a 
fallback form of reading configuration files, but that's marked as a 
feature request for now: http://issues.ez.no/IssueView.php?Id=14709

regards,
-- 
Derick Rethans
eZ components Product Manager
eZ systems | http://ez.no
-- 
Components mailing list
Components@lists.ez.no
http://lists.ez.no/mailman/listinfo/components

Re: [Components] [Configuration] Quotes in ini files

2009-03-31 Thread Derick Rethans 
On Mon, 30 Mar 2009, Piotrek Karas wrote:

 I'm trying to use Configuration component to dynamically modify linux 
 configuration files. All seems fine except for string-based values 
 (both empty and non-empty ones) that get automatically quoted, for 
 example:
 
 Read operation:
 oldest_color = (136, 136, 255)
 
 Write operation:
 oldest_color = (136, 136, 255)
 
 Is it possible to avoid automated application of quotes (and just 
 leave that possibility for strings whose white spaces would NEED to be 
 preserved)?

We've a feature request for it here (with an explanation why it is like 
this): http://issues.ez.no/IssueView.php?Id=13244 At the moment we have 
not planned to implement this. A contribution for this would 
however be appreciated.

with kind regards,
-- 
Derick Rethans
eZ components Product Manager
eZ systems | http://ez.no
-- 
Components mailing list
Components@lists.ez.no
http://lists.ez.no/mailman/listinfo/components