Maemo Wiki Mirror - User contributions [en]

Qt-Maemo

2009-12-15T09:55:57Z

82.181.173.103: /* Image:Help-contents.png Docs */

__NOTOC__

=[[Image:Kblogger.png‎ ]] News=
<div id="news"><div class="tm"><div class="bm"><div class="lm"><div class="rm"><div class="tl"><div class="tr"><div class="bl"><div class="br">
<ul class="recent">
<li class="first">
</li>
<li>
<b>11 Dec 09</b> - Bye bye old static web pages.. all our pages are now in Maemo Wiki. Old website is [http://qt4.garage.maemo.org/index-old.html here]
</li>
</ul>
</div></div></div></div></div></div></div></div></div>
<br>
<br>
.

=[[Image:Intro.png]] What is Qt?=
Qt (pronounced as the English word "cute") is a cross-platform application development framework.

It is produced by Nokia's Qt Development Frameworks division, which came into being after Nokia's acquisition of the Norwegian company Trolltech.

Qt uses standard C++, but makes extensive use of the C pre-processor to enrich the language. Qt can also be used in several other programming languages via language bindings.

Distributed under the terms of the GNU Lesser General Public License (among others), Qt is free and open source software.
<br>
<br>

=[[Image:Rocket.png]] Maemo Qt main features=
* Hildon Style
* Hildon Input Method
* Optimizations
* Hildon specific widget
** partial support in Qt 4.5
** Qt 4.6 will have full support
<br>
<br>

=[[Image:Pda.png]] Supported Maemo devices=
* Nokia N800/N810 (OS2008/Maemo4.1/Diablo)
* Nokia N900 (OS2009/Maemo5/Fremantle)
<br>
<br>

=[[Image:Ktorrent.png‎ ]] Installing Qt=

<div id="news"><div class="tm"><div class="bm"><div class="lm"><div class="rm"><div class="tl"><div class="tr"><div class="bl"><div class="br">
<ul class="recent">
<li class="first">
<H3>N8x0</H3>
Supported Maemo version: 4.1 (Diablo)

Latest stable packages are into extras repository:<br>
deb http://repository.maemo.org/extras/ diablo free non-free

Testing packages are in extras-devel<br>
deb http://repository.maemo.org/extras-devel/ diablo free non-free

Install Qt binaries onto the device: <i>sudo gainroot && apt-get install libqt4-gui</i>

Install Qt binaries and development packages into the SDK:
<i>fakeroot apt-get install libqt4-dev</i>
</li>
<li class="">
<H3>N900</H3>
Supported Maemo version: 5 (Fremantle)

Qt core packages (qtcore, xml...) are pre-installed into the device. Rest of packages (GUI, webkit...) are in the Application repository (enabled by default in every device).

They are downloaded automatically when user install application packages that depends from those.

OVI store can host Maemo Qt Applications as well as other official Maemo repositories.

'''Qt 4.5 - community port''' core packages are already into the device.

- Installing Qt binaries into the device: <i>sudo gainroot && apt-get install libqt4-gui</i>

- Installing Qt binaries and development packages in scratchbox: <i>fakeroot apt-get install libqt4-dev</i>

'''Qt 4.6''' is still underdevelopment. It's in extras-devel; To install Qt 4.6:

- Add add extras-devel repository to /etc/apt/source.list. You can do that adding following line to that file.

<i>deb http://repository.maemo.org/extras-devel/ fremantle free non-free</i>

- Run <i>apt-get update</i>

- Install lib packages into the device with: <i>fakeroot apt-get install libqt4-maemo5-gui</i>

- Install dev packages into the SDK with: <i>fakeroot apt-get install libqt4-maemo5-dev</i>

Note:

- Qt 4.6tp is installed to /opt/qt4-maemo5
</li>
</ul>
</div></div></div></div></div></div></div></div></div>.
<br>
<br>

=[[Image:Available-qtapps-32.png‎ ]]Available and proposed Qt Applications=
If you want to port a Qt application to Maemo or if you want to check if an application you love has been already ported.. well [http://wiki.maemo.org/Qt4HildonApplications this] is the place you would like to check;
<br>
<br>

=[[Image:Help-contents.png]] Docs=
Qt:
* [http://wiki.maemo.org/Qt4Hildon Qt 4 Hildon]

Non-Qt stuff:
* Fremantle:
** [http://sw.nokia.com/id/a3187f95-ad88-4233-b0ef-a182da3ec1c7/Hildon_2_2_Widget_UI_Specification_v1_0_en.pdf Hildon 2.2 Widget UI Spec -PDF]
** [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guid -PDF]
* Diablo
** ADD_SOMETHING_HERE
* Other Docs
** [http://www.forum.nokia.com/Tools_Docs_and_Code/Documentation/Latest.xhtml Forum Nokia Docs] contain Maemo as well as other documentation related to other Nokia platforms.
<br>
<br>

=[[Image:Bug.png]] Bug tracking=
* Diablo & Fremanlte Qt 4.5 port
** [https://bugs.maemo.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=Qt&content= View bug list]
** [https://bugs.maemo.org/enter_bug.cgi?product=Qt Report a new bug]
* Fremantle Qt 4.6 port
** [http://doc.trolltech.com/4.6/bughowto.html How to report a bug]
** [http://bugreports.qt.nokia.com/secure/CreateIssue!default.jspa Report a new bug]
** [http://bugreports.qt.nokia.com/secure/IssueNavigator.jspa?reset=true&&query=maemo&summary=true&description=true&body=true&environment=true&pid=10510 View bug list]

=[[Image:Helmet.png]] Code=
* Qt 4.5 (Diablo)
** http://gitorious.org/+qt-maemo-developers/qt/qt-maemo
* Qt 4.5 (Fremantle)
** http://gitorious.org/+qt-maemo-developers/qt/qt-maemo
* Qt 4.6 (Fremantle)
** http://qt.gitorious.org/qt/x11-maemo
<br>
<br>

=[[Image:Preferences-desktop-user.png]] Contacting us=
* IRC
** Currently this is main and faster way to communicate with Qt 4.6 and Qt 4.5 developers.
** Click [http://webchat.freenode.net/?channels=qt-maemo here] to join the #qt-maemo channel in frenode (irc.freenode.net).

* Mailing list
** [https://garage.maemo.org/mailman/listinfo/qt4-devel Click here to Subscribe to the Qt community ML]

* Forum
** [https://garage.maemo.org/forum/?group_id=424 Click here to enter the Forum]

Qt-Maemo

2009-12-11T14:24:41Z

82.181.173.103: /* Contacting us */

__NOTOC__

=News=
<div id="news"><div class="tm"><div class="bm"><div class="lm"><div class="rm"><div class="tl"><div class="tr"><div class="bl"><div class="br">
<ul class="recent">
<li class="first">
</li>
<li>
<b>11 Dec 09</b> - Bye bye old static web pages.. all our pages are now in Maemo Wiki. Old website is [http://qt4.garage.maemo.org/index-old.html here]
</li>
</ul>
</div></div></div></div></div></div></div></div></div>
<br>
<br>
.

=What is Qt?=
Qt (pronounced as the English word "cute") is a cross-platform application development framework.

It is produced by Nokia's Qt Development Frameworks division, which came into being after Nokia's acquisition of the Norwegian company Trolltech.

Qt uses standard C++, but makes extensive use of the C pre-processor to enrich the language. Qt can also be used in several other programming languages via language bindings.

Distributed under the terms of the GNU Lesser General Public License (among others), Qt is free and open source software.
<br>
<br>

=Maemo Qt main features=
* Hildon Style
* Hildon Input Method
* Optimizations
* Hildon specific widget
** partial support in Qt 4.5
** Qt 4.6 will have full support
<br>
<br>

=Supported Maemo devices=
* Nokia N800/N810 (OS2008/Maemo4.1/Diablo)
* Nokia N900 (OS2009/Maemo5/Fremantle)
<br>
<br>

=Installing Qt=

<div id="news"><div class="tm"><div class="bm"><div class="lm"><div class="rm"><div class="tl"><div class="tr"><div class="bl"><div class="br">
<ul class="recent">
<li class="first">
<H3>N8x0</H3>
Supported Maemo version: 4.1 (Diablo)

Latest stable packages are into extras repository:<br>
deb http://repository.maemo.org/extras/ diablo free non-free

Testing packages are in extras-devel<br>
deb http://repository.maemo.org/extras-devel/ diablo free non-free

</li>
<li class="">
<H3>N900</H3>
Supported Maemo version: 5 (Fremantle)

Qt core packages (qtcore, xml...) are pre-installed into the device. Rest of packages (GUI, webkit...) are in the Application repository (enabled by default in every device).

They are downloaded automatically when user install application packages that depends from those.

OVI store can host Maemo Qt Applications as well as other official Maemo repositories.

Current Maemo Qt packages are based on '''Qt 4.5'''.

'''Qt 4.6''' is still underdevelopment. It's in extras-devel;

deb http://repository.maemo.org/extras-devel/ fremantle free non-free

</li>
</ul>
</div></div></div></div></div></div></div></div></div>.
<br>
<br>

=Available and proposed Qt Applications=
http://wiki.maemo.org/Qt4HildonApplications
<br>
<br>

=Docs=
http://wiki.maemo.org/Qt4Hildon
<br>
<br>

=Bug tracking=
* Diablo & Fremanlte Qt 4.5 port

* Fremantle Qt 4.6 port

=Code=
* Qt 4.5 (Diablo)
** http://gitorious.org/+qt-maemo-developers/qt/qt-maemo
* Qt 4.5 (Fremantle)
** http://gitorious.org/+qt-maemo-developers/qt/qt-maemo
* Qt 4.6 (Fremantle)
** http://qt.gitorious.org/qt/x11-maemo
<br>
<br>

=Contacting us=
* IRC
** Currently this is main and faster way to communicate with Qt 4.6 and Qt 4.5 developers.
** Click [http://webchat.freenode.net/?channels=qt-maemo here] to join the #qt-maemo channel in frenode (irc.freenode.net).

* Mailing list
** [https://garage.maemo.org/mailman/listinfo/qt4-devel Click here to Subscribe to the Qt community ML]

* Forum
** [https://garage.maemo.org/forum/?group_id=424 Click here to enter the Forum]

Qt-Maemo

2009-12-11T13:44:51Z

82.181.173.103: /* News */

__NOTOC__

=News=
<div id="news"><div class="tm"><div class="bm"><div class="lm"><div class="rm"><div class="tl"><div class="tr"><div class="bl"><div class="br">
<ul class="recent">
<li class="first">
</li>
<li>
<b>11 Dec 09</b> - Bye bye old static web pages.. all our pages are now in Maemo Wiki. Old website is [http://qt4.garage.maemo.org/index-old.html here]
</li>
</ul>
</div></div></div></div></div></div></div></div></div>
<br>
<br>
.

=What is Qt?=
Qt (pronounced as the English word "cute") is a cross-platform application development framework.

It is produced by Nokia's Qt Development Frameworks division, which came into being after Nokia's acquisition of the Norwegian company Trolltech.

Qt uses standard C++, but makes extensive use of the C pre-processor to enrich the language. Qt can also be used in several other programming languages via language bindings.

Distributed under the terms of the GNU Lesser General Public License (among others), Qt is free and open source software.
<br>
<br>

=Maemo Qt main features=
* Hildon Style
* Hildon Input Method
* Optimizations
* Hildon specific widget
** partial support in Qt 4.5
** Qt 4.6 will have full support
<br>
<br>

=Supported Maemo devices=
* Nokia N800/N810 (OS2008/Maemo4.1/Diablo)
* Nokia N900 (OS2009/Maemo5/Fremantle)
<br>
<br>

=Installing Qt=

<div id="news"><div class="tm"><div class="bm"><div class="lm"><div class="rm"><div class="tl"><div class="tr"><div class="bl"><div class="br">
<ul class="recent">
<li class="first">
<H3>N8x0</H3>
Supported Maemo version: 4.1 (Diablo)

Latest stable packages are into extras repository:<br>
deb http://repository.maemo.org/extras/ diablo free non-free

Testing packages are in extras-devel<br>
deb http://repository.maemo.org/extras-devel/ diablo free non-free

</li>
<li class="">
<H3>N900</H3>
Supported Maemo version: 5 (Fremantle)

Qt core packages (qtcore, xml...) are pre-installed into the device. Rest of packages (GUI, webkit...) are in the Application repository (enabled by default in every device).

They are downloaded automatically when user install application packages that depends from those.

OVI store can host Maemo Qt Applications as well as other official Maemo repositories.

Current Maemo Qt packages are based on '''Qt 4.5'''.

'''Qt 4.6''' is still underdevelopment. It's in extras-devel;

deb http://repository.maemo.org/extras-devel/ fremantle free non-free

</li>
</ul>
</div></div></div></div></div></div></div></div></div>.
<br>
<br>

=Available and proposed Qt Applications=
http://wiki.maemo.org/Qt4HildonApplications
<br>
<br>

=Docs=
http://wiki.maemo.org/Qt4Hildon
<br>
<br>

=Bug tracking=
* Diablo & Fremanlte Qt 4.5 port

* Fremantle Qt 4.6 port

=Code=
* Qt 4.5 (Diablo)
** http://gitorious.org/+qt-maemo-developers/qt/qt-maemo
* Qt 4.5 (Fremantle)
** http://gitorious.org/+qt-maemo-developers/qt/qt-maemo
* Qt 4.6 (Fremantle)
** http://qt.gitorious.org/qt/x11-maemo
<br>
<br>

=Contacting us=
* IRC
** Currently this is main and faster way to communicate with Qt 4.6 and Qt 4.5 developers.
**

* Mailing list
** [https://garage.maemo.org/mailman/listinfo/qt4-devel Click here to Subscribe to the Qt community ML]

* Forum
** [https://garage.maemo.org/forum/?group_id=424 Click here to enter the Forum]

Qt4 Hildon Legacy

2009-11-06T18:26:46Z

82.181.173.103: /* Is it yet possible to create Fremantle desktop widgets using Qt? */

[[Image:MaemoQtPicture.png]]
<br><br>
== [[Image:Intro.png]] Intro ==

=== Maemo Platform ===

The Maemo Platform is the software stack for Nokia Internet Tablets, which includes the Maemo operating system and the Maemo SDK. The Maemo Platform is mostly based on open source code, and has been developed by the Maemo Software department within Nokia in collaboration with many open source projects such as the Linux kernel, Debian, and GNOME.<ref>[http://en.wikipedia.org/wiki/Maemo_Platform Maemo Platform on Wikipedia]</ref>

[http://maemo.org/intro/platform/ Read more...]

=== What is Hildon? ===

Hildon is an application framework for Linux operating system mobile devices (PDAs, mobile phones, etc), developed by Nokia for Maemo and now a part of GNOME, that focuses on providing a finger friendly interface.<ref>[http://en.wikipedia.org/wiki/Hildon Hildon on Wikipedia]</ref>

[http://live.gnome.org/Hildon Read more...]

=== Developing on Maemo ===

Developing applications for Maemo is done with the Maemo SDK. The process from creating the first prototype of your application to distributing to a wide audience consists basically of three steps:

* Share your application project in the [http://garage.maemo.org Garage].
* Make your application easy to install and put in the [[Extras]].
* Once your application has a high quality - be promoted to the [http://www.nokia.com/os2008 Nokia user site].

[http://maemo.org/intro/developer_overview/ Read more...]

=== Maemo SDK ===

The Maemo SDK is based around the Debian-oriented Scratchbox Cross Compilation Toolkit, which provides a sandbox environment in which development may take place. Scratchbox uses Qemu to emulate an ARMEL processor or sbrsh to remotely execute instructions. Scratchbox-compatible rootstraps are available for both x86 and ARMEL, so the majority of development and debugging takes place on x86, with final packaging being for ARMEL.<ref>[http://en.wikipedia.org/wiki/Maemo_Platform#Maemo_SDK Maemo SDK on Wikipedia]</ref>

[http://www.youtube.com/watch?v=c8myh_iBy8k Watch the Maemo SDK in action!]

=== What is Scratchbox? ===

Scratchbox is a cross compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross compile an entire Linux distribution.<ref>[http://en.wikipedia.org/wiki/Scratchbox Scratchbox on Wikipedia]</ref>

[http://www.scratchbox.org/ Read more...]

<br>

== [[Image:Rocket.png]] Getting started ==

To start to develop with Maemo Qt, we need to install the Maemo SDK on a Linux machine.

=== Hey, I don't have a Linux machine! ===
That's not a big problem. You can run Maemo SDK in a virtual machine;
You can download Maemo SDK virtual Image (Linux Ubuntu + Diablo and Fremantle SDK)
from [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php tablets-dev.nokia.com].
You can get VMPlayer from [http://www.vmware.com/products/player/ here].

=== Installing the Maemo SDK ===
Maemo SDK can be installaed in any Linux environment.
However Debian based distros (eg: Ubuntu) are recommended.

Documentation you need to install Maemo SDK is [http://maemo.org/development/sdks/ here].

=== Installing Qt packages in Scratchbox ===
Maemo Qt developers offers a set of Qt packages for Diablo (Maemo4.1 - OS2008)
and Fremantle (Maemo5 - OS2009).

==== Diablo ====
Diablo Qt packages are into the official Extras repository.
In order to start to develop with those packages you need to add
extras repository to your repository list.

1. Open /etc/apt/source.list with a text editor (eg: kate, gedit...)
2. Append the following line to that file:
deb http://repository.maemo.org/extras/ diablo free non-free
3. Then update your APT cache with
<i>apt-get update</i>
4. Install Qt packages with
<i>apt-get install libqt4-dev</i>

==== Fremantle ====
You don't need to add any extra repository for Fremantle since Qt packages are already available into the SDK.

Then you can install Qt with:
fakeroot apt-get install libqt4-gui libqt4-dev

===How to compile a Qt application in scratchbox===
Qt applications are usually built using QMake. Project like KDE instead replaced
QMake with CMake for more flexibility.

==== QMake ====
[http://doc.trolltech.com/4.5/qmake-manual.html QMake] is a tool from Trolltech that helps simplify the build process for development project across different platforms

You can build your Maemo Qt application in 3 simple steps:
1. Generating project file [Required if there is not .pro file into the app source tree]
<i>qmake -project</i>
2. Generating Makefile from the QMake project file:
qmake file.pro
3. make

==== CMake ====
As told before it's not a standard tool but it's largely used from people and application coming from the KDE world.
Because of some issue with CMake, Diablo CMake packages are currently useless since CMake segfaults. This issue has been solved in Fremantle and CMake packages that comes from Fremantle SDK work nicely.

- CMake projects has usually a CMakeLists.txt file instead of
- .pro file used by QMake projects
- Makefile.am used by Autotools projects (standard in Unix/Linux)

Using CMake to build the project is extremely easy.
In the directory containing CMakeLists.txt, supply the following two commands, where path is the path to the source code.

- cmake path
- make

Note: CMake is not installed by defualt in scratchbox. You can install it with
<i>apt-get install cmake</i>

===Running a Qt application in: ===
====A. Scratchbox====
Diablo and Fremantle Qt applications can run into the device as into scratchbox.

First step to run a Qt application is starting the SDK UI:

1. Run Xephyr. It's able to run a [http://en.wikipedia.org/wiki/X_Window_System X Server] inside another X Server.
<i>Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb</i>

2. Set display for application that runs inside scratchbox
<i><b>[sbox-DIABLO_<target>:~] ></b> export DISPLAY=:2</i>

3. You can now run the SDK UI. Diablo or Fremantle desktop will appear into your Xephyr window:
<i><b>[sbox-DIABLO_<target>:~] ></b> af-sb-init.sh start</i>

4. Now you are ready to run any Maemo or Maemo Qt application with
<i><b>[sbox-DIABLO_<target>:~] ></b> run-standalone.sh ./qtapps</i>

Note: run-standalone.sh sets some variable needed by Qt to use the Hildon style.

====B. device====
Maemo Qt applications are linux binaries. They can run into the device without any problem if you copy it/them in "partitions" mounted with exec flag. (Eg: /home/user or /opt in Fremantle).

Eg: If we want to run quassel (Qt IRC Client) we have to launch it with:
<b>Nokia-N900-44-1:/home/user#</b> ./quassel

<br><br>

== [[Image:Hammer.png]] Porting Qt applications to Maemo ==

===Intro===

Porting a Qt desktop application to Maemo requires very little effort. This because the Maemo Qt libraries will take care of giving the Hildon look & Feel and enabling the virtual input methods for your application.

===Overriding the Qt Maemo changes===

====Maemo Style====
Hildon Style is the default Qt application style. Other style available are:
* [http://doc.trolltech.com/4.4/gallery-cleanlooks.html QCleanLooks]
* [http://doc.trolltech.com/4.4/gallery-windows.html Windows]
* [http://doc.trolltech.com/4.4/gallery-plastique.html Plastique]

Qt application can use other Qt styles;
* Running your application with the style flag:
<i>./qt-test-application -style windows</i>

* Using [http://doc.trolltech.com/4.4/qapplication.html#setStyle QApplication::setStyle( QStyle * style )]

* If you want to change the style of a widget:[http://doc.trolltech.com/4.4/qwidget.html#setStyle QWidget::setStyle( QStyle * style )]

====Showing the status bar====

Hildon applications don't have a status bar. Qt for Maemo hides the status bar by default.
You can show it again by modifying your code.

TODO

====Using the Kinetic Finger Scrolling (cf Gtk's PannableArea)====
See [[Qt/Finger Scrolling|Finger Scrolling]]

===Adding Maemo changes to a Qt Application===

Some methods of Qt for Maemo are not available in the "standard" Qt libs, so a Qt application with specific Maemo Qt code can't be built outside the Maemo SDK. To avoid this issue, the developer can use the preprocessor directives, for example:

#ifdef Q_WS_HILDON
//Specific hildon code here
#endif

===Limitations===

Currently Qt Maemo lacks full support for Hildon widgets introduced in Maemo 5.

'''At the moment, creating a Qt application that follows Maemo 5 UI Style requires using custom Qt widgets, coded within the application itself'''.

There is work ongoing to provide Qt Hildon widgets for Maemo 5, see [http://wiki.maemo.org/Qt4_Hildon/Qt_Hildon_Widgets Qt Hildon Widgets]

To get the benefits of the ongoing Maemo 5 hildon integration work in Qt, you must get the latest Qt source code and compile it yourself. See [http://wiki.maemo.org/Qt4_Hildon#Building_Qt_from_GIT_rep Building Qt from GIT repository].

<br>
<br>

== [[Image:Bug.png]] Debugging a Qt application ==

===GDB ===

====Intro ====

The GNU Project Debugger, or gdb for short, is a general purpose debugger that can be used for various debugging purposes.

====Debugging a Qt application in Scratchbox====

TODO

====Debugging a Qt application on device====

<ol>
<li>Installing gdb on the device.<ol>
<li>Add the [http://maemo.org/development/tools/ SDK tools] repository to the catalogue list.</li>
<li>install gdb by using apt-get (require around 6 MB of space)</li>
</ol></li>
<li>Install the debug symbols files in scratchbox (ARMEL target)</li>
apt-get install libqt4-dbg
<li>Run the application (device side)</li>
$gdbserver 0.0.0.0:1234 ./qtApplication
<li>Run the gdb client on your host PC (scratchbox side)</li>
[sbox-DIABLO_ARMEL: ~/TEST/svn/qt4-x11-4.4.0/examples/widgets/tablet] > gdb ./qtApplication
<li>Set the target of gdb</li>
(gdb) target remote 172.21.37.117:1234
<li>Tell to gdb to continue to debug the application on the device</li>
(gdb) continue
<li>Wait some moments...</li>
<li>If necessary you can put break points; eg: for void QWidget::setPalette ( const QPalette & )</li>
(gdb) break QWidget::setPalette(QPalette const&)
Breakpoint 1 at 0x4026ae68

<li>Your application will appear on the device screen. Happy debugging!</li></ol>

===Links===

* [http://www.gnu.org/software/gdb/documentation/ GDB documentation & tutorials]
* [http://maemo.org/development/documentation/man_pages/gdbserver/ GDBServer man page]
* [http://maemo.org/maemo_release_documentation/maemo4.1.x/node15.html Maemo debugging guide]
* [http://repository.maemo.org/pool/diablo/free/g/gdb/ gdb debian package for Diablo]

<br><br>
== [[Image:chart.png]] Profiling a Qt application ==

=== OProfile ===

OProfile is a low overhead system-wide profiler for Linux. It can be used to find CPU usage bottlenecks in the whole system and within processes. It works fine in the device, but viewing the reports can take quite a long time (10 minutes) when fired up on N800/N810 devices. Therefore, it often makes sense to run opreport in scratchbox.

If you want to know more about OProfile in Maemo see the [http://maemo.org/development/tools/doc/chinook/oprofile/ documentation].

=== Valgrind ===

TODO

<br><br>

== [[Image:chart.png]] Qt benchmarks ==
2D graphic benchmark tools:

* [[Qt/Benchmark/qgear|QGears]]
3D graphic benchmark tools:

* TODO
<br><br><br>

== [[Image:package.png]] Packaging a Qt application for Maemo ==

{{main|Packaging a Qt application}}

<br><br>
== [[Image:Helmet.png]] Maemo Qt API Reference ==

Maemo Qt is based on Qt for X11. It shares same APIs avoiding API breaks. In this way every Qt application that runs in other platforms (Windows, Mac OS X, Linux, S60, etc.) can run in Maemo devices as well.
To Develop a Qt application you can use the [http://doc.trolltech.com/4.5/index.html Official Qt 4.5 API documentation] and the list below to see what are the Maemo changes.

===Diablo===
'''QString QDesktopServices::storageLocation(StandardLocation type)''' returns specific Maemo locations for these types:
- DesktopLocation: QDir::homePath() + QLatin1String("/MyDocs"), instead of QDir::homePath() + QLatin1String("/Desktop")
- DocumentsLocation: QDir::homePath() + QLatin1String("/MyDocs/.documents"), instead of QDir::homePath() + QLatin1String("/MyDocs/.documents")
- PicturesLocation: QDir::homePath() + QLatin1String("/MyDocs/.images"), instead of QDir::homePath() + QLatin1String("/Pictures")
- MusicLocation: QDir::homePath() + QLatin1String("/MyDocs/.sounds"), instead of QDir::homePath() + QLatin1String("/Music")
- MoviesLocation: QDir::homePath() + QLatin1String("/MyDocs/.videos"), instead of QDir::homePath() + QLatin1String("/MyDocs/.videos")

'''QTabletEvents''' are able to get the pressure value from the touchscreen.
- The eventdeviceType is for the touchscreen is set to QTabletEvent::Stylus.
- QTabletEvents won't be used anymore in Fremantle

'''Finger poke''' is emulated in scratchbox by the Middle Mouse button (NOTE: There is no Fullscreen VKB in scratchbox)

'''QInputEvents''' don't move the cursor.
It's mandatory to get working the HIM moving the cursor via QInputMethodEvents.
Why is it mandatory?
Because if the user select text with the finger from the right to the left, we are able to remove the highlighted text, but the
cursor will be moved on the last char instead to stay on the first one.

To do that some changes has been added to some widget function like: ''widget::inputMethodEvent(QInputMethodEvent *e)''.
Modifing that function in some custom widgets may be necessary.
Don't reimplementing that function will break some fullscreen virtual keyboard features.

'''Hardcoded Keys:'''
In the QMainWindow:
- F6 - Toggle fullscreen the application
- F4 - Shows/Hides the application context menu
- Zoom in - is a standard [http://doc.trolltech.com/4.4/qkeysequence.html#StandardKey-enum key sequence] QKeySequence::ZoomIn
- Zoom out - is a standard [http://doc.trolltech.com/4.4/qkeysequence.html#StandardKey-enum key sequence] QKeySequence::ZoomOut

'''Input Method:'''
Maemo Qt uses the Hildon IM as default Input method.
Each kind of widget can set the IM mode. This allows the input method to focus on the type of input that the application is expecting.
Eg: spinboxes can receive only numeric characters (1-9).

NOTE: Qt widgets like QTextEdit, QLineEdit... set the right input method mode automatically.

A developer can change it by using:
void QInputContext::setInputMode(int mode);
It will update immediately the Hildon Input method to use the selected IM mode.

HIC Modes:
HILDON_GTK_INPUT_MODE_ALPHA alphabetical characters and whitespace
HILDON_GTK_INPUT_MODE_NUMERIC numbers 0-9 and the '-' character
HILDON_GTK_INPUT_MODE_SPECIAL special characters
HILDON_GTK_INPUT_MODE_HEXA hexadecimal characters; numbers 0-9, characters a-f, and A-F
HILDON_GTK_INPUT_MODE_TELE telephone numbers; numbers 0-9, whitespace, and the characters "pwPW/().-+*#?,"
HILDON_GTK_INPUT_MODE_FULL unrestricted entry mode, combination of the alpha, numeric and special modes.
HILDON_GTK_INPUT_MODE_MULTILINE the client contains multiple lines of text or accepts linebreaks in the input.
HILDON_GTK_INPUT_MODE_INVISIBLE do not echo or save the input in the IM when entering sensitive information such as passwords.
HILDON_GTK_INPUT_MODE_AUTOCAP automatically capitalize the first letter at the start of a sentence.
HILDON_GTK_INPUT_MODE_DICTIONARY enable predictive dictionaries and learning based on the input.

Example:
For a password field we need to set a specific IM mode:
int mode = HILDON_GTK_INPUT_MODE_FULL | HILDON_GTK_INPUT_MODE_INVISIBLE
QInputContext qic = widget->inputContext();
qic->setInputMode(mode);

If you are developing a Custom widget able to receive input text, you can instruct your widget to use the right IM Mode just returning
the mode.

- How does it work?
The Hildon IM sends a XMessage to pop up the "Virtual Keyboard" (or better the Main HIM UI) when an input widget receive the focus.
The IM before to raise the VKB, makes an inputMethodQuery to the widget retrieving the IM mode.
If the developer of the custom widget doesn't set the mode property, the IM will use HILDON_GTK_INPUT_MODE_FULL (the default mode) for that widget.

Setting the ImMode is quite easy. Check the code below for more understanding.

#ifdef Q_WS_HILDON
#include <QInputContext>
#endif

QVariant QAbstractSpinBox::inputMethodQuery(Qt::InputMethodQuery query) const
{
Q_D(const QAbstractSpinBox);
switch(query) {
case Qt::ImMode:{
int mode = HILDON_GTK_INPUT_MODE_NUMERIC;
return QVariant(mode);
}
default:
return d->edit->inputMethodQuery(query);
}
}

===FREMANTLE===
[TODO]

Note:
Printing (QPrint*) and System tray support has been compiled out in current
Qt 4.5.3-xxxx-maemo4 packages.
Since incompatibility with KDE, they will be enabled again in next Qt 4.5.3 packages.

<br><br>

== [[Image:Helmet.png]] Contributing to the Maemo Qt Project ==

Maemo Qt is a community project. Contributing to the forum, sending us patches, give us feedbacks, tracking bugs are all activities that help us to improve the quality of our work.

Here there is a list of things that every person interested in helping us should read.

===Be updated===
Any Maemo Qt developer should be updated and should participate to the discussions, for that he must join the Mailing list.
BTW the mailing list is not for Maemo Qt Developers but it's open to Maemo Qt application developers too.

=== Introduction to Git ===
If you are a git newbie you maybe find interesting these links:
* http://www.sourcemage.org/Git_Guide
* http://www.gitcasts.com/
* http://www.gnome.org/~newren/eg/git-for-svn-users.html
* Using the git protocol through a HTTP CONNECT proxy: http://www.emilsit.net/blog/archives/how-to-use-the-git-protocol-through-a-http-connect-proxy/

===Understanding the structure of our Git repository===
These info are here:[[Qt Maemo Git Process]].

=== Preparation ===
Make sure each scratchbox target has

fakeroot apt-get build-dep libqt4-gui

(you may need to apt-get install libgl-dev too as it's not in the Build-Depends: yet)

===Building Qt from GIT rep===

* Clone the repository:
git clone git://gitorious.org/+qt-maemo-developers/qt/qt-maemo.git
or if you are a member of our team:
git clone git@gitorious.org:+qt-maemo-developers/qt/qt-maemo.git

* Change dir
cd qt-maemo

* Copy the remote 4.5 branch in your workingcopy
git checkout -b 4.5 origin/4.5

* Checkout ONE of these branches:
git checkout -b qt-diablo origin/qt-diablo
git checkout -b qt-n900 origin/qt-n900
git checkout -b qt-mer origin/qt-mer

* Build the packages:
dpkg-buildpackage -rfakeroot -b

===Checking out all the remote branches===
* Clone the repository:
git clone git://gitorious.org/+qt-maemo-developers/qt/qt-maemo.git
or if you are a member of our team:
git clone git@gitorious.org:+qt-maemo-developers/qt/qt-maemo.git

* Change dir
cd qt-maemo

* Check out our script branch
git checkout -b maemo-qt-scripts origin/maemo-qt-scripts

* Save a copy of the script outside the working directories
cp maemo-qt-scripts/copy-all-remote-branches-locally/copy.sh ../

* Launch the copy.sh script
../copy.sh

===Commit changes in SVN [OLD]===

If you are a Maemo Qt developer and you want to save your changes in the Garage SVN but your project is not ready to go to the main line (trunk/qt-x11), you should create a private branch and then work there until the merging with the mainline.

For that you have to create a your directory in branches/ named ''developer_name-qt''. After that you can copy trunk/qt-x11 in your directory.
svn copy --username developer_name https://garage.maemo.org/svn/qt4/trunk/qt-x11 https://garage.maemo.org/svn/qt4/branches/developer_name-qt -m "Creating private branch of trunk/qt-x11"

NOTE: Subversion uses cheap copy, so them don't increase the size of the repository. Then feel free to create your own branch.

===Merging branches changes in the mainline [OLD]===

Before to merge your changes in the mainline, the code must be full working, cleaned and tested. A review from another developer is also needed in order to reduce the possibility to add errors.
<br><br>

==[[Image:Help-contents.png]] F.A.Q.==

=== I'm trying to compile a Qt application for ARMEL, but I got the error below. What's wrong? ===

/targets/FREMANTLE_X86/usr/include/qt4/QtCore/qatomic_i386.h:127: error: impossible constraint in 'asm'

You are using x86 include files, then you have to update your Makefile. Running <code>qmake</code> before <code>make</code> will be solve this issue.

=== I'm trying to compile a Qt packcage for x86, but I got the error below. What's wrong? ===

In file included from maemo/gconfsymbols.cpp:41:
maemo/gconfsymbols_p.h:49:25: gconf/gconf.h: No such file or directory

Your scratchbox does not have <code>/bin/sh</code>, so when calling <code>pkg-config</code> from <code>qmake</code>, <code>CFLAGS</code> and <code>LIBS</code> are not set correctly. Running <code>ln -s /scratchbox/tools/bin/sh /bin/sh</code> will be solve this issue.

=== I'm trying to compile a diablo Qt package, so I just created a symbolic link, debian, for debian.diablo, and then run dpkg-buildpackage command, but I got a build error because the symbolic link was deleted. ===

When running dpkg-buildpackage, all symbolic links will be deleted, so need to rename the folder from debian.diablo to debian to make a build of diablo Qt package.

=== I installed Qt (libqt4-dev) to scratchbox and tried to build a sample application, but I got the error because some header files such as qhildonstyle.h, and qvfbhdr.h etc. were missing. ===

libqt4-dev should copy all header files, but now, at least in 4.5.2-1maemo1, some files are missing. Please download file below and extract to your scratchbox system.

http://qt4.garage.maemo.org/patches/qt4-missing-header.tgz

===Installing Qt on N900===
If you have already a fremantle device then you can install new Qt packages from extras-devel.
The step to follow are:
* Free space
* echo "deb http://repository.maemo.org/extras-devel/ fremantle free non-free
" >> /etc/apt/sources.list.d/hildon-application-manager.list
* apt-get install libqt4-gui
The basic packages will be so installed.

Current known issues:
* libqt4-opengl depends by libgles2, but it is not installable anymore.Has it been replaced with libgles2-sgx-img?

===Where are the Hildon Widgets for Qt===
Short answer : they've not been written.... yet.

Qt allows you to create your own widgets very easily. However, in order to provide as consistent an appearance as possible for the Maemo platform the community will be creating a set of [[/Qt Hildon Widgets|Qt Hildon Widgets]]

===Is it possible to create fremantle desktop widgets with Qt?===
Yes, but unfortunately you can't load them with the widget manager since hildon widgets are GTK shared object file.

A simple Qt hildon-desktop widget is in Extras-devel; Browse your application manager and look for qt-example-hildondesktopwidget.

== How to minimize a Qt application? ==
QDBusConnection c = QDBusConnection::sessionBus();
QDBusMessage m = QDBusMessage::createSignal("/","com.nokia.hildon_desktop","exit_app_view");
c.send(m);

== References ==

<references/>

[[Category:Development]]
[[Category:Qt]]

Qt4 Hildon Legacy

2009-11-06T18:25:28Z

82.181.173.103: /* Is it yet possible to create Fremantle desktop widgets using Qt? */

[[Image:MaemoQtPicture.png]]
<br><br>
== [[Image:Intro.png]] Intro ==

=== Maemo Platform ===

The Maemo Platform is the software stack for Nokia Internet Tablets, which includes the Maemo operating system and the Maemo SDK. The Maemo Platform is mostly based on open source code, and has been developed by the Maemo Software department within Nokia in collaboration with many open source projects such as the Linux kernel, Debian, and GNOME.<ref>[http://en.wikipedia.org/wiki/Maemo_Platform Maemo Platform on Wikipedia]</ref>

[http://maemo.org/intro/platform/ Read more...]

=== What is Hildon? ===

Hildon is an application framework for Linux operating system mobile devices (PDAs, mobile phones, etc), developed by Nokia for Maemo and now a part of GNOME, that focuses on providing a finger friendly interface.<ref>[http://en.wikipedia.org/wiki/Hildon Hildon on Wikipedia]</ref>

[http://live.gnome.org/Hildon Read more...]

=== Developing on Maemo ===

Developing applications for Maemo is done with the Maemo SDK. The process from creating the first prototype of your application to distributing to a wide audience consists basically of three steps:

* Share your application project in the [http://garage.maemo.org Garage].
* Make your application easy to install and put in the [[Extras]].
* Once your application has a high quality - be promoted to the [http://www.nokia.com/os2008 Nokia user site].

[http://maemo.org/intro/developer_overview/ Read more...]

=== Maemo SDK ===

The Maemo SDK is based around the Debian-oriented Scratchbox Cross Compilation Toolkit, which provides a sandbox environment in which development may take place. Scratchbox uses Qemu to emulate an ARMEL processor or sbrsh to remotely execute instructions. Scratchbox-compatible rootstraps are available for both x86 and ARMEL, so the majority of development and debugging takes place on x86, with final packaging being for ARMEL.<ref>[http://en.wikipedia.org/wiki/Maemo_Platform#Maemo_SDK Maemo SDK on Wikipedia]</ref>

[http://www.youtube.com/watch?v=c8myh_iBy8k Watch the Maemo SDK in action!]

=== What is Scratchbox? ===

Scratchbox is a cross compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross compile an entire Linux distribution.<ref>[http://en.wikipedia.org/wiki/Scratchbox Scratchbox on Wikipedia]</ref>

[http://www.scratchbox.org/ Read more...]

<br>

== [[Image:Rocket.png]] Getting started ==

To start to develop with Maemo Qt, we need to install the Maemo SDK on a Linux machine.

=== Hey, I don't have a Linux machine! ===
That's not a big problem. You can run Maemo SDK in a virtual machine;
You can download Maemo SDK virtual Image (Linux Ubuntu + Diablo and Fremantle SDK)
from [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php tablets-dev.nokia.com].
You can get VMPlayer from [http://www.vmware.com/products/player/ here].

=== Installing the Maemo SDK ===
Maemo SDK can be installaed in any Linux environment.
However Debian based distros (eg: Ubuntu) are recommended.

Documentation you need to install Maemo SDK is [http://maemo.org/development/sdks/ here].

=== Installing Qt packages in Scratchbox ===
Maemo Qt developers offers a set of Qt packages for Diablo (Maemo4.1 - OS2008)
and Fremantle (Maemo5 - OS2009).

==== Diablo ====
Diablo Qt packages are into the official Extras repository.
In order to start to develop with those packages you need to add
extras repository to your repository list.

1. Open /etc/apt/source.list with a text editor (eg: kate, gedit...)
2. Append the following line to that file:
deb http://repository.maemo.org/extras/ diablo free non-free
3. Then update your APT cache with
<i>apt-get update</i>
4. Install Qt packages with
<i>apt-get install libqt4-dev</i>

==== Fremantle ====
You don't need to add any extra repository for Fremantle since Qt packages are already available into the SDK.

Then you can install Qt with:
fakeroot apt-get install libqt4-gui libqt4-dev

===How to compile a Qt application in scratchbox===
Qt applications are usually built using QMake. Project like KDE instead replaced
QMake with CMake for more flexibility.

==== QMake ====
[http://doc.trolltech.com/4.5/qmake-manual.html QMake] is a tool from Trolltech that helps simplify the build process for development project across different platforms

You can build your Maemo Qt application in 3 simple steps:
1. Generating project file [Required if there is not .pro file into the app source tree]
<i>qmake -project</i>
2. Generating Makefile from the QMake project file:
qmake file.pro
3. make

==== CMake ====
As told before it's not a standard tool but it's largely used from people and application coming from the KDE world.
Because of some issue with CMake, Diablo CMake packages are currently useless since CMake segfaults. This issue has been solved in Fremantle and CMake packages that comes from Fremantle SDK work nicely.

- CMake projects has usually a CMakeLists.txt file instead of
- .pro file used by QMake projects
- Makefile.am used by Autotools projects (standard in Unix/Linux)

Using CMake to build the project is extremely easy.
In the directory containing CMakeLists.txt, supply the following two commands, where path is the path to the source code.

- cmake path
- make

Note: CMake is not installed by defualt in scratchbox. You can install it with
<i>apt-get install cmake</i>

===Running a Qt application in: ===
====A. Scratchbox====
Diablo and Fremantle Qt applications can run into the device as into scratchbox.

First step to run a Qt application is starting the SDK UI:

1. Run Xephyr. It's able to run a [http://en.wikipedia.org/wiki/X_Window_System X Server] inside another X Server.
<i>Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb</i>

2. Set display for application that runs inside scratchbox
<i><b>[sbox-DIABLO_<target>:~] ></b> export DISPLAY=:2</i>

3. You can now run the SDK UI. Diablo or Fremantle desktop will appear into your Xephyr window:
<i><b>[sbox-DIABLO_<target>:~] ></b> af-sb-init.sh start</i>

4. Now you are ready to run any Maemo or Maemo Qt application with
<i><b>[sbox-DIABLO_<target>:~] ></b> run-standalone.sh ./qtapps</i>

Note: run-standalone.sh sets some variable needed by Qt to use the Hildon style.

====B. device====
Maemo Qt applications are linux binaries. They can run into the device without any problem if you copy it/them in "partitions" mounted with exec flag. (Eg: /home/user or /opt in Fremantle).

Eg: If we want to run quassel (Qt IRC Client) we have to launch it with:
<b>Nokia-N900-44-1:/home/user#</b> ./quassel

<br><br>

== [[Image:Hammer.png]] Porting Qt applications to Maemo ==

===Intro===

Porting a Qt desktop application to Maemo requires very little effort. This because the Maemo Qt libraries will take care of giving the Hildon look & Feel and enabling the virtual input methods for your application.

===Overriding the Qt Maemo changes===

====Maemo Style====
Hildon Style is the default Qt application style. Other style available are:
* [http://doc.trolltech.com/4.4/gallery-cleanlooks.html QCleanLooks]
* [http://doc.trolltech.com/4.4/gallery-windows.html Windows]
* [http://doc.trolltech.com/4.4/gallery-plastique.html Plastique]

Qt application can use other Qt styles;
* Running your application with the style flag:
<i>./qt-test-application -style windows</i>

* Using [http://doc.trolltech.com/4.4/qapplication.html#setStyle QApplication::setStyle( QStyle * style )]

* If you want to change the style of a widget:[http://doc.trolltech.com/4.4/qwidget.html#setStyle QWidget::setStyle( QStyle * style )]

====Showing the status bar====

Hildon applications don't have a status bar. Qt for Maemo hides the status bar by default.
You can show it again by modifying your code.

TODO

====Using the Kinetic Finger Scrolling (cf Gtk's PannableArea)====
See [[Qt/Finger Scrolling|Finger Scrolling]]

===Adding Maemo changes to a Qt Application===

Some methods of Qt for Maemo are not available in the "standard" Qt libs, so a Qt application with specific Maemo Qt code can't be built outside the Maemo SDK. To avoid this issue, the developer can use the preprocessor directives, for example:

#ifdef Q_WS_HILDON
//Specific hildon code here
#endif

===Limitations===

Currently Qt Maemo lacks full support for Hildon widgets introduced in Maemo 5.

'''At the moment, creating a Qt application that follows Maemo 5 UI Style requires using custom Qt widgets, coded within the application itself'''.

There is work ongoing to provide Qt Hildon widgets for Maemo 5, see [http://wiki.maemo.org/Qt4_Hildon/Qt_Hildon_Widgets Qt Hildon Widgets]

To get the benefits of the ongoing Maemo 5 hildon integration work in Qt, you must get the latest Qt source code and compile it yourself. See [http://wiki.maemo.org/Qt4_Hildon#Building_Qt_from_GIT_rep Building Qt from GIT repository].

<br>
<br>

== [[Image:Bug.png]] Debugging a Qt application ==

===GDB ===

====Intro ====

The GNU Project Debugger, or gdb for short, is a general purpose debugger that can be used for various debugging purposes.

====Debugging a Qt application in Scratchbox====

TODO

====Debugging a Qt application on device====

<ol>
<li>Installing gdb on the device.<ol>
<li>Add the [http://maemo.org/development/tools/ SDK tools] repository to the catalogue list.</li>
<li>install gdb by using apt-get (require around 6 MB of space)</li>
</ol></li>
<li>Install the debug symbols files in scratchbox (ARMEL target)</li>
apt-get install libqt4-dbg
<li>Run the application (device side)</li>
$gdbserver 0.0.0.0:1234 ./qtApplication
<li>Run the gdb client on your host PC (scratchbox side)</li>
[sbox-DIABLO_ARMEL: ~/TEST/svn/qt4-x11-4.4.0/examples/widgets/tablet] > gdb ./qtApplication
<li>Set the target of gdb</li>
(gdb) target remote 172.21.37.117:1234
<li>Tell to gdb to continue to debug the application on the device</li>
(gdb) continue
<li>Wait some moments...</li>
<li>If necessary you can put break points; eg: for void QWidget::setPalette ( const QPalette & )</li>
(gdb) break QWidget::setPalette(QPalette const&)
Breakpoint 1 at 0x4026ae68

<li>Your application will appear on the device screen. Happy debugging!</li></ol>

===Links===

* [http://www.gnu.org/software/gdb/documentation/ GDB documentation & tutorials]
* [http://maemo.org/development/documentation/man_pages/gdbserver/ GDBServer man page]
* [http://maemo.org/maemo_release_documentation/maemo4.1.x/node15.html Maemo debugging guide]
* [http://repository.maemo.org/pool/diablo/free/g/gdb/ gdb debian package for Diablo]

<br><br>
== [[Image:chart.png]] Profiling a Qt application ==

=== OProfile ===

OProfile is a low overhead system-wide profiler for Linux. It can be used to find CPU usage bottlenecks in the whole system and within processes. It works fine in the device, but viewing the reports can take quite a long time (10 minutes) when fired up on N800/N810 devices. Therefore, it often makes sense to run opreport in scratchbox.

If you want to know more about OProfile in Maemo see the [http://maemo.org/development/tools/doc/chinook/oprofile/ documentation].

=== Valgrind ===

TODO

<br><br>

== [[Image:chart.png]] Qt benchmarks ==
2D graphic benchmark tools:

* [[Qt/Benchmark/qgear|QGears]]
3D graphic benchmark tools:

* TODO
<br><br><br>

== [[Image:package.png]] Packaging a Qt application for Maemo ==

{{main|Packaging a Qt application}}

<br><br>
== [[Image:Helmet.png]] Maemo Qt API Reference ==

Maemo Qt is based on Qt for X11. It shares same APIs avoiding API breaks. In this way every Qt application that runs in other platforms (Windows, Mac OS X, Linux, S60, etc.) can run in Maemo devices as well.
To Develop a Qt application you can use the [http://doc.trolltech.com/4.5/index.html Official Qt 4.5 API documentation] and the list below to see what are the Maemo changes.

===Diablo===
'''QString QDesktopServices::storageLocation(StandardLocation type)''' returns specific Maemo locations for these types:
- DesktopLocation: QDir::homePath() + QLatin1String("/MyDocs"), instead of QDir::homePath() + QLatin1String("/Desktop")
- DocumentsLocation: QDir::homePath() + QLatin1String("/MyDocs/.documents"), instead of QDir::homePath() + QLatin1String("/MyDocs/.documents")
- PicturesLocation: QDir::homePath() + QLatin1String("/MyDocs/.images"), instead of QDir::homePath() + QLatin1String("/Pictures")
- MusicLocation: QDir::homePath() + QLatin1String("/MyDocs/.sounds"), instead of QDir::homePath() + QLatin1String("/Music")
- MoviesLocation: QDir::homePath() + QLatin1String("/MyDocs/.videos"), instead of QDir::homePath() + QLatin1String("/MyDocs/.videos")

'''QTabletEvents''' are able to get the pressure value from the touchscreen.
- The eventdeviceType is for the touchscreen is set to QTabletEvent::Stylus.
- QTabletEvents won't be used anymore in Fremantle

'''Finger poke''' is emulated in scratchbox by the Middle Mouse button (NOTE: There is no Fullscreen VKB in scratchbox)

'''QInputEvents''' don't move the cursor.
It's mandatory to get working the HIM moving the cursor via QInputMethodEvents.
Why is it mandatory?
Because if the user select text with the finger from the right to the left, we are able to remove the highlighted text, but the
cursor will be moved on the last char instead to stay on the first one.

To do that some changes has been added to some widget function like: ''widget::inputMethodEvent(QInputMethodEvent *e)''.
Modifing that function in some custom widgets may be necessary.
Don't reimplementing that function will break some fullscreen virtual keyboard features.

'''Hardcoded Keys:'''
In the QMainWindow:
- F6 - Toggle fullscreen the application
- F4 - Shows/Hides the application context menu
- Zoom in - is a standard [http://doc.trolltech.com/4.4/qkeysequence.html#StandardKey-enum key sequence] QKeySequence::ZoomIn
- Zoom out - is a standard [http://doc.trolltech.com/4.4/qkeysequence.html#StandardKey-enum key sequence] QKeySequence::ZoomOut

'''Input Method:'''
Maemo Qt uses the Hildon IM as default Input method.
Each kind of widget can set the IM mode. This allows the input method to focus on the type of input that the application is expecting.
Eg: spinboxes can receive only numeric characters (1-9).

NOTE: Qt widgets like QTextEdit, QLineEdit... set the right input method mode automatically.

A developer can change it by using:
void QInputContext::setInputMode(int mode);
It will update immediately the Hildon Input method to use the selected IM mode.

HIC Modes:
HILDON_GTK_INPUT_MODE_ALPHA alphabetical characters and whitespace
HILDON_GTK_INPUT_MODE_NUMERIC numbers 0-9 and the '-' character
HILDON_GTK_INPUT_MODE_SPECIAL special characters
HILDON_GTK_INPUT_MODE_HEXA hexadecimal characters; numbers 0-9, characters a-f, and A-F
HILDON_GTK_INPUT_MODE_TELE telephone numbers; numbers 0-9, whitespace, and the characters "pwPW/().-+*#?,"
HILDON_GTK_INPUT_MODE_FULL unrestricted entry mode, combination of the alpha, numeric and special modes.
HILDON_GTK_INPUT_MODE_MULTILINE the client contains multiple lines of text or accepts linebreaks in the input.
HILDON_GTK_INPUT_MODE_INVISIBLE do not echo or save the input in the IM when entering sensitive information such as passwords.
HILDON_GTK_INPUT_MODE_AUTOCAP automatically capitalize the first letter at the start of a sentence.
HILDON_GTK_INPUT_MODE_DICTIONARY enable predictive dictionaries and learning based on the input.

Example:
For a password field we need to set a specific IM mode:
int mode = HILDON_GTK_INPUT_MODE_FULL | HILDON_GTK_INPUT_MODE_INVISIBLE
QInputContext qic = widget->inputContext();
qic->setInputMode(mode);

If you are developing a Custom widget able to receive input text, you can instruct your widget to use the right IM Mode just returning
the mode.

- How does it work?
The Hildon IM sends a XMessage to pop up the "Virtual Keyboard" (or better the Main HIM UI) when an input widget receive the focus.
The IM before to raise the VKB, makes an inputMethodQuery to the widget retrieving the IM mode.
If the developer of the custom widget doesn't set the mode property, the IM will use HILDON_GTK_INPUT_MODE_FULL (the default mode) for that widget.

Setting the ImMode is quite easy. Check the code below for more understanding.

#ifdef Q_WS_HILDON
#include <QInputContext>
#endif

QVariant QAbstractSpinBox::inputMethodQuery(Qt::InputMethodQuery query) const
{
Q_D(const QAbstractSpinBox);
switch(query) {
case Qt::ImMode:{
int mode = HILDON_GTK_INPUT_MODE_NUMERIC;
return QVariant(mode);
}
default:
return d->edit->inputMethodQuery(query);
}
}

===FREMANTLE===
[TODO]

Note:
Printing (QPrint*) and System tray support has been compiled out in current
Qt 4.5.3-xxxx-maemo4 packages.
Since incompatibility with KDE, they will be enabled again in next Qt 4.5.3 packages.

<br><br>

== [[Image:Helmet.png]] Contributing to the Maemo Qt Project ==

Maemo Qt is a community project. Contributing to the forum, sending us patches, give us feedbacks, tracking bugs are all activities that help us to improve the quality of our work.

Here there is a list of things that every person interested in helping us should read.

===Be updated===
Any Maemo Qt developer should be updated and should participate to the discussions, for that he must join the Mailing list.
BTW the mailing list is not for Maemo Qt Developers but it's open to Maemo Qt application developers too.

=== Introduction to Git ===
If you are a git newbie you maybe find interesting these links:
* http://www.sourcemage.org/Git_Guide
* http://www.gitcasts.com/
* http://www.gnome.org/~newren/eg/git-for-svn-users.html
* Using the git protocol through a HTTP CONNECT proxy: http://www.emilsit.net/blog/archives/how-to-use-the-git-protocol-through-a-http-connect-proxy/

===Understanding the structure of our Git repository===
These info are here:[[Qt Maemo Git Process]].

=== Preparation ===
Make sure each scratchbox target has

fakeroot apt-get build-dep libqt4-gui

(you may need to apt-get install libgl-dev too as it's not in the Build-Depends: yet)

===Building Qt from GIT rep===

* Clone the repository:
git clone git://gitorious.org/+qt-maemo-developers/qt/qt-maemo.git
or if you are a member of our team:
git clone git@gitorious.org:+qt-maemo-developers/qt/qt-maemo.git

* Change dir
cd qt-maemo

* Copy the remote 4.5 branch in your workingcopy
git checkout -b 4.5 origin/4.5

* Checkout ONE of these branches:
git checkout -b qt-diablo origin/qt-diablo
git checkout -b qt-n900 origin/qt-n900
git checkout -b qt-mer origin/qt-mer

* Build the packages:
dpkg-buildpackage -rfakeroot -b

===Checking out all the remote branches===
* Clone the repository:
git clone git://gitorious.org/+qt-maemo-developers/qt/qt-maemo.git
or if you are a member of our team:
git clone git@gitorious.org:+qt-maemo-developers/qt/qt-maemo.git

* Change dir
cd qt-maemo

* Check out our script branch
git checkout -b maemo-qt-scripts origin/maemo-qt-scripts

* Save a copy of the script outside the working directories
cp maemo-qt-scripts/copy-all-remote-branches-locally/copy.sh ../

* Launch the copy.sh script
../copy.sh

===Commit changes in SVN [OLD]===

If you are a Maemo Qt developer and you want to save your changes in the Garage SVN but your project is not ready to go to the main line (trunk/qt-x11), you should create a private branch and then work there until the merging with the mainline.

For that you have to create a your directory in branches/ named ''developer_name-qt''. After that you can copy trunk/qt-x11 in your directory.
svn copy --username developer_name https://garage.maemo.org/svn/qt4/trunk/qt-x11 https://garage.maemo.org/svn/qt4/branches/developer_name-qt -m "Creating private branch of trunk/qt-x11"

NOTE: Subversion uses cheap copy, so them don't increase the size of the repository. Then feel free to create your own branch.

===Merging branches changes in the mainline [OLD]===

Before to merge your changes in the mainline, the code must be full working, cleaned and tested. A review from another developer is also needed in order to reduce the possibility to add errors.
<br><br>

==[[Image:Help-contents.png]] F.A.Q.==

=== I'm trying to compile a Qt application for ARMEL, but I got the error below. What's wrong? ===

/targets/FREMANTLE_X86/usr/include/qt4/QtCore/qatomic_i386.h:127: error: impossible constraint in 'asm'

You are using x86 include files, then you have to update your Makefile. Running <code>qmake</code> before <code>make</code> will be solve this issue.

=== I'm trying to compile a Qt packcage for x86, but I got the error below. What's wrong? ===

In file included from maemo/gconfsymbols.cpp:41:
maemo/gconfsymbols_p.h:49:25: gconf/gconf.h: No such file or directory

Your scratchbox does not have <code>/bin/sh</code>, so when calling <code>pkg-config</code> from <code>qmake</code>, <code>CFLAGS</code> and <code>LIBS</code> are not set correctly. Running <code>ln -s /scratchbox/tools/bin/sh /bin/sh</code> will be solve this issue.

=== I'm trying to compile a diablo Qt package, so I just created a symbolic link, debian, for debian.diablo, and then run dpkg-buildpackage command, but I got a build error because the symbolic link was deleted. ===

When running dpkg-buildpackage, all symbolic links will be deleted, so need to rename the folder from debian.diablo to debian to make a build of diablo Qt package.

=== I installed Qt (libqt4-dev) to scratchbox and tried to build a sample application, but I got the error because some header files such as qhildonstyle.h, and qvfbhdr.h etc. were missing. ===

libqt4-dev should copy all header files, but now, at least in 4.5.2-1maemo1, some files are missing. Please download file below and extract to your scratchbox system.

http://qt4.garage.maemo.org/patches/qt4-missing-header.tgz

===Installing Qt on N900===
If you have already a fremantle device then you can install new Qt packages from extras-devel.
The step to follow are:
* Free space
* echo "deb http://repository.maemo.org/extras-devel/ fremantle free non-free
" >> /etc/apt/sources.list.d/hildon-application-manager.list
* apt-get install libqt4-gui
The basic packages will be so installed.

Current known issues:
* libqt4-opengl depends by libgles2, but it is not installable anymore.Has it been replaced with libgles2-sgx-img?

===Where are the Hildon Widgets for Qt===
Short answer : they've not been written.... yet.

Qt allows you to create your own widgets very easily. However, in order to provide as consistent an appearance as possible for the Maemo platform the community will be creating a set of [[/Qt Hildon Widgets|Qt Hildon Widgets]]

===Is it yet possible to create Fremantle desktop widgets using Qt?===
Yes you can write Fremantle desktop widgets using Qt. But unfortunately you can't load them with the widget manager since hildon widgets are GTK shared object file.

A simple desktop widget is in Extras-devel; Browse your application manager and look for qt-example-hildondesktopwidget.

== How to minimize a Qt application? ==
QDBusConnection c = QDBusConnection::sessionBus();
QDBusMessage m = QDBusMessage::createSignal("/","com.nokia.hildon_desktop","exit_app_view");
c.send(m);

== References ==

<references/>

[[Category:Development]]
[[Category:Qt]]

Qt4 Hildon/Qt Hildon Widgets

2009-10-14T20:10:22Z

82.181.173.103:

Qt for Hildon won't provide a set of composite widgets similar to those provided in Gtk Hildon. They will be part of an extra library.

This page is intended to link to resources to help the community develop these widgets.

Note that they will not be part of Qt as such, but will be optional widgets to aid developing applications for Maemo.

For details about Maemo 5 user experience, see:
* [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]
* [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification]
* [http://www.forum.nokia.com/info/sw.nokia.com/id/e778ba1f-2507-4672-be45-798359a3aea7/Fremantle_Master_Layout_Guide.html Fremantle Master Layout Guide]

* [http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines Maemo 5 Human Interface Guidelines]
* [http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Graphical_UI_Tutorial Maemo 5 Graphical UI Tutorial]

Following existing Qt Widgets have issues with Maemo 5 theming/Maemo 5 UI Style:
* Toolbar does not have correct height [Toolbar sizeHint is 48px] => Visual height should be 70px in Maemo 5.
* Toolbar icons do not have correct size (HILDON_ICON_SIZE_FINGER)
* <s>Dialogs do not have finger size buttons (HILDON_SIZE_FINGER_HEIGHT)</s>
* <s>Dialogs do not theme dialog buttons as such (different theme from normal buttons)</s>
* Dialogs have type icons (e.g. warning) where has in Maemo 5 use of those icons is not allowed.
* <s>Dialog buttons should stack on top of each other, but currently they layout themselves horizontally</s>
* Checkboxes should be embedded into button => Checkboxbutton. [Checkable QPushButton have to be themed or this will be part of an extra lib]
* <s>keyboard accelerator hints (underscores) are being shown, while Maemo 5 UI Style requires them to be hidden</s>
* <s>Stock dialogs use button strings such as "OK" and "Cancel", which are forbidden in Maemo 5 UI Style. "OK" should be replaced with an action string or with "Done".<s> The "Cancel" should be removed, as dialogs are cancelled by tapping outside of the dialog.</s>
* stock "Exit" command should be removed from the menus. It is not allowed in Maemo 5 UI Style. [Legacy menus should not be used]
* <s>Sliders/Scales</s>
* <s>Button heights? [minimal pushbutton height sizeHints is set by the style to 65px]</s>
* <s>Text input fields</s> [Style is okay]
* text areas(?)

Following important Hildon widgets need the respective Qt Hildon widget (in priority order):
* <s>Sub views ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Windows description]) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-stackable-window.h;hb=HEAD HildonStackableWindow] ([http://qt.gitorious.org/+qt-maemo-developers/qt/qt-maemo/commits/patch-hildon.stacked.windows-fremantle])</s>
* <s>view menu ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/View_Menu description], filter buttons) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-app-menu.h;hb=HEAD HildonAppMenu] (NOTE: this is not at all same widget as the legacy application menu in Gtk or Maemo 4) </s>
* Edit mode toolbar ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls#Edit_Toolbar description]) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-edit-toolbar.h;hb=HEAD HildonEditToolbar] [This could be part of our Qt Hildon Extra lib]
* Action buttons for pannable lists ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Porting_Software/Redesigning_From_Maemo_4_to_Maemo_5#Accounts_view example]) - [https://stage.maemo.org/viewcvs.cgi/projects/haf/trunk/gtk%2B/gtk/gtktreeview.h?root=maemo&view=markup hildon_tree_view_get_action_area_box etc. in Maemo GtkTreeview][will be part of the extra Qt lib or you can use a QPushButton and load the "+" icon by yourself]
* Picker buttons ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls#Picker_Button description], see also HildonTouchSelector) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-picker-button.h;hb=HEAD HildonPickerButton][will be part of the extra Qt lib]
* list selectors ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls#Touch_Selectors description], single column, multi column, single selection, multiselection, picker with entry, with images) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-touch-selector.h;hb=HEAD HildonTouchSelector][will be part of the extra Qt lib]
* Date picker ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls#Date_Button description], including column re-layout based on locale data) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-date-button.h;hb=HEAD HildonDateButton][will be part of the extra Qt lib]
* Time picker ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls#Time_Button description], including AM/PM support based on user setting) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-time-button.h;hb=HEAD HildonTimeButton][will be part of the extra Qt lib]
* <s>hildon banner</s> [part of the extra lib http://gitorious.org/qt-maemo/qmaemo-ext-libs/commit/f05642e2faa8a0bdef1f7d6f0cc004e825abba8a]
* hildon confirmation note
* <s>hildon dialog (with buttons on the bottom right side in landscape)</s>
* <s>hildon entry (including the possibility for placeholder text)</s>

Following QT toolkit widgets are not optimized for mobile ui, and consequently are not finger usable on high DPI touchscreens like Nokia N900.
* <s>QColorDialog</s> [Qt dialog has been modified in order to be usable with fingers]
* <s>QFontDialog</s> [Qt dialog has been modified in order to be usable with fingers]
* ...

These links may be of use:
* Discussion thread starting [http://www.mail-archive.com/maemo-developers@maemo.org/msg20237.html about here]
* http://maemomm.garage.maemo.org/docs/tutorial/figures/
* https://bugs.maemo.org/show_bug.cgi?id=4625
* https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=summary
* [[Using Fremantle Widgets]] and the [[Talk:Using Fremantle Widgets|talk]] page

Qt4 Hildon Legacy

2009-10-04T21:31:43Z

82.181.173.103: /* Building Qt from GIT rep */

[[Image:MaemoQtPicture.png]]
<br><br>
== [[Image:Intro.png]] Intro ==

=== Maemo Platform ===

The Maemo Platform is the software stack for Nokia Internet Tablets, which includes the Maemo operating system and the Maemo SDK. The Maemo Platform is mostly based on open source code, and has been developed by the Maemo Software department within Nokia in collaboration with many open source projects such as the Linux kernel, Debian, and GNOME.<ref>[http://en.wikipedia.org/wiki/Maemo_Platform Maemo Platform on Wikipedia]</ref>

[http://maemo.org/intro/platform/ Read more...]

=== What is Hildon? ===

Hildon is an application framework for Linux operating system mobile devices (PDAs, mobile phones, etc), developed by Nokia for Maemo and now a part of GNOME, that focuses on providing a finger friendly interface.<ref>[http://en.wikipedia.org/wiki/Hildon Hildon on Wikipedia]</ref>

[http://live.gnome.org/Hildon Read more...]

=== Developing on Maemo ===

Developing applications for Maemo is done with the Maemo SDK. The process from creating the first prototype of your application to distributing to a wide audience consists basically of three steps:

* Share your application project in the [http://garage.maemo.org Garage].
* Make your application easy to install and put in the [[Extras]].
* Once your application has a high quality - be promoted to the [http://www.nokia.com/os2008 Nokia user site].

[http://maemo.org/intro/developer_overview/ Read more...]

=== Maemo SDK ===

The Maemo SDK is based around the Debian-oriented Scratchbox Cross Compilation Toolkit, which provides a sandbox environment in which development may take place. Scratchbox uses Qemu to emulate an ARMEL processor or sbrsh to remotely execute instructions. Scratchbox-compatible rootstraps are available for both x86 and ARMEL, so the majority of development and debugging takes place on x86, with final packaging being for ARMEL.<ref>[http://en.wikipedia.org/wiki/Maemo_Platform#Maemo_SDK Maemo SDK on Wikipedia]</ref>

[http://www.youtube.com/watch?v=c8myh_iBy8k Watch the Maemo SDK in action!]

=== What is Scratchbox? ===

Scratchbox is a cross compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross compile an entire Linux distribution.<ref>[http://en.wikipedia.org/wiki/Scratchbox Scratchbox on Wikipedia]</ref>

[http://www.scratchbox.org/ Read more...]

<br>

== [[Image:Rocket.png]] Getting started ==

To start to develop with Maemo Qt, we need to install the Maemo SDK on a Linux machine.

=== Hey, I don't have a Linux machine! ===

That's not a big problem. [http://maemovmware.garage.maemo.org/ Maemo SDK Virtual Image project] provides a virtual development image for the Maemo platform that can be used with [http://www.vmware.com/products/player/ VMPlayer].

=== Installing the Maemo SDK ===

See the [http://maemo.org/development/sdks/ SDK documentation] for details on installing the SDK.

If you are on a non-debian system such as openSUSE you might need to perform the following command
in another shell prior to logging in in order to get ARM CPU emulation working:

sudo /scratchbox/sbin/sbox_ctl start

=== Installing the Qt packages in Scratchbox ===

After Scratchbox and the SDK are installed and working, you need to login, add the [[Extras]] and [[Extras#Extras-devel|Extras-devel]] repositories to your apt-get sources and install the Qt libs. Paste this into your Scratchbox shell (without the ">" prompt):

==== Diablo ====
> echo "# Maemo extras and extras-devel
deb http://repository.maemo.org/extras/ diablo free non-free
deb-src http://repository.maemo.org/extras/ diablo free
deb http://repository.maemo.org/extras-devel/ diablo free non-free
deb-src http://repository.maemo.org/extras-devel/ diablo free" > /etc/apt/sources.list.d/qt.list

==== Fremantle ====
> echo "# Maemo extras and extras-devel
deb http://repository.maemo.org/extras/ fremantle free non-free
deb-src http://repository.maemo.org/extras/ fremantle free
deb http://repository.maemo.org/extras-devel/ fremantle free non-free
deb-src http://repository.maemo.org/extras-devel/ fremantle free" > /etc/apt/sources.list.d/qt.list

Then run these commands to update the catalog and install Qt libraries:

> apt-get update
> fakeroot apt-get install libqt4-gui libqt4-dev

Do these steps for each of the DIABLO_X86, FREMANTLE_X86, DIABLO_ARMEL, FREMANTLE_ARMEL targets that you plan to build on.

===How to compile a Qt application in scratchbox===

All the Qt tools you need are available in scratchbox. In order to compile a Qt application you need to follow the
standard Qt way:

qmake -project
qmake file.pro
make

===Running a Qt application in scratchbox===
You can run a Qt application in both the target supported by scratchbox (ARMEL, X86).
However using the X86 target is recommended.

Before running the application you have to start Xephyr outside Scratchbox with the following parameters:
$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite

In the Scratchbox environment the DISPLAY variable has to be set so that it matches the display setting given above for the Xephyr server (parameter :2 in the above example).

[sbox-DIABLO_<target>:~] > export DISPLAY=:2

After the Xephyr server is running on the Linux host, you can start the Hildon Application Framework with the following command:

[sbox-DIABLO_<target>:~] > af-sb-init.sh start

This should start the Hildon Application Framework inside the Xephyr window.

Now we are ready to run an application in scratchbox:

[sbox-DIABLO_<target>:~] > run-standalone.sh ./qtapps

===Running a Qt application on the device===

To run a Qt application into the device, we need to copy it there.

====Installing OpenSSH server on the device====

To install and run applications on the device, we'll need to install an [[SSH]] server.

* Open the Application Manager.
* Make sure [[Extras]] is enabled.
* Install openssh-server from the list.

====Setting up a network connection====

We can connect to device to our working machine via WLAN or USB. Connecting the device to a WLAN is quite easy, but [[USB networking]] is more difficult to set up.

====Using scp to copy the excutable on the device====

[http://en.wikipedia.org/wiki/Secure_copy scp] or secure copy is a common Linux application. It can copy files or a directories over a secure connection. To copy our application on the device we just need to run it with a syntax like this:

PC_$> scp qtApplication root@DEVICE-IP:/home/user

====Executing the application====

Now that the application has been copied onto the device, we can run it. For that we need to open the terminal or we can use ssh from our PC.

PC_$> ssh root@DEVICE-IP
N810_#> su - user
N810_$> ./qtApplication

<br>
<br>

== [[Image:Hammer.png]] Porting a Qt application to Maemo ==

===Intro===

Porting a Qt desktop application to Maemo requires very little effort. This because the Maemo Qt libraries will take care of giving the Hildon look & Feel and enabling the virtual input methods for your application.

===Overriding the Qt Maemo changes===

====Maemo Style====

The Maemo style is the default style of Qt applications on Maemo. The other styles available in Qt 4.4 Maemo are [http://doc.trolltech.com/4.4/gallery-cleanlooks.html QCleanLooks], [http://doc.trolltech.com/4.4/gallery-windows.html Windows] and [http://doc.trolltech.com/4.4/gallery-plastique.html Plastique] (It will be available in the next release of Qt).

You can force your application to use another style in several ways:

* Running your application with the flag -style <style_name>
<small>''HINT: You can put this flag in the Exec field of the desktop file that launch the application.''</small>

$> ./qt-test-application -style windows

* If you want to change your code, you can use this static function:[http://doc.trolltech.com/4.4/qapplication.html#setStyle QApplication::setStyle( QStyle * style )]

* If you want to change the style only for a particular widget, you can call this function in the widget constructor: [http://doc.trolltech.com/4.4/qwidget.html#setStyle QWidget::setStyle( QStyle * style )]

====Showing the status bar====

Hildon applications don't have a status bar. Qt for Maemo hides the status bar by default.
You can show it again by modifying your code.

TODO

====Using the Kinetic Finger Scrolling (cf Gtk's PannableArea)====
See [[Qt/Finger Scrolling|Finger Scrolling]]

===Adding Maemo changes to a Qt Application===

Some methods of Qt for Maemo are not available in the "standard" Qt libs, so a Qt application with specific Maemo Qt code can't be built outside the Maemo SDK. To avoid this issue, the developer can use the preprocessor directives, for example:

#ifdef Q_WS_HILDON
//Specific hildon code here
#endif

===Limitations===

Currently Qt Maemo lacks full support for Hildon widgets introduced in Maemo 5.

'''At the moment, creating a Qt application that follows Maemo 5 UI Style requires using custom Qt widgets, coded within the application itself'''.

There is work ongoing to provide Qt Hildon widgets for Maemo 5, see [http://wiki.maemo.org/Qt4_Hildon/Qt_Hildon_Widgets Qt Hildon Widgets]

To get the benefits of the ongoing Maemo 5 hildon integration work in Qt, you must get the latest Qt source code and compile it yourself. See [http://wiki.maemo.org/Qt4_Hildon#Building_Qt_from_GIT_rep Building Qt from GIT repository].

<br>
<br>

== [[Image:Bug.png]] Debugging a Qt application ==

===GDB ===

====Intro ====

The GNU Project Debugger, or gdb for short, is a general purpose debugger that can be used for various debugging purposes.

====Debugging a Qt application in Scratchbox====

TODO

====Debugging a Qt application on device====

<ol>
<li>Installing gdb on the device.<ol>
<li>Add the [http://maemo.org/development/tools/ SDK tools] repository to the catalogue list.</li>
<li>install gdb by using apt-get (require around 6 MB of space)</li>
</ol></li>
<li>Install the debug symbols files in scratchbox (ARMEL target)</li>
apt-get install libqt4-dbg
<li>Run the application (device side)</li>
$gdbserver 0.0.0.0:1234 ./qtApplication
<li>Run the gdb client on your host PC (scratchbox side)</li>
[sbox-DIABLO_ARMEL: ~/TEST/svn/qt4-x11-4.4.0/examples/widgets/tablet] > gdb ./qtApplication
<li>Set the target of gdb</li>
(gdb) target remote 172.21.37.117:1234
<li>Tell to gdb to continue to debug the application on the device</li>
(gdb) continue
<li>Wait some moments...</li>
<li>Your application will appear on the device screen. Happy debugging!</li></ol>

===Links===

* [http://www.gnu.org/software/gdb/documentation/ GDB documentation & tutorials]
* [http://maemo.org/development/documentation/man_pages/gdbserver/ GDBServer man page]
* [http://maemo.org/maemo_release_documentation/maemo4.1.x/node15.html Maemo debugging guide]
* [http://repository.maemo.org/pool/diablo/free/g/gdb/ gdb debian package for Diablo]

<br><br>
== [[Image:chart.png]] Profiling a Qt application ==

=== OProfile ===

OProfile is a low overhead system-wide profiler for Linux. It can be used to find CPU usage bottlenecks in the whole system and within processes. It works fine in the device, but viewing the reports can take quite a long time (10 minutes) when fired up on N800/N810 devices. Therefore, it often makes sense to run opreport in scratchbox.

If you want to know more about OProfile in Maemo see the [http://maemo.org/development/tools/doc/chinook/oprofile/ documentation].

=== Valgrind ===

TODO

<br><br>

== [[Image:chart.png]] Qt benchmarks ==
2D graphic benchmark tools:

* [http://wiki.maemo.org/Qt/Benchmark/qgear QGears]
3D graphic benchmark tools:

* TODO
<br><br><br>

== [[Image:package.png]] Packaging a Qt application for Maemo ==

{{main|Packaging a Qt application}}

<br><br>
== [[Image:Helmet.png]] Maemo Qt API Reference ==

Maemo Qt is based on Qt for X11. It shares the same API avoiding API breaks. In this way every Qt application that runs in other platforms (Windows, Mac OS X, Linux, S60, etc.) can run also into the Maemo devices. To Develop a Qt application you can use the [http://doc.trolltech.com/4.5/index.html Official Qt 4.5 API documentation] and the list below to see what are the Maemo changes.

'''QString QDesktopServices::storageLocation(StandardLocation type)''' returns specific Maemo locations for these types:
- DesktopLocation: QDir::homePath() + QLatin1String("/MyDocs"), instead of QDir::homePath() + QLatin1String("/Desktop")
- DocumentsLocation: QDir::homePath() + QLatin1String("/MyDocs/.documents"), instead of QDir::homePath() + QLatin1String("/MyDocs/.documents")
- PicturesLocation: QDir::homePath() + QLatin1String("/MyDocs/.images"), instead of QDir::homePath() + QLatin1String("/Pictures")
- MusicLocation: QDir::homePath() + QLatin1String("/MyDocs/.sounds"), instead of QDir::homePath() + QLatin1String("/Music")
- MoviesLocation: QDir::homePath() + QLatin1String("/MyDocs/.videos"), instead of QDir::homePath() + QLatin1String("/MyDocs/.videos")

'''QTabletEvents''' are able to get the pressure value from the touchscreen.
- The eventdeviceType is for the touchscreen is set to QTabletEvent::Stylus.
- QTabletEvents won't be used anymore in Fremantle

'''Finger poke''' is emulated in scratchbox by the Middle Mouse button (NOTE: There is no Fullscreen VKB in scratchbox)

'''QInputEvents''' don't move the cursor.
It's mandatory to get working the HIM moving the cursor via QInputMethodEvents.
Why is it mandatory?
Because if the user select text with the finger from the right to the left, we are able to remove the highlighted text, but the
cursor will be moved on the last char instead to stay on the first one.

To do that some changes has been added to some widget function like: ''widget::inputMethodEvent(QInputMethodEvent *e)''.
Modifing that function in some custom widgets may be necessary.
Don't reimplementing that function will break some fullscreen virtual keyboard features.

'''Hardcoded Keys:'''
In the QMainWindow:
- F6 - Toggle fullscreen the application
- F4 - Shows/Hides the application context menu
- Zoom in - is a standard [http://doc.trolltech.com/4.4/qkeysequence.html#StandardKey-enum key sequence] QKeySequence::ZoomIn
- Zoom out - is a standard [http://doc.trolltech.com/4.4/qkeysequence.html#StandardKey-enum key sequence] QKeySequence::ZoomOut

'''Input Method:'''
Maemo Qt uses the Hildon IM as default Input method.
Each kind of widget can set the IM mode. This allows the input method to focus on the type of input that the application is expecting.
Eg: spinboxes can receive only numeric characters (1-9).

NOTE: Qt widgets like QTextEdit, QLineEdit... set the right input method mode automatically.

A developer can change it by using:
void QInputContext::setInputMode(int mode);
It will update immediately the Hildon Input method to use the selected IM mode.

HIC Modes:
HILDON_GTK_INPUT_MODE_ALPHA alphabetical characters and whitespace
HILDON_GTK_INPUT_MODE_NUMERIC numbers 0-9 and the '-' character
HILDON_GTK_INPUT_MODE_SPECIAL special characters
HILDON_GTK_INPUT_MODE_HEXA hexadecimal characters; numbers 0-9, characters a-f, and A-F
HILDON_GTK_INPUT_MODE_TELE telephone numbers; numbers 0-9, whitespace, and the characters "pwPW/().-+*#?,"
HILDON_GTK_INPUT_MODE_FULL unrestricted entry mode, combination of the alpha, numeric and special modes.
HILDON_GTK_INPUT_MODE_MULTILINE the client contains multiple lines of text or accepts linebreaks in the input.
HILDON_GTK_INPUT_MODE_INVISIBLE do not echo or save the input in the IM when entering sensitive information such as passwords.
HILDON_GTK_INPUT_MODE_AUTOCAP automatically capitalize the first letter at the start of a sentence.
HILDON_GTK_INPUT_MODE_DICTIONARY enable predictive dictionaries and learning based on the input.

Example:
For a password field we need to set a specific IM mode:
int mode = HILDON_GTK_INPUT_MODE_FULL | HILDON_GTK_INPUT_MODE_INVISIBLE
QInputContext qic = widget->inputContext();
qic->setInputMode(mode);

If you are developing a Custom widget able to receive input text, you can instruct your widget to use the right IM Mode just returning
the mode.

- How does it work?
The Hildon IM sends a XMessage to pop up the "Virtual Keyboard" (or better the Main HIM UI) when an input widget receive the focus.
The IM before to raise the VKB, makes an inputMethodQuery to the widget retrieving the IM mode.
If the developer of the custom widget doesn't set the mode property, the IM will use HILDON_GTK_INPUT_MODE_FULL (the default mode) for that widget.

Setting the ImMode is quite easy. Check the code below for more understanding.

#ifdef Q_WS_HILDON
#include <QInputContext>
#endif

QVariant QAbstractSpinBox::inputMethodQuery(Qt::InputMethodQuery query) const
{
Q_D(const QAbstractSpinBox);
switch(query) {
case Qt::ImMode:{
int mode = HILDON_GTK_INPUT_MODE_NUMERIC;
return QVariant(mode);
}
default:
return d->edit->inputMethodQuery(query);
}
}

'''QDialogs in fremantle.'''
The fremantle WM doesn't allow QDialogs without a parent (at least this is true for Qt apps).
A dialog without a parent won't be shown by the WM.

Eg:
This is what you MUST avoid.
QColorDialog::getColor ( Qt::white, 0 )

Remember to setup a parent
QColorDialog::getColor ( Qt::white, this )

'''QPrinter and QPrintDialog'''
Print support has been removed from Maemo Qt.
Application compiled with old libs are still binary compatible with the new libs but they crash when a removed component is called.

Nokia: /home/user# ./textedit
./textedit: symbol lookup error: ./textedit: undefined symbol: _ZN8QPrinterC1ENS_11PrinterModeE

'''System tray support'''
System tray is not available anymore in Fremantle. That support has been removed from Qt too.
Hence QSystemTrayIcon class is not available anymore.

<br><br>

== [[Image:Helmet.png]] Contributing to the Maemo Qt Project ==

Maemo Qt is a community project. Contributing to the forum, sending us patches, give us feedbacks, tracking bugs are all activities that help us to improve the quality of our work.

Here there is a list of things that every person interested in helping us should read.

===Be updated===
Any Maemo Qt developer should be updated and should participate to the discussions, for that he must join the Mailing list.
BTW the mailing list is not for Maemo Qt Developers but it's open to Maemo Qt application developers too.

=== Introduction to Git ===
If you are a git newbie you maybe find interesting these links:
* http://www.sourcemage.org/Git_Guide
* http://www.gitcasts.com/
* http://www.gnome.org/~newren/eg/git-for-svn-users.html
* Using the git protocol through a HTTP CONNECT proxy: http://www.emilsit.net/blog/archives/how-to-use-the-git-protocol-through-a-http-connect-proxy/

===Understanding the structure of our Git repository===
These info are here:[[Qt Maemo Git Process]].

=== Preparation ===
Make sure each scratchbox target has

fakeroot apt-get build-dep libqt4-gui

(you may need to apt-get install libgl-dev too as it's not in the Build-Depends: yet)

===Building Qt from GIT rep===

* Clone the repository:
git clone git://gitorious.org/+qt-maemo-developers/qt/qt-maemo.git
or if you are a member of our team:
git clone git@gitorious.org:+qt-maemo-developers/qt/qt-maemo.git

* Change dir
cd qt-maemo

* Copy the remote 4.5 branch in your workingcopy
git checkout -b 4.5 origin/4.5

* Checkout ONE of these branches:
git checkout -b qt-diablo origin/qt-diablo
git checkout -b qt-n900 origin/qt-n900
git checkout -b qt-mer origin/qt-mer

* Build the packages:
dpkg-buildpackage -rfakeroot -b

===Checking out all the remote branches===
* Clone the repository:
git clone git://gitorious.org/+qt-maemo-developers/qt/qt-maemo.git
or if you are a member of our team:
git clone git@gitorious.org:+qt-maemo-developers/qt/qt-maemo.git

* Change dir
cd qt-maemo

* Check out our script branch
git checkout -b maemo-qt-scripts origin/maemo-qt-scripts

* Save a copy of the script outside the working directories
cp maemo-qt-scripts/copy-all-remote-branches-locally/copy.sh ../

* Launch the copy.sh script
../copy.sh

===Commit changes in SVN [OLD]===

If you are a Maemo Qt developer and you want to save your changes in the Garage SVN but your project is not ready to go to the main line (trunk/qt-x11), you should create a private branch and then work there until the merging with the mainline.

For that you have to create a your directory in branches/ named ''developer_name-qt''. After that you can copy trunk/qt-x11 in your directory.
svn copy --username developer_name https://garage.maemo.org/svn/qt4/trunk/qt-x11 https://garage.maemo.org/svn/qt4/branches/developer_name-qt -m "Creating private branch of trunk/qt-x11"

NOTE: Subversion uses cheap copy, so them don't increase the size of the repository. Then feel free to create your own branch.

===Merging branches changes in the mainline [OLD]===

Before to merge your changes in the mainline, the code must be full working, cleaned and tested. A review from another developer is also needed in order to reduce the possibility to add errors.
<br><br>

==[[Image:Help-contents.png]] F.A.Q.==

=== I'm trying to compile a Qt application for ARMEL, but I got the error below. What's wrong? ===

/targets/FREMANTLE_X86/usr/include/qt4/QtCore/qatomic_i386.h:127: error: impossible constraint in 'asm'

You are using x86 include files, then you have to update your Makefile. Running <code>qmake</code> before <code>make</code> will be solve this issue.

=== I'm trying to compile a Qt packcage for x86, but I got the error below. What's wrong? ===

In file included from maemo/gconfsymbols.cpp:41:
maemo/gconfsymbols_p.h:49:25: gconf/gconf.h: No such file or directory

Your scratchbox does not have <code>/bin/sh</code>, so when calling <code>pkg-config</code> from <code>qmake</code>, <code>CFLAGS</code> and <code>LIBS</code> are not set correctly. Running <code>ln -s /scratchbox/tools/bin/sh /bin/sh</code> will be solve this issue.

=== I'm trying to compile a diablo Qt package, so I just created a symbolic link, debian, for debian.diablo, and then run dpkg-buildpackage command, but I got a build error because the symbolic link was deleted. ===

When running dpkg-buildpackage, all symbolic links will be deleted, so need to rename the folder from debian.diablo to debian to make a build of diablo Qt package.

=== I installed Qt (libqt4-dev) to scratchbox and tried to build a sample application, but I got the error because some header files such as qhildonstyle.h, and qvfbhdr.h etc. were missing. ===

libqt4-dev should copy all header files, but now, at least in 4.5.2-1maemo1, some files are missing. Please download file below and extract to your scratchbox system.

http://qt4.garage.maemo.org/patches/qt4-missing-header.tgz

===Installing Qt on N900===
If you have already a fremantle device then you can install new Qt packages from extras-devel.
The step to follow are:
* Free space
* echo "deb http://repository.maemo.org/extras-devel/ fremantle free non-free
" >> /etc/apt/sources.list.d/hildon-application-manager.list
* apt-get install libqt4-gui
The basic packages will be so installed.

Current known issues:
* libqt4-opengl depends by libgles2, but it is not installable anymore.Has it been replaced with libgles2-sgx-img?

===Where are the Hildon Widgets for Qt===
Short answer : they've not been written.... yet.

Qt allows you to create your own widgets very easily. However, in order to provide as consistent an appearance as possible for the Maemo platform the community will be creating a set of [[/Qt Hildon Widgets|Qt Hildon Widgets]]

===Is it yet possible to create Fremantle desktop widgets using Qt?===
Since desktop applet are libraries (.so files) then it's not so simple making Qt desktop applet.

At moment I didn't investigate for a solution.. but it's possible (I tried it) to put Qt Widgets into the desktop just changing the Window Type of the widget (eg a QDialog) with the right Window Type.

Then a Qt application can put widgets in the hildon-desktop but the "applet manager" that loads the desktop widgets doesn't recognize them as applet, then it doesn't manage Qt home applets.

== References ==

<references/>

[[Category:Development]]
[[Category:Qt]]

Qt4 Hildon/Qt Hildon Widgets

2009-10-04T15:30:29Z

82.181.173.103:

Qt for Hildon won't provide a set of composite widgets similar to those provided in Gtk Hildon. They will be part of an extra library.

This page is intended to link to resources to help the community develop these widgets.

Note that they will not be part of Qt as such, but will be optional widgets to aid developing applications for Maemo.

For details about Maemo 5 user experience, see:
* [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]
* [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification]
* [http://www.forum.nokia.com/info/sw.nokia.com/id/e778ba1f-2507-4672-be45-798359a3aea7/Fremantle_Master_Layout_Guide.html Fremantle Master Layout Guide]

* [http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines Maemo 5 Human Interface Guidelines]
* [http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Graphical_UI_Tutorial Maemo 5 Graphical UI Tutorial]

Following existing Qt Widgets have issues with Maemo 5 theming/Maemo 5 UI Style:
* Toolbar does not have correct height [Toolbar sizeHint is 48px] => Visual height should be 70px in Maemo 5.
* Toolbar icons do not have correct size (HILDON_ICON_SIZE_FINGER)
* <s>Dialogs do not have finger size buttons (HILDON_SIZE_FINGER_HEIGHT)</s>
* Dialogs do not theme dialog buttons as such (different theme from normal buttons)
* Dialogs have type icons (e.g. warning) where has in Maemo 5 use of those icons is not allowed.
* <s>Dialog buttons should stack on top of each other, but currently they layout themselves horizontally</s>
* Checkboxes should be embedded into button => Checkboxbutton. [Checkable QPushButton have to be themed or this will be part of an extra lib]
* <s>keyboard accelerator hints (underscores) are being shown, while Maemo 5 UI Style requires them to be hidden</s>
* <s>Stock dialogs use button strings such as "OK" and "Cancel", which are forbidden in Maemo 5 UI Style. "OK" should be replaced with an action string or with "Done".<s> The "Cancel" should be removed, as dialogs are cancelled by tapping outside of the dialog.</s>
* stock "Exit" command should be removed from the menus. It is not allowed in Maemo 5 UI Style. [Legacy menus should not be used]
* <s>Sliders/Scales</s>
* <s>Button heights? [minimal pushbutton height sizeHints is set by the style to 65px]</s>
* <s>Text input fields</s> [Style is okay]
* text areas(?)

Following important Hildon widgets need the respective Qt Hildon widget (in priority order):
* <s>Sub views ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Windows description]) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-stackable-window.h;hb=HEAD HildonStackableWindow] ([http://qt.gitorious.org/+qt-maemo-developers/qt/qt-maemo/commits/patch-hildon.stacked.windows-fremantle])</s>
* <s>view menu ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/View_Menu description], filter buttons) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-app-menu.h;hb=HEAD HildonAppMenu] (NOTE: this is not at all same widget as the legacy application menu in Gtk or Maemo 4) </s>
* Edit mode toolbar ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls#Edit_Toolbar description]) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-edit-toolbar.h;hb=HEAD HildonEditToolbar] [This could be part of our Qt Hildon Extra lib]
* Action buttons for pannable lists ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Porting_Software/Redesigning_From_Maemo_4_to_Maemo_5#Accounts_view example]) - [https://stage.maemo.org/viewcvs.cgi/projects/haf/trunk/gtk%2B/gtk/gtktreeview.h?root=maemo&view=markup hildon_tree_view_get_action_area_box etc. in Maemo GtkTreeview][will be part of the extra Qt lib or you can use a QPushButton and load the "+" icon by yourself]
* Picker buttons ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls#Picker_Button description], see also HildonTouchSelector) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-picker-button.h;hb=HEAD HildonPickerButton][will be part of the extra Qt lib]
* list selectors ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls#Touch_Selectors description], single column, multi column, single selection, multiselection, picker with entry, with images) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-touch-selector.h;hb=HEAD HildonTouchSelector][will be part of the extra Qt lib]
* Date picker ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls#Date_Button description], including column re-layout based on locale data) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-date-button.h;hb=HEAD HildonDateButton][will be part of the extra Qt lib]
* Time picker ([http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls#Time_Button description], including AM/PM support based on user setting) - [https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-time-button.h;hb=HEAD HildonTimeButton][will be part of the extra Qt lib]
* <s>hildon banner</s> [part of the extra lib http://gitorious.org/qt-maemo/qmaemo-ext-libs/commit/f05642e2faa8a0bdef1f7d6f0cc004e825abba8a]
* hildon confirmation note
* <s>hildon dialog (with buttons on the bottom right side in landscape)</s>
* <s>hildon entry (including the possibility for placeholder text)</s>

Following QT toolkit widgets are not optimized for mobile ui, and consequently are not finger usable on high DPI touchscreens like Nokia N900.
* <s>QColorDialog</s> [Qt dialog has been modified in order to be usable with fingers]
* <s>QFontDialog</s> [Qt dialog has been modified in order to be usable with fingers]
* ...

These links may be of use:
* Discussion thread starting [http://www.mail-archive.com/maemo-developers@maemo.org/msg20237.html about here]
* http://maemomm.garage.maemo.org/docs_unstable/tutorial/figures/
* https://bugs.maemo.org/show_bug.cgi?id=4625
* https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=summary
* [[Using Fremantle Widgets]] and the [[Talk:Using Fremantle Widgets|talk]] page