To elaborate a bit... I considered using
pluginNamePlugin/config/settings.yml to pass information, but there's
no way for several plugins to share responsibility for contributing to
a single array of values.
That is, I could write this in fooPlugin/config/settings.yml:
all:
.settings:
pkContextCMS_global_buttons:
- foo: ... data here for foo's button ...
But the button setting for the 'bar' plugin wouldn't merge with this.
It would just smother it, depending on which one loaded first.
Correct?
I suspect I really do have to use a global variable to solve this
problem in a way that doesn't create serious chicken and egg problems
at installation time. Unless there's some other way for plugins to
declare an interest in each other that's quickly accessible at
runtime.
I could do it in app.yml like this:
all:
pkContextCMS_button_providers:
- pkMediaCMSSlotsPlugin
... etc ...
But this means that users must tweak app.yml by hand every time they
add a plugin simply to get normal and useful behavior that ought to be
the default. That fails to meet the "convention over configuration"
standard.
--
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---
