Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.
Organizer API: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (added delete template) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
{{Delete | reason=Outdated. Dead Links. Unsupported architectures.}} | |||
'''English''' [[Organizer_API_Spanish|Spanish]] | |||
[[Category:Developing with Qt::QtMobility]] | |||
== | == Qt Mobility 1.1 Features == | ||
== News == | |||
[http://labs.qt.nokia.com/2011/05/04/qt-4-7-3-and-qt-mobility-1-1-3-have-been-released/ Qt Mobility 1.1.3 Release] is available now for commercial app development and deployment on Ovi store. | |||
[http://labs.qt.nokia.com/2011/05/12/qt-mobility-1-2-0-released/ Qt Mobility 1.2.0 release] is available now. | |||
= | = Organizer API = | ||
== Summary == | |||
==Key features (planned)== | The Qt Organizer API lets you work with personal information data like appointments, birthdays, to-do lists, and journal entries. It's primarly aimed at time based data, rather than people (Qt Contacts API) or messages (Qt Messaging API). The data model is aimed to be compatible with iCalendar. | ||
== Key features (planned) == | |||
* Create, filter, update and delete time based data: | * Create, filter, update and delete time based data: | ||
| Line 22: | Line 27: | ||
* Supports iCalendar recurrence model | * Supports iCalendar recurrence model | ||
** Exceptions, complex rules etc (all the useless stuff that only unit tests use | ** Exceptions, complex rules etc (all the useless stuff that only unit tests use :) | ||
** (but currently not recurrence shorter than one day) | ** (but currently not recurrence shorter than one day) | ||
* Synchronous and asynchronous | * Synchronous and asynchronous APIs | ||
** Clear separation of the | ** Clear separation of the APIs, allows developers to build applications with responsive UIs | ||
* Multi platform support | * Multi platform support | ||
| Line 32: | Line 37: | ||
** MeeGo | ** MeeGo | ||
** Symbian (S60 3.1 to Symbian^3) | ** Symbian (S60 3.1 to Symbian^3) | ||
** | ** KDE kcal (extended) | ||
* Multiple calendar support | * Multiple calendar support | ||
| Line 38: | Line 43: | ||
* Flexible backend scheme | * Flexible backend scheme | ||
** Allows | ** Allows HTTP based backends as well as local device backends. | ||
* | * QML Support | ||
** Bindings to allow clients to access organizer functionality from | ** Bindings to allow clients to access organizer functionality from QML via QtDeclarative plugins | ||
** Build next-generation, fluidly animated user interfaces for time-context-aware social applications | ** Build next-generation, fluidly animated user interfaces for time-context-aware social applications | ||
Currently not all features are implemented on all platforms, and we expect that the | Currently not all features are implemented on all platforms, and we expect that the API will change in several areas before release, including: | ||
* Time zone support | * Time zone support | ||
* All day events | * All day events | ||
| Line 51: | Line 55: | ||
* Reminders | * Reminders | ||
==Key features== | == Key features == | ||
* Create/Filter/Update/Delete events, todos, journals and notes | * Create/Filter/Update/Delete events, todos, journals and notes | ||
* Third-party providers can write plugins which allow access to different calendar or schedule sources (device, device clouds, online clouds, etc) | * Third-party providers can write plugins which allow access to different calendar or schedule sources (device, device clouds, online clouds, etc) | ||
==Example applications!== | == Example applications! == | ||
There are two example applications at the moment: | There are two example applications at the moment: | ||
* [http://doc.qt.nokia.com/qtmobility-1.1.0-beta/calendardemo.html calendardemo] | |||
* timescape (QML) (development continuing) | |||
Both are simple demonstrations of slightly different features of the API. The timescape example uses QML, while the calendardemo example uses traditional Qt widgets. | |||
Both are simple demonstrations of slightly different features of the | |||
Latest revision as of 09:21, 16 June 2015
| 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. |
| This article is nominated for deletion. Reason: Outdated. Dead Links. Unsupported architectures. Please raise your support/opposition to this nomination in the article's discussion page. |
English Spanish
Qt Mobility 1.1 Features
News
Qt Mobility 1.1.3 Release is available now for commercial app development and deployment on Ovi store. Qt Mobility 1.2.0 release is available now.
Organizer API
Summary
The Qt Organizer API lets you work with personal information data like appointments, birthdays, to-do lists, and journal entries. It's primarly aimed at time based data, rather than people (Qt Contacts API) or messages (Qt Messaging API). The data model is aimed to be compatible with iCalendar.
Key features (planned)
- Create, filter, update and delete time based data:
- Events (appointments, parties, deadlines etc)
- Journal entries (associated with (Gregorian) dates)
- To-do tasks
- Also supports notes (little scraps of text you might stick to something in real life)
- Supports iCalendar recurrence model
- Exceptions, complex rules etc (all the useless stuff that only unit tests use :)
- (but currently not recurrence shorter than one day)
- Synchronous and asynchronous APIs
- Clear separation of the APIs, allows developers to build applications with responsive UIs
- Multi platform support
- Maemo 5
- MeeGo
- Symbian (S60 3.1 to Symbian^3)
- KDE kcal (extended)
- Multiple calendar support
- Different users, or different collections of events
- Flexible backend scheme
- Allows HTTP based backends as well as local device backends.
- QML Support
- Bindings to allow clients to access organizer functionality from QML via QtDeclarative plugins
- Build next-generation, fluidly animated user interfaces for time-context-aware social applications
Currently not all features are implemented on all platforms, and we expect that the API will change in several areas before release, including:
- Time zone support
- All day events
- Multiple calendar support
- Reminders
Key features
- Create/Filter/Update/Delete events, todos, journals and notes
- Third-party providers can write plugins which allow access to different calendar or schedule sources (device, device clouds, online clouds, etc)
Example applications!
There are two example applications at the moment:
- calendardemo
- timescape (QML) (development continuing)
Both are simple demonstrations of slightly different features of the API. The timescape example uses QML, while the calendardemo example uses traditional Qt widgets.