Feedback API: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 1: Line 1:
'''English''' [[Feedback API Spanish|Spanish]]
'''English''' [[Feedback_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.


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


==Summary==
== Summary ==


The Feedback <span class="caps">API</span> is a new <span class="caps">API</span> designed to help applications respond to user interaction and give feedback. That can be haptics or audio feedback.
The Feedback API is a new API designed to help applications respond to user interaction and give feedback. That can be haptics or audio feedback.


==Key features==
== Key features ==


The feedback <span class="caps">API</span> provides three kinds of feedback,
The feedback API provides three kinds of feedback,


* Theme-based feedback:<br /> You can decide on the reaction of your application by asking the system to execute a feedback that is theme specific. So for instance if you have a UI component that should be used as a button, you can make that happen.
* Theme-based feedback:<br />You can decide on the reaction of your application by asking the system to execute a feedback that is theme specific. So for instance if you have a UI component that should be used as a button, you can make that happen.


* Custom haptics:<br /> You can start a specific haptics feedback. You get to specify the duration, intensity, period, … That is useful if you need to be in complete control of the feedback that you want, for example in games. The system will play this feedback on an actuator. You can query the available actuators and their properties (name, state…) through the QFeedbackActuator class.
* Custom haptics:<br />You can start a specific haptics feedback. You get to specify the duration, intensity, period, … That is useful if you need to be in complete control of the feedback that you want, for example in games. The system will play this feedback on an actuator. You can query the available actuators and their properties (name, state…) through the QFeedbackActuator class.


* File support:<br /> For some technologies, you can get the feedback stored in a file. That can be a haptics feedback with all it parameters, a wave file… So there is support for loading those files and play them.<br /> There is currently the support for Immersion <span class="caps">IVT</span> files (for platforms that support it) and a Phonon backend to play sound.
* File support:<br />For some technologies, you can get the feedback stored in a file. That can be a haptics feedback with all it parameters, a wave file… So there is support for loading those files and play them.<br />There is currently the support for Immersion IVT files (for platforms that support it) and a Phonon backend to play sound.


===Back-ends===
=== Back-ends ===


Each kind of feedback is implemented by means of a plug-in back-end architecture. We currently have support for the MeeGo (through the MeeGo Touch <span class="caps">API</span>) and Symbian^3 platforms. Support is as follows,
Each kind of feedback is implemented by means of a plug-in back-end architecture. We currently have support for the MeeGo (through the MeeGo Touch API) and Symbian^3 platforms. Support is as follows,


{| class="infotable line"
{|
| '''Platform'''
|'''Platform'''
| '''Theme-based'''
|'''Theme-based'''
| '''Custom'''
|'''Custom'''
| '''File-based'''
|'''File-based'''
|-
|-
| '''MeeGo'''
|'''MeeGo'''
| Yes
|Yes
| Yes
|Yes
| Yes
|Yes
|-
|-
| '''Symbian^3'''
|'''Symbian^3'''
| Yes
|Yes
| Yes
|Yes
| No
|No
|}
|}


The back-end plug-ins’ source code is available in plugins/feedback. Note also that since the underlying support for the hardware is completely different in Maemo 5, the MeeGo plug-in will ''not'' work on (as is ''not'' trivially portable to) that platform.
The back-end plug-ins' source code is available in plugins/feedback. Note also that since the underlying support for the hardware is completely different in Maemo 5, the MeeGo plug-in will ''not'' work on (as is ''not'' trivially portable to) that platform.


==Haptics Player example application==
== Haptics Player example application ==


The small example demonstrating the feedback <span class="caps">API</span> is called “haptics player”. It allows to use all the features from the <span class="caps">API</span>. Select the kind of feedback from the tabs, and set the parameters on its form.
The small example demonstrating the feedback API is called &quot;haptics player&amp;quot;. It allows to use all the features from the API. Select the kind of feedback from the tabs, and set the parameters on its form.
 
===Categories:===
 
* [[:Category:Developing with Qt|Developing_with_Qt]]
** [[:Category:Developing with Qt::QtMobility|QtMobility]]

Revision as of 11:32, 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.

Feedback API

Summary

The Feedback API is a new API designed to help applications respond to user interaction and give feedback. That can be haptics or audio feedback.

Key features

The feedback API provides three kinds of feedback,

  • Theme-based feedback:
    You can decide on the reaction of your application by asking the system to execute a feedback that is theme specific. So for instance if you have a UI component that should be used as a button, you can make that happen.
  • Custom haptics:
    You can start a specific haptics feedback. You get to specify the duration, intensity, period, … That is useful if you need to be in complete control of the feedback that you want, for example in games. The system will play this feedback on an actuator. You can query the available actuators and their properties (name, state…) through the QFeedbackActuator class.
  • File support:
    For some technologies, you can get the feedback stored in a file. That can be a haptics feedback with all it parameters, a wave file… So there is support for loading those files and play them.
    There is currently the support for Immersion IVT files (for platforms that support it) and a Phonon backend to play sound.

Back-ends

Each kind of feedback is implemented by means of a plug-in back-end architecture. We currently have support for the MeeGo (through the MeeGo Touch API) and Symbian^3 platforms. Support is as follows,

Platform Theme-based Custom File-based
MeeGo Yes Yes Yes
Symbian^3 Yes Yes No

The back-end plug-ins' source code is available in plugins/feedback. Note also that since the underlying support for the hardware is completely different in Maemo 5, the MeeGo plug-in will not work on (as is not trivially portable to) that platform.

Haptics Player example application

The small example demonstrating the feedback API is called "haptics player&quot;. It allows to use all the features from the API. Select the kind of feedback from the tabs, and set the parameters on its form.