canmove, Confirmed users
1,570
edits
Extension Manager:Future Work: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 39: | Line 39: | ||
<td>'''Unified error logging''' | <td>'''Unified error logging''' | ||
Extension authors have to look all over the place for errors relating to installation, component registration, overlays and templating. These could all be brought together into one place. | Extension authors have to look all over the place for errors relating to installation, component registration, overlays and templating. These could all be brought together into one place. | ||
<td>P2 | |||
<td>S | |||
<td> | |||
<td> | |||
<tr> | |||
<td>'''Blocklist plugins by file version''' | |||
We currently rely on plugin vendors including the plugin version in one of the name, filename or description of the plugin. On windows the dll also contains a version number that many vendors use, we should start reading this and make the blocklist able to match on it. | |||
<td>P2 | <td>P2 | ||
<td>S | <td>S | ||
| Line 62: | Line 69: | ||
<td>P3 | <td>P3 | ||
<td>M | <td>M | ||
<td> | |||
<td> | |||
<tr> | |||
<td>'''Sandboxing extension code''' | |||
It would be nice to be able to sandbox certain extensions so they don't have certain privileges like writing to the local disk. | |||
<td>P3 | |||
<td>? | |||
<td> | |||
<td> | |||
<tr> | |||
<td>'''Multiple compatibility ranges per application''' | |||
It is currently impossible to distribute a single add-on that is compatible with two different min/max version ranges of one application. | |||
<td>P4 | |||
<td>S | |||
<td> | |||
<td> | |||
<tr> | |||
<td>'''Improve blocklist interaction with plugin host''' | |||
The blocklist has to rescan and check every plugin whenever a new plugin is detected at the moment. Instead the plugin host should just ask the blocklist if the new plugin is blocked or not in the same way the extension manager does | |||
<td>P4 | |||
<td>S | |||
<td> | <td> | ||
<td> | <td> | ||
| Line 67: | Line 95: | ||
<td>'''Better install/uninstall hooks''' | <td>'''Better install/uninstall hooks''' | ||
Fairly common request from add-on authors is to do things on install/uninstall. There are some existing hooks to handle this but they could be made easier to use. | Fairly common request from add-on authors is to do things on install/uninstall. There are some existing hooks to handle this but they could be made easier to use. | ||
<td>P4 | |||
<td>S | |||
<td> | |||
<td> | |||
<tr> | |||
<td>'''Replace install/update.rdf''' | |||
RDF is painful to read and write. While it is not great that authors could have to learn something new, so long as we continued to support the rdf forms switching to something new would make new author's lives easier. Either a simple xml schema or json are likely candidates. | |||
<td>P4 | <td>P4 | ||
<td>S | <td>S | ||