[dev] Re: [cvs] commit: horde/config registry.php.dist imp/lib api.php horde/lib api.php nag/lib api.php juno/lib api.php merk/lib api.php scry/lib api.php agora/lib api.php genie/lib api.php goops/lib api.php jonah/lib api.php klutz/lib api.php midas/lib api.php mnemo/lib ...

[Jan Schneider]

Zitat von Marko Djukic <mdjukic at horde.org>:

> Quoting Chuck Hagenbuch <chuck at horde.org>:
>
>> Quoting Jan Schneider <jan at horde.org>:
>>
>> >   Log:
>> >   Blocks are no longer defined by the applications' api.php files or
>> >   registry.php. Instead we scan all application/lib/Block directories
>> > for   blocks once per session now.
>>
>> What this takes away is the ability to disable blocks by only 
>> touching config
>> files, instead of code (which we had for Horde, though not 
>> applications). Any
>> thoughts on how we could provide that with this scheme?
>
> Have the blocks list appear in the conf.xml generation screen 
> (something similar
> to the app menu selection) and the blocks can be explicitly disabled 
> (enabled)
> in the conf.php?

Haven't even thought of that. My original idea was to allow to override
block configuration (and turning them off completely for that matter) in
registry.php. But embedding blocks configuration into our conf.xml system
would be absolutely cool.

Jan.

--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting.php