+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+/****************************************************************************

+**

+** Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies).

+** All rights reserved.

+** Contact: Nokia Corporation (qt-info@nokia.com)

+**

+** This file is part of the documentation of the Qt Toolkit.

+**

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+**

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+**

+** If you have questions regarding the use of this file, please contact

+** Nokia at qt-info@nokia.com.

+** $QT_END_LICENSE$

+**

+****************************************************************************/

+

+

+/*!

+

+\page camera.html

+

+\title Camera

+\brief An API to control camera devices.

+

+\ingroup mobility

+

+

+\note This API and documentation is a \bold {Technology Preview} and is still

+subject to change.

+

+

+The Camera API provides control of system camera devices. Providing support

+for still or video image capture with sound support.

+

+

+\tableofcontents

+

+

+\section1 Overview

+

+The Camera API allows high level control of various aspects of still images

+and video. Camera is a part of the Multimedia API and this relationship is

+apparent when you notice that certain core classes are subclassed from some

+Multimedia base classes including \l QMediaObject and \l QMediaControl.

+

+

+

+\section1 Still Images

+

+In order to capture an image we need to create a \l QCamera object and use

+it to initialize a \l QVideoWidget, so we can see where the camera is

+pointing - a viewfinder. The camera object is also used to initialize a new

+QStillImageCapture object, imageCapture. All that is then needed is to start

+the camera, lock it so that the settings are not changed while the image

+capture occurs, capture the image, and finally unlock the camera ready for

+the next photo.

+

+ \code

+ camera = new QCamera;

+ viewFinder = new QCameraViewfinder();

+ viewFinder->show();

+

+ camera->setViewfinder(viewFinder);

+

+ imageCapture = new QStillImageCapture(camera);

+

+ camera->start();

+

+ //on half pressed shutter button

+ camera->lock();

+

+ ...

+

+ //on shutter button pressed

+ imageCapture->capture("imagefile.jpg");

+

+ //on shutter button released

+ camera->unlock();

+ \endcode

+

+Alternatively, we could have used a QVideoWidget initialized with the camera

+object to create a view finder.

+

+

+

+\section1 Video Clips

+

+Previously we saw code that allowed the capture of a still image. Recording

+video requires the use of a \l QMediaRecorder object and a \l

+QAudioCaptureSource for sound.

+

+To record video we need to create a camera object as before but this time as

+well as creating a viewfinder, we will also initialize a media recorder object

+and an audio source object for sound configuration details.

+

+ \code

+ mediaRecorder = new QMediaRecorder(camera);

+ ...

+ audioSource = new QAudioCaptureSource(camera);

+ \endcode

+

+Signals from the \i mediaRecorder can be connected to slots to react to

+changes in the state of the recorder or error events. Recording itself

+starts with the \l {QMediaRecorder::record()}{record()} function of

+mediaRecorder being called, this causes the signal \l

+{QMediaRecorder::stateChanged()}{stateChanged()} to be emitted. The

+recording process can be changed with the \l {QMediaRecorder::record()}{record()},

+\l {QMediaRecorder::pause()}{pause()}, \l {QMediaRecorder::stop()}{stop()} and

+\l {QMediaRecorder::setMuted()}{setMuted()} slots in \l QMediaRecorder.

+

+When the camera is in video mode, as decided by the application, then as the

+shutter button is pressed the camera is locked as before but instead the

+\l {QMediaRecorder::record()}{record()} function in \l QMediaRecorder is used.

+

+

+

+\section1 Focus

+

+Focusing is managed by the classes \l QCameraFocus and \l QCameraFocusControl.

+QCameraFocus allows the developer to set the general policy by means of the

+enums for the \l {QCameraFocus::FocusMode}{FocusMode} and the

+\l {QCameraFocus::FocusPointMode}{FocusPointMode}. \l FocusMode deals with

+settings such as \l AutoFocus, \l ContinuousFocus and \l InfinityFocus, whereas

+\l FocusPointMode deals with the various focus zones within the view.

+\l FocusPointMode has support for face recognition, center focus and a custom

+focus where the focus point can be specified.

+

+

+

+\section1 Cancelling Asynchronous Operations

+

+Various operations such as image capture and auto focusing occur

+asynchrously. These operations can often be cancelled by the start of a new

+operation as long as this is supported by the backend. For image capture,

+the operation can be cancelled by calling

+\l {QStillImageCapture::cancelCapture()}{cancelCapture()}. For AutoFocus,

+autoexposure or white balance cancellation can be done by calling

+\i {QCamera::unlock(QCamera::LockFocus)}.

+

+

+

+\section1 Camera Controls

+

+ \table

+ \header

+ \o Control Name

+ \o Description

+ \row

+ \o camera

+ \o the interface for system camera devices

+ \row

+ \o burst control

+ \o capturing multiple images as fast as possible

+ \row

+ \o bracketing

+ \o Capture a number of images with different camera settings

+ \row

+ \o exposure

+ \o Includes: flash mode; flash power; metering mode; aperture; shutter speed, iso setting

+ \row

+ \o focus

+ \o Includes: optical zoom; digital zoom; focus point; focus zones

+ \row

+ \o image processing

+ \o white balance; contrast; saturation; sharpen; denoise

+ \row

+ \o locks

+ \o handles the locking and unlocking of camera devices

+ \row

+ \o viewfinder

+ \o used to set displayed items and resolution

+ \endtable

+

+

+\section1 Classes

+\annotatedlist camera

+

+

+*/

+

+

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+

+

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+/****************************************************************************

+**

+** Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies).

+** All rights reserved.

+** Contact: Nokia Corporation (qt-info@nokia.com)

+**

+** This file is part of the documentation of the Qt Toolkit.

+**

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+**

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+**

+** If you have questions regarding the use of this file, please contact

+** Nokia at qt-info@nokia.com.

+** $QT_END_LICENSE$

+**

+****************************************************************************/

+

+/*!

+ \group mobility

+ \title Qt Mobility Project APIs

+

+ Qt Mobility Project supplies a set of new APIs for Qt enabling a range of

+ mobile-centric technologies and features on mobile and non-mobile platforms.

+

+*/

+

+

+

+/*!

+ \page index.html

+ \startpage index.html Qt Reference Documentation

+

+ \title Qt Mobility Project APIs Overview

+

+ \brief An overview of the Qt Mobility Project APIs.

+

+ Qt Mobility Project delivers a set of new APIs to Qt with features

+ that are well known from the mobile device world, in particular phones.

+ However, these APIs allow the developer to use these features with ease

+ from one framework and apply them to phones, netbooks and non-mobile

+ personal computers. The framework not only improves many aspects of a

+ mobile experience, because it improves the use of these technologies,

+ but has applicability beyond the mobile device arena.

+

+ \tableofcontents

+

+

+

+ \section1 Overview

+

+ \section2 Introducing the New Qt APIs

+

+ Qt Mobility covers a wide range of features and technologies so it best

+ to regard it not as a single API but as a collection of APIs or frameworks.

+

+ This release contains the following APIs:

+

+ \annotatedlist mobility

+

+ These APIs give the developer a range of desirable functions for a

+ mobile platform, but now these functions become possible on platforms not

+ traditionally associated with some of the features. A mobile device

+ using the Qt Mobility Project API would be able to

+ \list

+ \o Locate services on-board or remotely. Find an optimal

+ connection to the network for the particular service.

+ \o Services built on top of these APIs would include Internet

+ applications such as email and web browsing.

+ \o Multimedia features enable image and video capture with audio ,

+ audio recording, and the playing of music or video clips.

+ \o Location will make the device aware of its geographical location

+ to support GIS applications.

+ \o Publish-Subscribe enables communication between separate objects

+ whether local or remote to the device.

+ \endlist

+

+ The New Qt APIs deliver to developers an enabling package. It

+ will be used by developers to build a variety of applications and

+ services that are mobile capable or familiar to mobile users,

+ irrespective of whether the platform is mobile or not. This means that

+ there is the possibility of easy transfer of user experience from PC to

+ phone or vice versa.

+

+ \section1 Namespace

+

+ The QtMobility APIs are placed into the \i{QtMobility} namespace, with

+ the important exception of Multimedia. This is done to facilitate the

+ future migration of Mobility APIs into Qt.

+

+ See the \l {Quickstart Example}{Quickstart guide} for an example on how

+ the namespace impacts on application development.

+

+ \section1 Getting Started

+ To get started with Qt Mobility see the

+ \list

+ \o \l {Installation Guide}

+ \o \l {Quickstart Example}

+ \o \l {Qt Mobility Examples}{List of all examples.}

+ \endlist

+

+ For users on the supported Symbian platforms, shown at the bottom of this

+ page, see the instructions at the

+ \l{http://library.forum.nokia.com/topic/Qt_for_Symbian_Developers_Library/GUID-7E53D0F7-72CB-41C4-8807-FE7A772B0DB4.html}{Qt For Symbian Developer's Library}

+

+ \section2 Known Issues

+ For a list of known issues and an additional details on feature supported see

+ \l {Release Notes of the QtMobility Project}.

+

+ For a overview of Platform Compatibility see \l {Platform Compatibility}.

+

+ \section1 The New Qt APIs

+ \section2 Bearer Management

+

+ Although not a network manager, this component manages the connectivity

+ state of the device to the network. So it does not manage network

+ configurations, which are the role of the platform provider, but it does

+ allow the user to start or stop network interfaces. Some higher level

+ management of the connection session may also be possible as well

+ depending on the platform.

+

+ Some platforms can have a set of grouped access points perhaps based on a

+ common purpose. Bearer Management allows comparison and prioritization

+ of the access and use of these points.

+

+ The aim of Bearer Management is to reduce the need for the developer to be

+ concerned about trying to locate the best connection from a list of

+ possible IP bearers and 3G connections. The user can select the best or

+ it can be selected transparently so that WLAN roaming can occur

+ seemlessly.

+

+ Some examples of the Bearer Management functionality,

+ \list

+ \o On demand use of the appropriate Access Point. When a user starts

+ to use a browser, the appropriate access point is selected from those

+ available and a connection is transparently made.

+ \o Always-on applications such as email or IM roam automatically

+ between cellular packet data and WLAN networks. The application developer

+ is in control and for example the application can gracefully close TCP

+ connections over the old bearer after setting up new TCP connections

+ over the new bearer.

+ \o Application developer can create a settings user interface, where

+ the user can select a certain connection to be used with the application

+ \o A connection manager application can be implemented with Qt. This

+ application enumerates available connections, shows counters, and allows

+ the user to connect or disconnect

+ \endlist

+

+ For more details, see the \l {Bearer management} {Bearer Management API overview}.

+

+ \section2 Contacts

+

+ The structure and retrieval of contact data from local or remote backends.

+ It includes the ability to create, edit, list, delete and lookup contact

+ information whether it is stored locally or remotely.

+

+ For more details, see the \l {Contacts} {Contacts API overview}.

+

+ \section2 Publish and Subscribe

+

+ Will enable context sensitive access to information in future releases.

+ Data is organized as a tree, with data being able to 'shadow' other

+ data with the 'same key', a string specifying the leaf or node. The

+ context is an example of a context ontology, a defined set of

+ relationships. As the context changes the values of the objects change

+ but the relationships remain the same. It is intended to be an enabling

+ technology, the basis of a range future applications.

+

+ At this stage the API is intended to act as a common communications

+ method between applications, whether local or remote.

+

+ For more details, see the \l {Publish and Subscribe} {Publish and Subscribe API overview}.

+

+ \section2 Location

+

+ The C++ API is one layer of this feature. This API provides an easy to

+ use interface that encapsulates basic geographical information obtained

+ from satellite or other sources about the user, including latitude and

+ longitude, bearing, speed and altitude. It will enable a range of

+ geographical applications, for example, maps.

+

+ For more details, see the \l {Location} {Location API overview}.

+

+ \section2 Messaging

+

+ A common interface for handling SMS, MMS, MIME Email and TNEF Email

+ messages. Enables access to messaging services to search and sort

+ messages, notify of changes to messages stored, send messages

+ with or without attachments, retrieve message data, and launch the

+ preferred messaging client to either display an existing message,

+ or compose a message.

+

+ For more details see the \l {Messaging} {Messaging API overview}.

+

+ \section2 Multimedia

+

+ An API to play audio and video of various formats. Record audio. The playing

+ and managing of an FM radio. This includes the typical functionality you

+ would find on a music and video player, combined with an FM radio.

+

+ For more details see the \l {Multimedia} {Multimedia API overview}.

+

+ \section2 Sensors

+

+ An API for accessing hardware sensors. This covers both high-level

+ sensors such as screen orientation (portrait, landscape) and low-level,

+ real-time sensors such as accelerometer data.

+

+ For more details see the \l{Sensors API}{Sensors API overview}.

+

+ \section2 Service Framework

+

+ A platform independent method of finding Services. A 'service' is an

+ independent component that allows a client to perform a well-defined

+ operation.

+

+ The services are implemented as plugins installed on the device and can

+ look for supporting external services running on a central server. E.g.

+ weather, local tourist attractions etc. Default applications can use

+ the layer to locate servers.

+

+ Since this is an abstraction layer then the app does not need to be

+ concerned with the underlying protocol, where the servers are, the

+ hardware peculiarities with networking and other low level details.

+

+ For more details see the \l {Qt Service Framework} {Service Framework API overview}.

+

+ \section2 System Information

+

+ An API to discover system related information and capabilities. Information

+ available will cover software version numbers, hardware features,

+ network connection types and status, display, data storage devices,

+ device information and the screensaver.

+

+ For more details see the \l {System Information} {System Information API overview}.

+

+ \section2 Versit

+

+ An API to manage Versit \reg documents, such as vCards.

+

+ For more details see the \l{Versit API}{Versit API overview}.

+

+ \section1 The QtMobility Namespace

+

+ The QtMobility APIs are placed into the QtMobility namespace. This is

+ done to facilitate the future migration of Mobility APIs into Qt. See

+ the \l {Quickstart Example}{Quickstart guide} for an example on how

+ the namespace impacts on application development.

+

+

+ \section1 Platform Compatibility

+

+

+ \raw HTML

+

+ <table cellpadding="2" cellspacing="1" border="0">

+ <tbody>

+ <tr>

+ <td>Color</td>

+ <td>Explanation</td>

+

+ </tr>

+ </tr>

+ <tr>

+ <td bgcolor="green"></td>

+ <td>A functional backend for the API on the platform is complete.</td>

+ </tr>

+ <tr>

+ <td bgcolor="yellow"></td>

+ <td>A functional backend for the API on the platform is being worked however it is not functionally complete.</td>

+

+ </tr>

+ <tr>

+ <tr>

+ <td bgcolor="lightgray"></td>

+ <td>A functional backend for the API on the platform is being worked on. At this point it is far from functionally complete or there is no platform specific code inside QDF source code.</td>

+ </tr>

+ <tr>

+ <td bgcolor="gray"></td>

+ <td>A functional backend for the API on the platform is not being worked on. It is possible for others to implement and integrate support.</td>

+ </tr>

+ </tbody>

+ </table>

+ <br>

+

+ <b>Tier 1 Platforms</b><br>

+ Primary platforms are the main focus of Mobility API. There platforms are frequently tested by our unit test suite and other internal testing tools. However, the timeline of availability for each backend is subject to change.

+ <br>

+ <b>Tier 2 Platforms</b><br>

+ Secondary platforms include future direction of Qt Mobility API. Contributions to these platforms are welcome.

+ <br>

+ <br>

+ <table align="center" cellpadding="2" cellspacing="1" border="1">

+ <tbody>

+ <tr>

+ <td rowspan="2">&nbsp;</td>

+ <td rowspan="2"><b>API Maturity Level</b></td>

+ <td colspan="7" align="center" bgcolor="#96E066"><b>Tier 1 Platforms</b></td>

+ <td colspan="4" align="center" bgcolor="#96E066"><b>Tier 2 Platforms</b></td>

+ </tr>

+ <tr>

+ <td width="9%"><b>S60 3rd Edition, Feature Pack 1</b></td>

+ <td width="9%"><b>S60 3rd Edition, Feature Pack 2</b></td>

+ <td width="9%"><b>S60 5th Edition</b></td>

+ <td width="9%"><b>Symbian^3</b></td>

+ <td width="9%"><b>Maemo 5</b></td>

+ <td width="9%"><b>Windows CE/Mobile<b></b></b></td>

+ <td width="9%"><b>Windows XP/Vista</b></td>

+ <td width="9%"><b>Linux</b></td>

+ <td width="9%"><b>Mac OS X</b></td>

+ </tr>

+ <tr>

+ <td>Service Framework (in-process)</td>

+ <td>FINAL</td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ </tr>

+ <tr>

+ <td>Messaging</td>

+ <td>FINAL</td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="gray"></td>

+ </tr>

+ <tr>

+ <td>Bearer Management</td>

+ <td>FINAL</td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ </tr>

+ <tr>

+ <td>Publish and Subscribe</td>

+ <td>FINAL</td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ </tr>

+ <tr>

+ <td>Contacts</td>

+ <td>FINAL</td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ </tr>

+ <tr>

+ <td>Location</td>

+ <td>FINAL</td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ </tr>

+ <tr>

+ <td>Multimedia</td>

+ <td>FINAL</td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ </tr>

+ <tr>

+ <td>System Information</td>

+ <td>FINAL</td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ </tr>

+ <tr>

+ <td>Sensors</td>

+ <td>FINAL</td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ </tr>

+ <tr>

+ <td>Versit(vCard)</td>

+ <td>FINAL</td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ </tr>

+ <tr>

+ <td>Versit(iCal)</td>

+ <td>TP</td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ <td bgcolor="green"></td>

+ </tr>

+ <tr>

+ <td>Camera</td>

+ <td>TP</td>

+ <td bgcolor="lightgray"></td>

+ <td bgcolor="lightgray"></td>

+ <td bgcolor="lightgray"></td>

+ <td bgcolor="lightgray"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ </tr>

+ <tr>

+ <td>Service Framework(OOP)</td>

+ <td>TP</td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ </tr>

+ <tr>

+ <td>Organizer</td>

+ <td>TP</td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ </tr>

+ <tr>

+ <td>Landmarks</td>

+ <td>TP</td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="gray"></td>

+ </tr>

+ <tr>

+ <td>Document Gallery</td>

+ <td>TP</td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ </tr>

+ <tr>

+ <td>Maps/Navigation</td>

+ <td>TP</td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="yellow"></td>

+ </tr>

+ <tr>

+ <td>Vibra</td>

+ <td>TP</td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ </tr>

+ <tr>

+ <td>Telephony Events</td>

+ <td>TP</td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="yellow"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ <td bgcolor="gray"></td>

+ </tr>

+ <p></p>

+ <p></p>

+ </tbody>

+ </table>

+ <br>

+

+ \endraw

+

+ \raw HTML

+ <p>

+ \endraw

+

+ \section1 Feedback and bug reports

+ Email any inquiries and feedback about Qt Mobility to qt-mobility-feedback@trolltech.com

+

+ And please report any bugs you may find to \l {http://bugreports.qt.nokia.com}

+

+ \section1 Acknowledgements

+

+ The icheck tool uses the following third-party component:

+

+ \bold {Open Source front-end for C++ (MIT license)}, Roberto Raggi <roberto.raggi@gmail.com>, QTMOBILITY/tools/icheck/parser/src

+*/

+

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+ Additionally note that CE MAPI is available on Windows Mobile and

+ does not need to be installed separately.

+

+ For more detailed instructions on installation on Windows Mobile

+ see \l {Messaging Installation On Windows Mobile}

+ although System Information will compile without them, there will be reduced functionality. It also depends on QtGui, and

+ on libbluetooth development headers.

+

+ On Symbian, it depends on WLANManagementAPI. WLANManagementAPI plugin is available at \l http://wiki.forum.nokia.com/index.php/SDK_API_Plug-in

+ For 5th edition sdk plugins are installed with installer (all at once), but for FP1 and FP2 devices a WLANManagementAPI.zip is provided.

+

+ On Symbian, it depends on SIM Utils API SDK plugin available from Forum Nokia \l http://wiki.forum.nokia.com/index.php/File:SIMUtilsAPI_3x_50.zip

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+/****************************************************************************

+**

+** Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies).

+** All rights reserved.

+** Contact: Nokia Corporation (qt-info@nokia.com)

+**

+** This file is part of the Qt Mobility Components.

+**

+** $QT_BEGIN_LICENSE:LGPL$

+** No Commercial Usage

+** This file contains pre-release code and may not be distributed.

+** You may use this file in accordance with the terms and conditions

+** contained in the Technology Preview License Agreement accompanying

+** this package.

+**

+** GNU Lesser General Public License Usage

+** Alternatively, this file may be used under the terms of the GNU Lesser

+** General Public License version 2.1 as published by the Free Software

+** Foundation and appearing in the file LICENSE.LGPL included in the

+** packaging of this file. Please review the following information to

+** ensure the GNU Lesser General Public License version 2.1 requirements

+** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.

+**

+** In addition, as a special exception, Nokia gives you certain additional

+** rights. These rights are described in the Nokia Qt LGPL Exception

+** version 1.1, included in the file LGPL_EXCEPTION.txt in this package.

+**

+** If you have questions regarding the use of this file, please contact

+** Nokia at qt-info@nokia.com.

+**

+**

+**

+**

+**

+**

+**

+**

+** $QT_END_LICENSE$

+**

+****************************************************************************/

+

+/*!

+\page messaging-installation-on-windows-mobile.html

+

+\title Messaging Installation On Windows Mobile

+\tableofcontents

+

+\section1 Get Qt Mobility and Qt packages

+

+Get the Qt Mobility Package from \l {http://get.qt.nokia.com}

+

+Get Qt 4.5.2 (or newer) Embedded for Windows Mobile package \l {http://get.qt.nokia.com/qt/source/qt-embedded-wince-opensource-src-4.5.3.zip} {download here}.

+

+\section1 Install pre-requisites

+

+A perl interpreter such as \l {http://www.activestate.com/activeperl} {ActivePerl} must be installed and available in the environment path.

+

+Visual Studio 2009 or newer must be installed.

+

+Windows Mobile 6 Standard SDK (including ActiveSync) must be installed \l {http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=20686a1d-97a8-4f80-bc6a-ae010e085a6e} {download page}.

+

+\section1 Build Qt

+

+ Extract Qt 4.5.2 Embedded (or newer) into your Qt directory on windows. e.g. c:\\Qt\\4.5.2_winmobile6_standard

+

+ Open a Visual Studio cmd shell

+

+ Set your PATH to include the Qt binaries

+ \code

+ set PATH=c:\Qt\4.5.2_winmobile6_standard\bin;%PATH%

+ \endcode

+

+ Set the INCLUDE and LIB vars to point to your ActiveSync sources

+ \code

+ set INCLUDE=%INCLUDE%;C:\Program Files\Windows Mobile 6 SDK\Activesync\inc

+ set LIB=%LIB%;C:\Program Files\Windows Mobile 6 SDK\Activesync\Lib

+ \endcode

+

+ Configure Qt

+ \code

+ cd c:\Qt\4.5.2_winmobile6_standard

+ configure.exe -debug -platform win32-msvc2008 -xplatform wincewm60standard-msvc2008 -cetest -plugindir \qtplugins

+ \endcode

+

+ Run setcepaths to setup embedded compiler paths

+ \code

+ setcepaths wincewm60standard-msvc2008

+ \endcode

+

+ Use devtools/ibmake or nmake to build. If using ibmake, ensure devtools/shell is in your path and that you have ActivePerl installed on your windows machine

+ \code

+ ibmake

+ \endcode

+ or

+ \code

+ nmake

+ \endcode

+

+\section1 Build Mobility Messaging

+

+ Open a new Visual Studio cmd shell

+

+ Set the path to Qt

+ \code

+ set PATH=%PATH%;c:\Qt\4.5.2_winmobile6_standard\bin

+ \endcode

+

+ Set QMAKESPEC

+ \code

+ set QMAKESPEC=wincewm60standard-msvc2008

+ \endcode

+

+ Run setcepaths to set embedded compiler paths

+ \code

+ setcepaths wincewm60standard-msvc2008

+ \endcode

+

+ Run qmake and build

+ \code

+ cd <path-to-mobility-messaging-depot-or-source-package>

+ qmake mobility.pro

+ nmake

+ \endcode

+

+ Visual Studio is recommended to build the mobility project for windows mobile, although it is not necessary, it makes debugging and deployment easier.

+

+ \code

+ cd <path-to-mobility-messaging-depot>

+ qmake -tp vc QT_CONFIG+=release mobility.pro -recursive

+ \endcode

+

+ If using git edit your git configuration so it does not consider Visual Studio files

+

+ Edit <path-to-mobility-messaging-depot>/.git/info/exclude

+

+ Append the following

+ \code

+ *.sln

+ *.ncb

+ *.suo

+ *.user

+ \endcode

+

+

+ Open the generated *.sln file and compile.

+

+ If you get errors during the Visual Studio build regarding mainACRT, right click on the project, goto linker-advanced and Clear the Entry-Point value.

+

+\section1 Deploy

+

+ Before running a debug instance, ensure that the QtMessaging.dll is a deployment dependency for the examples and tests.

+

+ Right click properties on project e.g. serviceactions. Under deployment->addition files add:

+ \code

+ "QtMessaging.dll|$(TargetDir)|%CSIDL_PROGRAM_FILES%\serviceactions|0"

+ \endcode

+ Replacing "serviceactions" with the relevant project.

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+ \module QtMultimediaKit

+ \title QtMultimediaKit Module

+ \brief The QtMultimediaKit Module providees APIs to play and record media, and manage a collection of media content.

+

+*/

+

+

+/*!

+

+For the developer who wishes to extend the functionality of the Multimedia

+classes there are several classes of particular importance. The default

+classes are QMediaService, QMediaServiceProvider and QMediaControl.

+

+Basically, the idea is that to use the Multimedia API you would use these three classes or classes derived from them as follows

+

+ \list

+ \o \l QMediaServiceProvider is used by the top level client class to request a service. The top level class knowing what kind of service it needs.

+

+ \o \l QMediaService provides a service and when asked by the top level object, say a component, will return a QMediaControl object.

+

+ \o \l QMediaControl allows the control of the service using a known interface.

+ \endlist

+

+Consider a developer creating, for example, a media player class called MyPlayer. It may have special requirements beyond ordinary media players and so may need a custom service and a custom control. We can subclass \l QMediaServiceProvider to create out MyServiceProvider class. Also we will create a MyMediaService, and the MyMediaControl to manipulate the media service.

+

+The MyPlayer object calls MyServiceProvider::requestService() to get an instance of MyMediaService. Then the MyPlayer object calls this service object it has just received and calling \l {QMediaService::control()}{control()} it will receive the control object derived from QMediaControl. Now we have all the parts necessary for our media application. We have the service provider, the service it provides and the control used to manipulate the service. Since our MyPlayer object has instances of the service and its control then it would be possible for these to be used by associated classes that could do additional actions, perhaps with their own control since the parameter to control() is a c-type string, \i {const char *}, for the interface.

+

+

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+\section2 Bearer Management API

+\list

+ \o Fremantle: Segmentation fault on removing a connected network

+\endlist

+

+\section2 Bearer Management API

+\list

+ \o All platforms: QNetworkConfigurationManager is not thread-safe; using it from other than main-thread off the application will not work properly.

+ Applies to QtMobility::QtBearer (1.0), QtBearer in Qt4.7 onwards is thread-safe.

+\endlist

+

+\endlist

+

+\section2 Bearer Management API

+\list

+ \o Fremantle: Application fail to acquire satellite signal

+ \o Fremantle: Audiorecorder fails to create file

+ \o Fremantle: Slideshow fails to display images

+ \o S60, Fremantle: Full screen video not handled correctly

+ \o S60: Signal strength is not implemented

+ ../../src/telephony \

+ ../../src/camera \

+ ../../src/telephony \

+ ../../src/camera \

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+ interpreted as permissions/capabilities. The list elements are

+ comma-separated and spaces after commas are not permitted.

+ This list can be empty.

+ filter.setInterface("com.nokia.qt.ILocation");

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.

+/****************************************************************************

+**

+** Copyright (C) 2009 Nokia Corporation and/or its subsidiary(-ies).

+** All rights reserved.

+** Contact: Nokia Corporation (qt-info@nokia.com)

+**

+** This file is part of the Qt Mobility Components.

+**

+** $QT_BEGIN_LICENSE:LGPL$

+** No Commercial Usage

+** This file contains pre-release code and may not be distributed.

+** You may use this file in accordance with the terms and conditions

+** contained in the Technology Preview License Agreement accompanying

+** this package.

+**

+** GNU Lesser General Public License Usage

+** Alternatively, this file may be used under the terms of the GNU Lesser

+** General Public License version 2.1 as published by the Free Software

+** Foundation and appearing in the file LICENSE.LGPL included in the

+** packaging of this file. Please review the following information to

+** ensure the GNU Lesser General Public License version 2.1 requirements

+** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.

+**

+** In addition, as a special exception, Nokia gives you certain additional

+** rights. These rights are described in the Nokia Qt LGPL Exception

+** version 1.1, included in the file LGPL_EXCEPTION.txt in this package.

+**

+** If you have questions regarding the use of this file, please contact

+** Nokia at qt-info@nokia.com.

+**

+**

+**

+**

+**

+**

+**

+**

+** $QT_END_LICENSE$

+**

+****************************************************************************/

+

+/*!

+\page telephony.html

+\ingroup mobility

+

+\title Telephony API

+

+\brief The Telephony API enables access to the telephony event services.

+

+The Qt Telephony API enables access to the telephony event services to

+provide telephony call notification that other applications can use to

+be notified.

+Using this API you can further get information abaout the status of all

+existing calls.

+

+\tableofcontents

+

+

+\section1 Overview

+

+The telephony library provides a set of function for accessing existing calls

+and their information like.

+Using this API you are able to queries the current telephony state. e.g. no call, ringing,

+call in-progress and call on-hold.

+Signals are provided to inform other application of changes of a call status. e.g. ringing,

+on-hold, terminating or of a change of the list of the current existing calls. e.g. call is ending.

+The Application can query call information using this API. e.g. call type, phone number, SIP id, link to the caller contact.

+

+\section1 Reference documentation

+

+\section2 Main classes

+

+\annotatedlist telephony

+

+\section1 Information and Events of Calls

+

+The library provides a number of classes and signals and properties to assist with the access of the calls in a mobile system.

+

+Another application can use this library to get informed about incomming calls, accessing calls information and more of the current system.

+Basically the library provides an easy access of call information of different OS system (here it is Linux and the DBus system).

+

+** This file is part of the documentation of the Qt Toolkit.

+** $QT_BEGIN_LICENSE:FDL$

+** Commercial Usage

+** Licensees holding valid Qt Commercial licenses may use this file in

+** accordance with the Qt Commercial License Agreement provided with the

+** Software or, alternatively, in accordance with the terms contained in a

+** written agreement between you and Nokia.

+** GNU Free Documentation License

+** Alternatively, this file may be used under the terms of the GNU Free

+** Documentation License version 1.3 as published by the Free Software

+** Foundation and appearing in the file included in the packaging of this

+** file.