Wishlist: Generic plugin type
Bug #1328768 reported by
Aaron Wells
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
High
|
Aaron Wells |
Bug Description
It would be useful to have a generic plugin type that provides all the benefits of every plugin type (i.e. lang strings, templates, cron jobs, config screens, config table, etc), while not having any specific functionality tied to it. This would be useful for:
1. Encouraging encapsulation of core code, especially for components that are mostly standalone, like the new "chat" functionality.
2. Third-party distributed code that doesn't match any of the existing plugin types. (Although really, we should just have a "local" plugin type for these.)
tags: | added: nominatedfeature |
Changed in mahara: | |
status: | In Progress → Fix Committed |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
We were discussing this on the IRC channel. I've decided to call the new plugintype "module", because the plugintype shows up in the URL so we need it to be something nice and generic. Here's a discussion from Simon that summarizes the results of our discussion:
<simoncoggins> so the summary is:
<simoncoggins> 1. Some bits of core code can be isolated into a plugin
<simoncoggins> 2. This is generally a good idea to keep related code together
<simoncoggins> 3. Not all plugins fit within the existing types
<simoncoggins> 4. Therefore it would be good to have a generic plugin type
<simoncoggins> 5. It would be good if it was specific to the distribution to avoid clashing with 3rd party modules
<simoncoggins> 6. The name will be in the url therefore should be generic/not too messy
<simoncoggins> 7. Therefore module/ for core code, and possibly local/ for 3rd party stuff