Changes

m
no edit summary
Line 97: Line 97:  
* http://wiki.laptop.org/go/API_reference?
 
* http://wiki.laptop.org/go/API_reference?
 
* Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.
 
* Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.
* Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collabration].
+
* Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].
    
:* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the "manual". One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]
 
:* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the "manual". One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]