| Latest revision |
Your text |
| Line 1: |
Line 1: |
| - | == Introduction == | + | [[Image:MaemoQtPicture.png]] |
| | + | == [[Image:Intro.png]] Intro == |
| | | | |
| - | To develop with [[Qt-Maemo|Qt for Maemo]], a working SDK installation is required. There are [[Documentation/Maemo_5_Final_SDK_Installation|instructions on how to install the Maemo SDK]], and you can [http://www.youtube.com/watch?v=c8myh_iBy8k watch the Maemo SDK in action]. Alternatively, you may want to try [[MADDE]], a cross-platform Maemo development tool, available as a technology preview.
| + | === Maemo Platform === |
| | | | |
| - | == 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> |
| | | | |
| - | 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, [[Hildon]] and GNOME.
| + | [http://maemo.org/intro/platform/ Read more...] |
| | | | |
| - | Read more about [http://maemo.org/intro/platform/ the Maemo platform] and a [http://maemo.org/intro/developer_overview/ developer overview].
| + | === What is Hildon? === |
| | | | |
| - | == Getting started ==
| + | 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> |
| | | | |
| - | To start to develop with Maemo Qt, we need to [[Documentation/Maemo_5_Final_SDK_Installation|install the Maemo SDK]].
| + | [http://live.gnome.org/Hildon Read more...] |
| | | | |
| - | === Installing Qt packages in Scratchbox === | + | === Developing on Maemo === |
| - | Maemo Qt developers offers a set of Qt packages for [[Open development/Maemo roadmap/Fremantle|Fremantle]] (Maemo5 - OS2009) and [[Open development/Maemo roadmap/Diablo|Diablo]] (Maemo4.1 - OS2008).
| + | |
| | | | |
| - | === Fremantle ===
| + | 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: |
| - | You do not need to add any extra repository for Fremantle since Qt packages are already available in the SDK. You can install Qt with the command:
| + | |
| - | fakeroot apt-get install libqt4-dev
| + | |
| | | | |
| - | ==== Using Qt 4.6 in Fremantle ====
| + | * 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]. |
| | | | |
| - | Since the [[Maemo 5/PR1.2|PR1.2]] release Qt 4.6 is available in public Fremantle repository. To upgrade older Scratchbox targets to use the latest packages execute the following commands:
| + | [http://maemo.org/intro/developer_overview/ Read more...] |
| - | fakeroot apt-get update
| + | |
| - | fakeroot apt-get dist-upgrade
| + | |
| | | | |
| - | === Diablo === | + | === Maemo SDK === |
| - | Diablo Qt packages are into the official [[Extras]] repository. In order to start to develop with those packages you need to [[Extras#Diablo|add extras repository to your repository list]], and then install Qt packages in the terminal:
| + | |
| - | apt-get install libqt4-dev
| + | |
| | | | |
| - | ==How to compile a Qt application in scratchbox==
| + | 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> |
| - | 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:
| + | [http://www.youtube.com/watch?v=c8myh_iBy8k Watch the Maemo SDK in action!] |
| - | # Generating project file (Required if there is no .pro file into the app source tree)<pre>qmake -project</pre>
| + | |
| - | # Generating Makefile from the QMake project file:<pre>qmake file.pro</pre>
| + | |
| - | # <pre>make</pre>
| + | |
| | | | |
| - | === CMake === | + | === What is Scratchbox? === |
| | | | |
| - | Because of some issue with [http://www.cmake.org/ CMake], [[Open development/Maemo roadmap/Diablo|Diablo]] CMake packages are currently useless since CMake segfaults (on the device at least). This issue has been solved in [[Open development/Maemo roadmap/Fremantle|Fremantle]] and CMake packages that comes from Fremantle SDK work nicely.
| + | 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> |
| | | | |
| - | CMake projects usually have a <code>CMakeLists.txt</code> file instead of:
| + | [http://www.scratchbox.org/ Read more...] |
| - | # .pro file used by QMake projects
| + | |
| - | # <code>Makefile.am</code> 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.
| + | == [[Image:Rocket.png]] Getting started == |
| - | cmake path
| + | |
| - | make
| + | |
| | | | |
| - | Note: CMake is not installed by default in [[:Category:Scratchbox|scratchbox]]. You can install it with the command:
| + | To start to develop with Maemo Qt, we need to install the Maemo SDK on a Linux machine. |
| - | fakeroot apt-get install cmake
| + | |
| | | | |
| - | == Running a Qt application in: == | + | === Hey, I don't have a Linux machine! === |
| - | === Scratchbox ===
| + | |
| - | Diablo and Fremantle Qt applications can run on the device as in Scratchbox.
| + | |
| | | | |
| - | First step to run a Qt application is starting the SDK UI:
| + | 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]. |
| - |
| + | |
| - | # Run Xephyr. It is able to run a [[:wikipedia:X_Window_System| X Server]] inside another X Server.<pre>Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb</pre>
| + | |
| - | # Set display for application that runs inside scratchbox:<pre>export DISPLAY=:2</pre>
| + | |
| - | # You can now run the SDK UI. A Diablo or Fremantle desktop will appear in your Xephyr window:<pre>af-sb-init.sh start</pre>
| + | |
| - | # Now you are ready to run any Maemo or Maemo Qt application with:<pre>run-standalone.sh ./qtapps</pre>
| + | |
| | | | |
| - | Note: <code>run-standalone.sh</code> sets some variable needed by Qt to use the Hildon style.
| + | === Installing the Maemo SDK === |
| | | | |
| - | === Device ===
| + | See the [http://maemo.org/development/sdks/ SDK documentation] for details on installing the SDK. |
| - | Maemo Qt applications are Linux binaries. They can run on the device without any problem if you copy them to "partitions" mounted with exec flag. (for example, <code>/home/user</code> or <code>/opt</code> in Fremantle).
| + | |
| | | | |
| - | Fore example, if we want to run quassel (Qt IRC Client) we have to launch it with:
| + | If you are on a non-debian system such as openSUSE you might need to perform the following command |
| - | su -c ./quassel user
| + | in another shell prior to logging in in order to get ARM CPU emulation working: |
| | | | |
| - | == Porting Qt applications to Maemo ==
| + | sudo /scratchbox/sbin/sbox_ctl start |
| | | | |
| - | Porting a Qt desktop application to Maemo requires very little effort. This is because the Maemo Qt libraries will take care of giving the Hildon look & Feel and enabling the virtual input methods for your application.
| + | === Installing the Qt packages in Scratchbox === |
| | | | |
| - | ===Overriding the Qt Maemo changes===
| + | 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): |
| | | | |
| - | ====Maemo Style====
| + | >> 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 |
| | | | |
| - | Hildon Style is the default Qt application style. Other style available are:
| + | Then run these commands to update the catalog: |
| - | * [http://doc.trolltech.com/4.5/gallery-cleanlooks.html QCleanLooks]
| + | |
| - | * [http://doc.trolltech.com/4.5/gallery-windows.html Windows]
| + | |
| - | * [http://doc.trolltech.com/4.5/gallery-plastique.html Plastique]
| + | |
| | | | |
| - | Qt application can use other Qt styles;
| + | >> apt-get update |
| - | * Running your application with the style flag:
| + | > fakeroot apt-get install libqt4-gui |
| - | ./qt-test-application -style windows | + | > fakeroot apt-get install libqt4-dev |
| | | | |
| - | * Using [http://doc.trolltech.com/4.5/qapplication.html#setStyle QApplication::setStyle( QStyle * style )]
| + | Do these steps for the DIABLO_X86 and the DIABLO_ARMEL target if you plan to build on both. |
| | | | |
| - | * If you want to change the style of a widget:[http://doc.trolltech.com/4.5/qwidget.html#setStyle QWidget::setStyle( QStyle * style )]
| + | ===How to compile a Qt application in scratchbox=== |
| | | | |
| - | ====Showing the status bar====
| + | 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: |
| | | | |
| - | Hildon applications don't have a status bar. Qt for Maemo hides the status bar by default.
| + | qmake -project |
| | + | qmake file.pro |
| | + | make |
| | | | |
| - | You can show it again by using method ''statusBar()->show()'' in your class derived from QMainWindow.
| + | ===Running a Qt application in scratchbox=== |
| | | | |
| - | ====Using the Kinetic Finger Scrolling (cf Gtk's PannableArea)====
| + | TODO |
| | | | |
| - | See [[Qt/Finger Scrolling|Finger Scrolling]]
| + | ===Running a Qt application on device=== |
| | | | |
| - | ===Adding Maemo changes to a Qt Application===
| + | To run a Qt application into the device, we need to copy it there. |
| | | | |
| - | 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 with Qt 4.5 on Diablo and Fremantle:
| + | ====Installing OpenSSH server on the device==== |
| | | | |
| - | <source lang="cpp-qt">
| + | To install and run applications on the device, we'll need to install an [[SSH]] server. |
| - | #ifdef Q_WS_HILDON
| + | |
| - | //Specific hildon/Maemo5 code here
| + | |
| - | #endif
| + | |
| - | </source>
| + | |
| | | | |
| - | Qt project files can load hildon files using: (check [http://doc.trolltech.com/4.5/qmake-function-reference.html qmake ref guide] for more info about qmake options)
| + | * Open the Application Manager. |
| - | contains(QT_CONFIG, hildon): {
| + | * Make sure [[Extras]] is enabled. |
| - | message("Hello Hildon")
| + | * Install openssh-server from the list. |
| - | SOURCE += hildon.cpp
| + | |
| - | HEADER += hildon.h
| + | |
| - | FORMS += hildon.ui
| + | |
| - | }
| + | |
| | | | |
| - | === Home widget interaction === | + | ====Setting up a network connection==== |
| | | | |
| - | {{main|Qt4 and Hildon home widget interaction}}
| + | 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. |
| | | | |
| - | ===Limitations=== | + | ====Using scp to copy the excutable on the device==== |
| | | | |
| - | Currently Qt Maemo lacks full support for Hildon widgets introduced in Maemo 5.
| + | [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: |
| | | | |
| - | '''At the moment, creating a Qt application that follows Maemo 5 UI Style requires using custom Qt widgets, coded within the application itself'''.
| + | PC_$> scp qtApplication root@DEVICE-IP:/home/user |
| | | | |
| - | There is work ongoing to provide Qt Hildon widgets for Maemo 5, see [[Qt4_Hildon/Qt_Hildon_Widgets|Qt Hildon Widgets]]
| + | ====Executing the application==== |
| | | | |
| - | 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 [[Qt4_Hildon#Building_Qt_from_GIT_rep|Building Qt from GIT repository]].
| + | 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. |
| | | | |
| - | == Debugging a Qt application ==
| + | PC_$> ssh root@DEVICE-IP |
| | + | N810_#> su - user |
| | + | N810_$> ./qtApplication |
| | | | |
| - | {{main|Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide}}
| + | == [[Image:Hammer.png]] Porting a Qt application in Maemo == |
| | | | |
| - | '''Note''': Fremantle Gdb 6.8 crashes in x86 and gives messed up backtraces on the device. Using gdb 7.0 is recommended. You can get gdb 7.0 sources from http://ftp.de.debian.org/debian/pool/main/g/gdb/gdb_7.0.orig.tar.gz, compile it (./configure && make) inside X86 and armel scratchbox targets.
| + | ===Intro=== |
| - | [http://chaos.troll.no/~harald/gdb7/ Here you can find GDB7 for fremantle x86 and armel].
| + | |
| - | /usr/local/bin/gdb7 ./myapp
| + | |
| | | | |
| - | == Profiling a Qt application ==
| + | 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. |
| | | | |
| - | === OProfile === | + | ===Overriding the Qt Maemo changes=== |
| | | | |
| - | {{main|Documentation/devtools/maemo5/oprofile}}
| + | ====Maemo Style==== |
| | | | |
| - | === Valgrind ===
| + | 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). |
| | | | |
| - | {{main|Documentation/devtools/maemo5/valgrind}}
| + | You can force your application to use another style in several ways: |
| | | | |
| - | == Packaging a Qt application for Maemo ==
| + | * 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> |
| | | | |
| - | {{main|Packaging a Qt application}}
| + | $> ./qt-test-application -style windows |
| | | | |
| - | == Maemo Qt API Reference ==
| + | * 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 )] |
| | | | |
| - | 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.
| + | * 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 )] |
| | | | |
| - | ===Diablo=== | + | ====Showing the status bar==== |
| | | | |
| - | '''QString QDesktopServices::storageLocation(StandardLocation type)''' returns specific Maemo locations for these types: | + | Hildon applications don't have a status bar. Qt for Maemo hides the status bar by default. |
| - | * DesktopLocation: QDir::homePath() + QLatin1String("/MyDocs"), instead of QDir::homePath() + QLatin1String("/Desktop")
| + | You can show it again by modifying your code. |
| - | * 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
| + | TODO |
| | | | |
| - | '''Finger poke''' is emulated in scratchbox by the Middle Mouse button (NOTE: There is no Fullscreen VKB in scratchbox)
| + | ===Adding Maemo changes to a Qt Application=== |
| | | | |
| - | '''QInputEvents''' don't move the cursor.
| + | 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: |
| - | 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:'''
| + | #ifdef Q_WS_HILDON |
| - | 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).
| + | //Specific hildon code here |
| | + | #endif |
| | | | |
| - | NOTE: Qt widgets like QTextEdit, QLineEdit... set the right input method mode automatically.
| + | ===Limitations=== |
| | | | |
| - | A developer can change it by using:
| + | TODO |
| - | <source lang="cpp-qt">
| + | |
| - | void QInputContext::setInputMode(int mode);
| + | |
| - | </source>
| + | |
| - | It will update immediately the Hildon Input method to use the selected IM mode.
| + | |
| | | | |
| - | HIC Modes:
| + | == [[Image:Bug.png]] Debugging a Qt application == |
| - | * <code>HILDON_GTK_INPUT_MODE_ALPHA</code> alphabetical characters and whitespace
| + | |
| - | * <code>HILDON_GTK_INPUT_MODE_NUMERIC</code> numbers 0-9 and the '-' character
| + | |
| - | * <code>HILDON_GTK_INPUT_MODE_SPECIAL</code> special characters
| + | |
| - | * <code>HILDON_GTK_INPUT_MODE_HEXA</code> hexadecimal characters; numbers 0-9, characters a-f, and A-F
| + | |
| - | * <code>HILDON_GTK_INPUT_MODE_TELE</code> telephone numbers; numbers 0-9, whitespace, and the characters "pwPW/().-+*#?,"
| + | |
| - | * <code>HILDON_GTK_INPUT_MODE_FULL</code> unrestricted entry mode, combination of the alpha, numeric and special modes.
| + | |
| - | * <code>HILDON_GTK_INPUT_MODE_MULTILINE</code> the client contains multiple lines of text or accepts linebreaks in the input.
| + | |
| - | * <code>HILDON_GTK_INPUT_MODE_INVISIBLE</code> do not echo or save the input in the IM when entering sensitive information such as passwords.
| + | |
| - | * <code>HILDON_GTK_INPUT_MODE_AUTOCAP</code> automatically capitalize the first letter at the start of a sentence.
| + | |
| - | * <code>HILDON_GTK_INPUT_MODE_DICTIONARY</code> enable predictive dictionaries and learning based on the input.
| + | |
| | | | |
| - | Example:
| + | ===GDB === |
| - | For a password field we need to set a specific IM mode:
| + | |
| - | <source lang="cpp-qt">
| + | |
| - | int mode = HILDON_GTK_INPUT_MODE_FULL | HILDON_GTK_INPUT_MODE_INVISIBLE
| + | |
| - | QInputContext *qic = widget->inputContext();
| + | |
| - | qic->setInputMode(mode);
| + | |
| - | </source>
| + | |
| - | 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 <code>HILDON_GTK_INPUT_MODE_FULL</code> (the default mode) for that widget.
| + | |
| | | | |
| - | Setting the ImMode is quite easy. Check the code below for more understanding.
| + | ====Intro ==== |
| - | <source lang="cpp-qt">
| + | |
| - | #ifdef Q_WS_HILDON
| + | |
| - | #include <QInputContext>
| + | |
| - | #endif
| + | |
| | | | |
| - | QVariant QAbstractSpinBox::inputMethodQuery(Qt::InputMethodQuery query) const
| + | The GNU Project Debugger, or gdb for short, is a general purpose debugger that can be used for various debugging purposes. |
| - | {
| + | |
| - | 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);
| + | |
| - | }
| + | |
| - | }
| + | |
| - | </source>
| + | |
| | | | |
| - | ==FREMANTLE (Qt 4.5)== | + | ====Debugging a Qt application in Scratchbox==== |
| | | | |
| - | ===Kinetic scrolling===
| + | TODO |
| | | | |
| - | Kinetic scrolling is enabled by default in QListWidgets and is supported by any Qt widget that inherits QScrollArea.
| + | ====Debugging a Qt application on device==== |
| - | Any item view widgets (QTreeView/QTreeWidget, QListView, QTableView/QTableWidget...) can use fingerscroll if it has "FingerScrollable" dynamic property set to true.
| + | |
| - | Eg:
| + | |
| - | <source lang="cpp-qt">
| + | |
| - | QTableWidget *table = new QTableWidget(this);
| + | |
| - | table->setProperty("FingerScrollable", true);
| + | |
| - | </source>
| + | |
| - | NOTE: Available in Qt > 4.5.3-xxxxx-maemo4
| + | |
| | | | |
| - | ===Hildon-Desktop widgets===
| + | <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> |
| | | | |
| - | {{main|Qt4 Hildon/Qt Hildon Widgets}}
| + | ===Links=== |
| | | | |
| - | They are supported by Qt. An example (qt-example-hildondesktopwidget) is available in extras-devel.
| + | * [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] |
| | | | |
| - | ===Hildon menus=== | + | == [[Image:chart.png]] Profiling a Qt application == |
| | | | |
| - | Maemo5 menus are created using QActions available in menu bar.
| + | === OProfile === |
| - | Hidden, disabled, separators and widget actions won't shown. (Same in Qt 4.6)
| + | |
| | | | |
| - | * qt-4.5.3-xxxx-maemo4 packages - needs QActions in a "fremantle" menu.
| + | 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. |
| - | * Pkgs > qt-4.5.3-xxxx-maemo4 shows Maemo5 menus automatically
| + | |
| | | | |
| - | Note: Maemo5 policy doesn't allow application to have more than 10 items.
| + | If you want to know more about OProfile in Maemo see the [http://maemo.org/development/tools/doc/chinook/oprofile/ documentation]. |
| | | | |
| - | ===Stackable windows=== | + | === Valgrind === |
| | | | |
| - | http://maemomm.garage.maemo.org/docs/tutorial/figures/stackable-window.png
| + | TODO |
| - | Are supported by Qt. To create them you need to create a MainWindow child of another Main window.
| + | |
| - | <source lang="cpp-qt">
| + | |
| - | QMainWindow *fistStackableWindow = new QMainWindow;
| + | |
| - | QMainWindow *secondStackableWindow = new QMainWindow(fistStackableWindow);
| + | |
| - | // you need the below line to see the back button on the top right hand corner of the stacked window instead of a cross
| + | |
| - | secondStackableWindow->setAttribute(Qt::WA_Maemo5StackedWindow);
| + | |
| - | </source>
| + | |
| - | ''Note: this is not entirely accurate, see''
| + | |
| | | | |
| - | http://qt.nokia.com/doc/qt-maemo-4.6/maemo5-stackedwindows.html
| + | == [[Image:package.png]] Packaging a Qt application for Maemo == |
| | | | |
| - | ===Raise a Qt application in background===
| + | {{main|Packaging a Qt application}} |
| | | | |
| - | <code>QWidget::activateWindow()</code> does the job.
| + | == [[Image:Helmet.png]] Maemo Qt API Reference == |
| | | | |
| - | Implemented in Qt packages >= qt-4.5.3-xxxx-maemo6
| + | 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. |
| | | | |
| - | === How to minimize a Qt application? ===
| + | '''QString QDesktopServices::storageLocation(StandardLocation type)''' returns specific Maemo locations for these types: |
| - | <source lang="cpp-qt">
| + | - DesktopLocation: QDir::homePath() + QLatin1String("/MyDocs"), instead of QDir::homePath() + QLatin1String("/Desktop") |
| - | QDBusConnection c = QDBusConnection::sessionBus();
| + | - DocumentsLocation: QDir::homePath() + QLatin1String("/MyDocs/.documents"), instead of QDir::homePath() + QLatin1String("/MyDocs/.documents") |
| - | QDBusMessage m = QDBusMessage::createSignal("/","com.nokia.hildon_desktop","exit_app_view");
| + | - PicturesLocation: QDir::homePath() + QLatin1String("/MyDocs/.images"), instead of QDir::homePath() + QLatin1String("/Pictures") |
| - | c.send(m);
| + | - MusicLocation: QDir::homePath() + QLatin1String("/MyDocs/.sounds"), instead of QDir::homePath() + QLatin1String("/Music") |
| - | </source>
| + | - MoviesLocation: QDir::homePath() + QLatin1String("/MyDocs/.videos"), instead of QDir::homePath() + QLatin1String("/MyDocs/.videos") |
| - | ===Portrait mode and listening for orientation changes===
| + | |
| | | | |
| - | If you want to run your application in portrait mode then you can add these lines to your application. The code goes in your main widget constructor.
| + | '''QTabletEvents''' are able to get the pressure value from the touchscreen. |
| - | <source lang="cpp-qt">
| + | - The eventdeviceType is for the touchscreen is set to QTabletEvent::Stylus. |
| - | #ifdef Q_WS_HILDON
| + | - QTabletEvents won't be used anymore in Fremantle |
| - | //Includes for portrait mode support | + | |
| - | # include <X11/Xlib.h>
| + | '''Finger poke''' is emulated in scratchbox by the Middle Mouse button (NOTE: There is no Fullscreen VKB in scratchbox) |
| - | # include <X11/Xatom.h>
| + | |
| - | # include <QtGui/QX11Info> | + | '''QInputEvents''' don't move the cursor. |
| - | #endif | + | 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 |
| | | | |
| - | #ifndef Q_WS_HILDON
| + | '''Input Method:''' |
| - | int value = 1;
| + | Maemo Qt uses the Hildon IM as default Input method. |
| - | Atom portraitSupport = XInternAtom(QX11Info::display(), "_HILDON_PORTRAIT_MODE_SUPPORT", false);
| + | 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. |
| - | Atom portraitRequest = XInternAtom(QX11Info::display(), "_HILDON_PORTRAIT_MODE_REQUEST", false);
| + | Eg: spinboxes can receive only numeric characters (1-9). |
| - | XChangeProperty(QX11Info::display(), winId(), portraitSupport, XA_CARDINAL, 32, PropModeReplace, (uchar *)&value, 1);
| + | |
| - | XChangeProperty(QX11Info::display(), winId(), portraitRequest, XA_CARDINAL, 32, PropModeReplace, (uchar *)&value, 1);
| + | NOTE: Qt widgets like QTextEdit, QLineEdit... set the right input method mode automatically. |
| - | #endif
| + | |
| - | </source>
| + | A developer can change it by using: |
| - | If you want to listen for orientation changes and then switch the view to landscape or potrait mode automatically than take a look at [[Maemo Qt Extra Libraries]] for more information.
| + | 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); |
| | + | } |
| | + | } |
| | | | |
| - | === QDockWidgets ===
| + | 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. |
| | | | |
| - | QDockWidgets are not finger friendly widgets. They should not be used in Maemo.
| + | Eg: |
| - | In case you are porting an application to Maemo maybe you want to do
| + | This is what you MUST avoid. |
| - | few changes as possible into your UI. Then you could use QDockWidget::setFeatures(QDockWidget::NoDockWidgetFeatures); to hide float and close button and lock the position of the dock widget.
| + | QColorDialog::getColor ( Qt::white, 0 ) |
| | + | |
| | + | Remember to setup a parent |
| | + | QColorDialog::getColor ( Qt::white, this ) |
| | | | |
| - | === QPrint* and QSystemTray support missing === | + | == [[Image:Helmet.png]] Contributing to the Maemo Qt Project == |
| | | | |
| - | Printing (QPrint*) and System tray support is missing in current Qt 4.5.3-xxxx-maemo4 packages. Since incompatibility with KDE and other Qt application, they will be enabled again in next Qt 4.5.3 packages.
| + | 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. |
| | | | |
| - | === QSplashScreen not fully compatible with Hildon-Desktop === | + | ===Commit changes in SVN=== |
| | | | |
| - | QSplashScreen's window type is not supported in Fremantle. The splash screen is shown in full screen and the image is repeated to fill the splash screen's window. When splash screen is closed normal window closing animation is shown before showing the actual application window. For these reasons developers are disencouraged to use splash screens in their applications.
| + | 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. |
| | | | |
| - | As a workaround for the problem you can set a window property that tells HD to skip the transitions:
| + | 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. |
| - | <source lang="cpp-qt">
| + | 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" |
| - | static void set_no_transitions (Display *dpy, Window w)
| + | |
| - | {
| + | |
| - | Atom no_trans;
| + | |
| - | int one = 1;
| + | |
| - | no_trans = XInternAtom (dpy, "_HILDON_WM_ACTION_NO_TRANSITIONS", False);
| + | |
| - | XChangeProperty (dpy, w, no_trans,
| + | |
| - | XA_CARDINAL, 32, PropModeReplace,
| + | |
| - | (unsigned char *)&one, 1);
| + | |
| - | }
| + | |
| - | </source>
| + | |
| | | | |
| - | === QToolBar limitations ===
| + | NOTE: Subversion uses cheap copy, so them don't increase the size of the repository. Then feel free to create your own branch. |
| | | | |
| - | Adding a QToolBar to a QMainWindow will always result in a toolbar at the bottom of the screen. (Justification/Workarounds?)
| + | ===Merging branche changes in the mainline=== |
| | | | |
| - | == Contributing to the Maemo Qt Project ==
| + | 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. |
| - | | + | |
| - | 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.
| + | |
| - | | + | |
| - | ===Stay 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.
| + | ===Be updated=== |
| | | | |
| - | === Introduction to Git ===
| + | Any Maemo Qt developer should be updated and should participate to the discussions, for that he must join the Mailing list. |
| | | | |
| | + | === Using Git === |
| | + | We started to move out our repository from SVN to GIT. |
| | If you are a git newbie you maybe find interesting these links: | | If you are a git newbie you maybe find interesting these links: |
| | + | |
| | * http://www.sourcemage.org/Git_Guide | | * http://www.sourcemage.org/Git_Guide |
| | * http://www.gitcasts.com/ | | * http://www.gitcasts.com/ |
| | * http://www.gnome.org/~newren/eg/git-for-svn-users.html | | * 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=== | + | ==[[Image:Help-contents.png]] F.A.Q.== |
| | | | |
| - | {{main|Qt Maemo Git Process}}
| + | === I'm trying to compile a Qt application for ARMEL, but I got the error below. What's wrong? === |
| | | | |
| - | === Preparation ===
| + | /targets/FREMANTLE_X86/usr/include/qt4/QtCore/qatomic_i386.h:127: error: impossible constraint in 'asm' |
| | | | |
| - | Make sure each scratchbox target has
| + | 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. |
| | | | |
| - | fakeroot apt-get build-dep libqt4-gui
| + | === I'm trying to compile a Qt packcage for x86, but I got the error below. What's wrong? === |
| - | | + | |
| - | (you may need to apt-get install libgl-dev too as it's not in the Build-Depends: yet)
| + | |
| - | | + | |
| - | ===Building Qt from Git repository=== | + | |
| - | | + | |
| - | # Clone the repository:<pre>git clone git://gitorious.org/+qt-maemo-developers/qt/qt-maemo.git</pre>or if you are a member of our team:<pre>git clone git@gitorious.org:+qt-maemo-developers/qt/qt-maemo.git</pre>
| + | |
| - | # Change dir:<pre>cd qt-maemo</pre>
| + | |
| - | # Copy the remote 4.5 branch in your working copy:<pre>git checkout -b 4.5 origin/4.5</pre>
| + | |
| - | # Checkout ONE of these branches:<pre>git checkout -b qt-diablo origin/qt-diablo</pre><pre>git checkout -b qt-n900+w34 origin/qt-n900+w34</pre><pre>git checkout -b qt-mer origin/qt-mer</pre>
| + | |
| - | # Build the packages:<pre>dpkg-buildpackage -rfakeroot -b</pre>
| + | |
| - | | + | |
| - | ===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.
| + | |
| | | | |
| - | ===QML===
| + | In file included from maemo/gconfsymbols.cpp:41: |
| - | [[QML]] is a GUI interface building scripting language for Qt. Check out the [[QML-EnhancedCalcExample | QML calculator example]].
| + | maemo/gconfsymbols_p.h:49:25: gconf/gconf.h: No such file or directory |
| | | | |
| - | ==F.A.Q.==
| + | 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 Qt application for ARMEL, but I got the error below. What's wrong?''
| + | === 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. === |
| - | : <pre>/targets/FREMANTLE_X86/usr/include/qt4/QtCore/qatomic_i386.h:127: error: impossible constraint in 'asm'</pre>
| + | |
| - | :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?
| + | 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. |
| - | : <pre>In file included from maemo/gconfsymbols.cpp:41:
| + | |
| - | maemo/gconfsymbols_p.h:49:25: gconf/gconf.h: No such file or directory</pre> | + | |
| - | : 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
| + | == References == |
| - | : 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
| + | <references/> |
| - | : 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.
| + | |
| - | : <pre>http://qt4.garage.maemo.org/patches/qt4-missing-header.tgz</pre>
| + | |
| | | | |
| | | | |
| | [[Category:Development]] | | [[Category:Development]] |
| | [[Category:Qt]] | | [[Category:Qt]] |
