Metadata
- Source
- FLUID-5263
- Type
- Improvement
- Priority
- Major
- Status
- Open
- Resolution
- N/A
- Assignee
- N/A
- Reporter
- Anastasia Cheetham
- Created
2014-01-30T14:07:06.820-0500 - Updated
2021-07-29T01:35:59.642-0400 - Versions
- N/A
- Fixed Versions
-
- 5.0
- Component
-
- Prefs Framework
Description
Right now, the only way to specify the panels that should be present in a prefsEditor is to specify them through the schemas or grades that are used directly to build/instantiate the prefsEditor.
I can envision a use case of two CMS plugins (say, plugins for WordPress, or Drupal, or Joomla):
1) a PrefsEditor plugin that adds the starter-panels-version of a prefsEditor to the site, and
2) a plugin for X (say, the VideoPlayer), which would like to add some panels to the prefsEditor
The only way the X plugin could add panels to the PrefsEditor is to use old-fashioned, deprecated demands blocks.
Obviously, we're trying to get rid of the use of demands blocks. It would be nice if there were some other way for the X plugin to "register" its preferences panels somehow, so that the PrefsEditor construction process would find them and add them, without directly knowing anything about them.