New Qt APIs for Mobile Development: Mobility I
summary
Overview of the new Qt Mobility pieces and where they actually change app code: a metadata store plus an IPC layer exposes services via QServiceManager so clients get a QObject proxy whose metaobject is serialized over debus, local sockets or Symbian IPC; services can be plug-ins or cross‑process with global vs private instantiation, and only first‑level QObjects and value types travel over IPC. QML support lands in 1.1 via QML wrappers mirroring managers and asynchronous request/reply patterns like QNetworkAccessManager.
AI-written summary · about
chapters (9)
- 0:00Introduction to Qt Mobility
- 1:32About Qt Mobility APIs
- 4:29Mobility API categories
- 7:39Service framework overview
- 21:27Service framework demo
- 32:19Data-driven APIs introduction
- 37:24Context API deep dive
- 42:07QML and Mobility integration
- 53:05Q&A session
related talks
18mAPI Design and QML
32mNetwork programmability and telecommunication APIs
15mLightning Talk: Designing an Intent-based API
19mVersioning strategy for a complex internal API
17mHybrid Integration Platform and API Management
16mDesigning API for Mobile Apps
52mMessenger Inside Out, or How to Build a Messenger in an iOS Mobile App Today
19mUnlocking New API Opportunities: PaaS to RPC Migration