emesene/emesene — Issue #989: Extension updates TODO
Author: Sbte
Created: 2012-01-25 18:34:26+00:00
State: open

Just keeping a list of ideas here. Anyone who wants to work on this can do so. I won't have time in the next few weeks I think.

- Make the Collections single instance. This can be done using extensions for the Collections. This probably means that we need separate classes for community and supported themes/plugins.
- Don't download directly to the themes/plugins folders. This might cause breakage when emesene is aborted while downloading. Just download to a temp dir, and then move to the right place. If the download is an updated, rather than replacing files, old content should be removed first using the remove method.
- Check for updates at startup. Only do this after the previous two have been implemented
- Implement a refresh button on the updates tab.