Gwibber
Differences between revisions 2 and 3
1060
Comment:
|
1165
|
Deletions are marked like this. | Additions are marked like this. |
Line 16: | Line 16: |
* Stop caching in the DB completely and rely on the DeeResourceManager for cached models? | |
Line 17: | Line 18: |
* Stop caching in the DB completely and rely on the DeeResourceManager for cached models? | |
Line 21: | Line 21: |
* use libpeas for plugins? | |
Line 22: | Line 23: |
* Handling failures | |
Line 24: | Line 24: |
* Barry already ported mx.DateTime and looks like there shouldn't be any blockers to porting |
Contents |
Launchpad Entry: desktop-q-gwibber
Created: 2012-04-27
Contributors: ken-vandine
Packages affected: gwibber
Summary
Discussion of plans for improvements to Gwibber in 12.10 and beyond.
Discussion Topics
- gwibber-service refactoring
- Testability
Stop caching in the DB completely and rely on the DeeResourceManager for cached models?
- DB schema changes to leverage the advantages of a relational DB instead of just storing json strings?
- Service Plugin changes
- Make plugins standalone processes?
- Provide superclass for all plugins to inherit from, useful for either current model or split processes?
- use libpeas for plugins?
- Split the plugins into separate sources and have individual maintainers for each?
- python3
Barry already ported mx.DateTime and looks like there shouldn't be any blockers to porting
Notes from UDS
Comments
DesktopTeam/Specs/Quantal/Gwibber (last edited 2012-05-14 13:58:59 by ken-vandine)