Organizer API: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 1: Line 1:
'''English''' [[Organizer API Spanish|Spanish]]
'''English''' [[Organizer_API_Spanish|Spanish]]<br />[[Category:Developing with Qt::QtMobility]]


==Qt Mobility 1.1 Features==
== Qt Mobility 1.1 Features ==


==News==
== 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] ''[labs.qt.nokia.com]'' is available now for commercial app development and deployment on Ovi store.<br />[http://labs.qt.nokia.com/2011/05/12/qt-mobility-1-2-0-released/ Qt Mobility 1.2.0 release] ''[labs.qt.nokia.com]'' is available now.
&quot;Qt Mobility 1.1.3 Release&amp;quot;:http://labs.qt.nokia.com/2011/05/04/qt-4-7-3-and-qt-mobility-1-1-3-have-been-released/ is available now for commercial app development and deployment on Ovi store.<br />&quot;Qt Mobility 1.2.0 release&amp;quot;:http://labs.qt.nokia.com/2011/05/12/qt-mobility-1-2-0-released/ is available now.


=Organizer <span class="caps">API</span>=
= Organizer API =


==Summary==
== Summary ==


The Qt Organizer <span class="caps">API</span> 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 <span class="caps">API</span>) or messages (Qt Messaging <span class="caps">API</span>). The data model is aimed to be compatible with iCalendar.
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)==
== Key features (planned) ==


* Create, filter, update and delete time based data:
* Create, filter, update and delete time based data:
Line 22: Line 22:


* Supports iCalendar recurrence model
* Supports iCalendar recurrence model
** Exceptions, complex rules etc (all the useless stuff that only unit tests use <span class="smiley">:)</span>
** 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 <span class="caps">API</span>s
* Synchronous and asynchronous APIs
** Clear separation of the <span class="caps">API</span>s, allows developers to build applications with responsive UIs
** Clear separation of the APIs, allows developers to build applications with responsive UIs


* Multi platform support
* Multi platform support
Line 32: Line 32:
** MeeGo
** MeeGo
** Symbian (S60 3.1 to Symbian^3)
** Symbian (S60 3.1 to Symbian^3)
** <span class="caps">KDE</span> kcal (extended)
** KDE kcal (extended)


* Multiple calendar support
* Multiple calendar support
Line 38: Line 38:


* Flexible backend scheme
* Flexible backend scheme
** Allows <span class="caps">HTTP</span> based backends as well as local device backends.
** Allows HTTP based backends as well as local device backends.


* <span class="caps">QML</span> Support
* QML Support
** Bindings to allow clients to access organizer functionality from <span class="caps">QML</span> via QtDeclarative plugins
** 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 <span class="caps">API</span> will change in several areas before release, including:
Currently not all features are implemented on all platforms, and we expect that the API will change in several areas before release, including:<br />* Time zone support<br />* All day events<br />* Multiple calendar support<br />* Reminders


* Time zone support
== Key features ==
* All day events
* Multiple calendar support
* Reminders
 
==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:
 
* [http://doc.qt.nokia.com/qtmobility-1.1.0-beta/calendardemo.html calendardemo] ''[doc.qt.nokia.com]''
* timescape (<span class="caps">QML</span>) (development continuing)
 
Both are simple demonstrations of slightly different features of the <span class="caps">API</span>. The timescape example uses <span class="caps">QML</span>, while the calendardemo example uses traditional Qt widgets.


===Categories:===
There are two example applications at the moment:<br />* &quot;calendardemo&amp;quot;:http://doc.qt.nokia.com/qtmobility-1.1.0-beta/calendardemo.html<br />* timescape (QML) (development continuing)


* [[:Category:Developing with Qt|Developing_with_Qt]]
Both are simple demonstrations of slightly different features of the API. The timescape example uses QML, while the calendardemo example uses traditional Qt widgets.
** [[:Category:Developing with Qt::QtMobility|QtMobility]]

Revision as of 10:07, 24 February 2015

English Spanish

Qt Mobility 1.1 Features

News

"Qt Mobility 1.1.3 Release&quot;:http://labs.qt.nokia.com/2011/05/04/qt-4-7-3-and-qt-mobility-1-1-3-have-been-released/ is available now for commercial app development and deployment on Ovi store.
"Qt Mobility 1.2.0 release&quot;:http://labs.qt.nokia.com/2011/05/12/qt-mobility-1-2-0-released/ 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&quot;:http://doc.qt.nokia.com/qtmobility-1.1.0-beta/calendardemo.html
* 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.