Please create a documentation package for the U1db QML module

Bug #1195275 reported by David Planella
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
U1DB Qt/ QML
Invalid
Undecided
Unassigned
Ubuntu UI Toolkit
Invalid
Undecided
Unassigned

Bug Description

In order for app developers to be able to use the U1db API, we need good documentation.

Ideally, we'd have well documented examples, classes and its members, but the very first step is to get documentation built at all.

In the same way we do with the ubuntu-ui-toolkit, we need a -doc package for the accounts QML module, which builds and ships the HTML documentation generated from qdoc. Once we've got that, I can get that documentation to be automatically published on developer.ubuntu.com from the -doc package.

Alternatively, if the U1 bindings are considered part of the SDK, the U1db documentation could also be shipped in the ubuntu-ui-toolkit-doc package.

The ubuntu-ui-toolkit-doc package and ubuntu-ui-toolkit branch (see the documentation folder) are a good example about creating the HTML with developer.ubuntu.com CSS styling.

Thanks!

Revision history for this message
Cris Dywan (kalikiana) wrote :
Revision history for this message
David Planella (dpm) wrote :

Yep, we built those docs manually back then, but now I know there is a package, so I'll use that for the doc publisher and mark the bug as invalid. Thanks!

Changed in u1db-qt:
status: New → Invalid
Changed in ubuntu-ui-toolkit:
status: New → Invalid
Revision history for this message
Cris Dywan (kalikiana) wrote :

Looks like packages are again silently broken:
https://launchpad.net/~ubuntu-sdk-team/+archive/ppa/+packages

Revision history for this message
Cris Dywan (kalikiana) wrote :
Revision history for this message
Kevin Wright (kevin-wright-1) wrote :

"if the U1 bindings are considered part of the SDK, the U1db documentation could also be shipped in the ubuntu-ui-toolkit-doc package."

While still assuming U1db-Qt will be (or is) a contribution to the Ubuntu SDK, from an information architecture perspective, a database plugin/API's documentation should probably be treated independent of a user interface plugin's documentation.

They might be used together in applications, and live side by side together as plugins available to developers, but neither is a part of the other (and in this particular case neither one depends on the other as well).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.