| Summary: | Creating accounts could use a high level method for setting initial properties | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Thomas Richard <thomas9999> |
| Component: | tp-qt | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | enhancement | ||
| Priority: | low | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Thomas Richard
2011-01-15 08:00:12 UTC
Indeed, we did a lot of work to weed out the uses of bare QVariantMaps with "well-known" keys in tp-qt4 0.5, but it seems we missed one case, which has confused at least two people by now (and counting). The class should be similar to our other bare variant map wrappers, with friendly accessors for commonly used properties, but retaining bare map access to allow extensions. Additionally, it could use integration with the SupportedAccountProperties property described here: http://telepathy.freedesktop.org/spec/Account_Manager.html#Property:SupportedAccountProperties such that you'd have some methods for checking whether setting a particular property is supported, and perhaps warnings for attempts to set with no support. This requires the wrapper class to be linked up to an introspected AccountManager, though. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-qt/issues/19. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.