Details
-
Epic
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
None
-
None
-
QtPIM backlog
Description
This issue is a metabug to track work required to bring the QtPim-related modules (Contacts, Organizer, Versit) up to "release-level" quality.
Currently identified tasks include:
1) API Review
- some issues have already been identified:
- QContactRelationship now requiring full QContact instances for first() / second() which either requires additional, costly database reads on behalf of the backend, or kludges (QContact first; first.setId(firstId); QContact second; second.setId(secondId); relationship.setFirst(first); relationship.setSecond(second)
- Relationship types returned via accessor functions instead of const strings.
- QContactOnlineAccount's protocol is an enum. Given how many varied types of accounts there can be and how quickly services come and go, this is not extensible enough.
2) Documentation Review and Generation
- The documentation needs to be reviewed to ensure it reaches required quality
3) Backend evaluation
- various backends need to be considered for inclusion or exclusion based on their quality and applicability (eg, remove old backend code for unsupported platforms, possibly add generic sqlite-based backends if applicable).
Stakeholders:
Alex Blasche (Digia), Chris Adams (Qinetic), Robin Burchell (Jolla)