Gwibber

Differences between revisions 1 and 4 (spanning 3 versions)
⇤ ← Revision 1 as of 2012-04-27 20:31:50 →
Size: 1048
Editor: ken-vandine
Comment:
← Revision 4 as of 2012-05-11 00:37:22 → ⇥
Size: 1165
Editor: ken-vandine
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
Discussion of plans for improvements to Gwibber in 12.10 and beyond. Discussion of plans for improvements to the Gwibber service in 12.10
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  * python3
  * Barry already ported mx.DateTime and looks like there shouldn't be any blockers to porting

Summary

Discussion of plans for improvements to the Gwibber service in 12.10

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


 CategorySpec 
 






        
 
            

DesktopTeam/Specs/Quantal/Gwibber  (last edited 2012-05-14 13:58:59 by ken-vandine)