Qt-contributors-summit-2013-QtDBus CS: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (Categorize) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
[[Category:QtCS2013]] | |||
=QtDBus module discussions at Qt Contributor Summit 2013= | =QtDBus module discussions at Qt Contributor Summit 2013= | ||
| Line 11: | Line 13: | ||
Discussion: | Discussion: | ||
# Take ahartmetz’s marshaller/demarshaller and put on top of QtDBus & | # Take ahartmetz’s marshaller/demarshaller and put on top of QtDBus & libdbus-1 | ||
# Moving the handling to a thread | # Moving the handling to a thread | ||
# Handling our own socket | # Handling our own socket | ||
| Line 19: | Line 21: | ||
* Generator in QtDBus generates synchronous property get and set | * Generator in QtDBus generates synchronous property get and set | ||
** QtDBus should discourage sync calls more | ** QtDBus should discourage sync calls more | ||
** For properties, we could add new <span class="caps">API</span> that is async (returns QDBusPendingReply | ** For properties, we could add new <span class="caps">API</span> that is async (returns QDBusPendingReply<void> and QDBusPendingReply<QDBusVariant>) | ||
* There is no error-checking in qdbus_cast (from variants) | * There is no error-checking in qdbus_cast (from variants) | ||
** No way to distinguish a T() returned from qdbus_cast | ** No way to distinguish a T() returned from qdbus_cast<T>() as empty or as error | ||
* Parse documentation annotations and generate documentation in the Interface and Adaptors? | * Parse documentation annotations and generate documentation in the Interface and Adaptors? | ||
* Investigate the type system used by Telepathy | * Investigate the type system used by Telepathy | ||
Latest revision as of 17:31, 6 January 2017
| This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean. |
QtDBus module discussions at Qt Contributor Summit 2013
Topics for discussion:
- Rewriting the engine:
- Dropping the libdbus-1 dependency
- Moving the connection handling to a dedicated thread
- Adding support for kdbus
- kdbus overview
Discussion:
- Take ahartmetz’s marshaller/demarshaller and put on top of QtDBus & libdbus-1
- Moving the handling to a thread
- Handling our own socket
- Remember the specifics about sockets on Windows
- Adding kdbus compatibility
- Generator in QtDBus generates synchronous property get and set
- QtDBus should discourage sync calls more
- For properties, we could add new API that is async (returns QDBusPendingReply<void> and QDBusPendingReply<QDBusVariant>)
- There is no error-checking in qdbus_cast (from variants)
- No way to distinguish a T() returned from qdbus_cast<T>() as empty or as error
- Parse documentation annotations and generate documentation in the Interface and Adaptors?
- Investigate the type system used by Telepathy
- Update documentation about supporting multiple platforms (specifically, Windows)
- Right now, it says it’s Unix-only
- Would be nice to have better tutorials too