Maemo Wiki Mirror - User contributions [en]

Maemo Summit 2009/Accommodation

2010-10-04T18:51:06Z

192.100.124.219: Redirecting to MeeGo Conference accommodation since this URL was used in an email notification by mistake

Looking for the MeeGo Conference 2010 Accommodation page?

See http://wiki.meego.com/MeeGo_Conference_2010/Accommodation

PyMaemo/Components

2010-08-18T10:12:58Z

192.100.124.219: /* Bindings */

=== Core ===

These packages are the minimal necessary to run or develop Python applications for Maemo.

;[http://www.python.org/ python2.5]
:Version 2.5 of the high-level, interactive object oriented language, includes an extensive class library with lots of goodies for network programming, system administration, sounds and graphics.
;python-central
:Provides support for building and installing python modules independent of the current installed Python version.
;python-defaults
:Provides meta packages with unversioned package names (e.g. python-dev, which installs python2.5-dev).
;python-runtime
:Meta package which installs the basic Python runtime environment.
;python-support
:Provides tools for byte-compilation of Python-only modules, and automatic rebuild on major Python upgrades.

=== Bindings ===

These packages provide bindings for various Maemo components.

;[http://dbus.freedesktop.org/doc/dbus-python/ dbus-python]
:Python interface to D-Bus.
;[http://www.pygtk.org/reference.html gnome-python]
:Python interface to various GNOME libraries: GConf, GnomeVFS, bonobo, libgnome, libgnomeui and libgnomecanvas.
;[http://pygstdocs.berlios.de/ gst0.10-python]
:Python interface to GStreamer.
;[http://codespeak.net/lxml/index.html#documentation lxml]
:Python interface to libxml2 and libxslt.
;[http://org.csail.mit.edu/pybluez/docs.html pybluez]
:Python interface to the BlueZ bluetooth stack.
;[http://www.cairographics.org/pycairo/ pycairo]
:Python interface to the Cairo vector graphics library.
;[http://pycurl.sourceforge.net/ pycurl]
:Python interface to libcurl.
;[http://www.pygame.org/news.html pygame]
:A multimedia development kit for Python, based mostly on SDL.
;[http://www.pygtk.org/reference.html pygobject]
:Python interface to GObject.
;[http://www.pygtk.org/reference.html pygtk]
:Python interface to GTK+.
;[http://packages.python.org/pyOpenSSL/ pyopenssl]
:Python interface to OpenSSL.
;python-alarm
:Python interface to libalarm.
;[http://www.clutter-project.org/ python-clutter]
:Python interface to Clutter.
;python-conic
:Python interface to libconic.
;python-hildon
:Python interface to Hildon.
;[[PyMaemo/HildonDesktop|python-hildondesktop]]
:Python interface to the Hildon Desktop applets.
;[http://www.pythonware.com/products/pil/ python-imaging]
:The Python Imaging Library.
;[[PyMaemo/Using_Location_API|python-location]]
:Python interface to liblocation.
;python-mafw
:Python interface to MAFW.
;[http://www.galago-project.org/specs/notification/ python-notify]
:Python interface to libnotify.
;[http://people.csail.mit.edu/jrennie/python/numeric/ python-numeric]
:The Numeric Extensions to Python (deprecated).
;python-osso
:Python interface to libosso.
;[http://pyxml.sourceforge.net/ python-xml]
:Python interface to XML (deprecated; use python-lxml instead).
;[https://storm.canonical.com/ storm]
:Object-relational mapper (ORM) for Python.
;pyside-qt4
:PySide Python Qt bindings (metapackage depending on everything else)
;pyside-qt4-core
:PySide QtCore library
;pyside-qt4-gui
:PySide QtCore library
;pyside-qt4-help
:PySide QtHelp library
;pyside-qt4-maemo5
:PySide QtMaemo5 library
;pyside-qt4-multimedia
:PySide QtMultimedia library
;pyside-qt4-network
:PySide QtNetwork library
;pyside-qt4-phonon
:PySide Phonon library
;pyside-qt4-script
:PySide QtScript library
;pyside-qt4-sql
:PySide QtSql library
;pyside-qt4-svg
:PySide QtSvg library
;pyside-qt4-test
:PySide QtTest library
;pyside-qt4-uitools
:PySide UiTools
;pyside-qt4-webkit
:PySide QtWebKit library
;pyside-qt4-xml
:PySide QtXml library
;pyside-qt4-xmlpatterns
:PySide QtXmlPatterns library
;pyside-mobility
:PySide Mobility metapackage depending on every other package
;pyside-mobility-bearer
:PySide Mobility Bearer API bindings
;pyside-mobility-contacts
:PySide Mobility Contacts API bindings
;pyside-mobility-location
:PySide Mobility Location API bindings
;pyside-mobility-messaging
:PySide Mobility Messaging API bindings
;pyside-mobility-publishsubscribe
:PySide Mobility PublishSubscribe API bindings
;pyside-mobility-sensors
:PySide Mobility Sensors API bindings
;pyside-mobility-serviceframework
:PySide Mobility Service Framework API bindings
;pyside-mobility-systeminfo
:PySide Mobility System Info API bindings
;pyside-mobility-versit
:PySide Mobility Versit API bindings

=== Applications ===

We provide some Python applications as examples, and that we find useful for PyMaemo users.

;[http://ipython.scipy.org/moin/ ipython]
:A enhanced interactive Python shell.

=== Development ===

These packages are necessary only if you are developing Python applications on Maemo.

;[http://www.cython.org/ cython]
:Cython is a language that makes writing C extensions for the Python language as easy as Python itself.
;[http://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/ pyrex]
:Pyrex lets you write code that mixes Python and C data types any way you want, and compiles it into a C extension for Python.
;[http://pypi.python.org/pypi/setuptools#using-setuptools-and-easyinstall python-setuptools]
:Extensions to the python-distutils for large or complex distributions.

=== Support packages ===

These packages are provided as dependencies for other packages, and are not used directly by users/developers.

;sdl-ttf2.0 (dependency for pygame)
:TTF library for SDL with FreeType 2 support.

[[Category:Python]]

Hildon-Extras

2010-08-16T11:14:43Z

192.100.124.219: /* List of applications using Hildon-Extras */

Hildon-Extras is a set of community-contributed widgets (that's GTK+ widgets, not Desktop widgets) and dialogs that can be used by application developers to provide a usable, well-balanced interface. Some of these widgets provide functionality that the "stock" [[Hildon]] widgets don't provide, and some dialogs are touch-friendly versions of existing dialogs in GTK+ and/or Hildon.

* http://hildon-extras.garage.maemo.org/

==Current status==

Hildon-Extras is very close to being released. The components are considered quite stable, but some small polishing is needed until release.

===Translations===

If you are interested in translating Hildon-Extras, please have a look at the Transifex project here: http://www.transifex.net/projects/p/hildon_extras/c/trunk/ There are only about 7 strings that shouldn't take you more than a minute to translate.

===Qt integration===

There is a class called <code>QtHeWrapper</code>. in Hildon-Extras that is provided to developers of [[Qt-Maemo|Qt]]-based apps. It is a [[:wikipedia:Wrapper_library|wrapper]] that provides interoperability between Hildon-Extras and Qt code. It allows developers to call Hildon-Extras easily from Qt-based software.

<code>QtHeWrapper</code> currenty supports all the dialogs in Hildon-Extras. It allows for easily displaying any of the dialogs.

===List of applications using Hildon-Extras===

* [http://maemo.org/downloads/product/Maemo5/conboy/ Conboy] (<code>HeCheckButton</code>, <code>HeFullscreenButton</code>, <code>HeAboutDialog</code>)
* [http://thpinfo.com/2010/maepad/ MaePad] (<code>HeAboutDialog</code>, <code>HeFullscreenButton</code>, <code>HeSimpleColorDialog</code>)
* [http://mrawviewer.garage.maemo.org MRAWViewer] (<code>HeFullscreenManager</code> at the moment, planning to add <code>HeAboutDialog</code> for the next release)
* [https://garage.maemo.org/projects/maemo-mapper/ Mapper] (<code>HeAboutDialog</code>)
* [http://maemo.org/downloads/product/Maemo5/custom-operator-name-widget/ Custom Operator Name Widget] (<code>HeColorDialog</code>)
* [http://maemo.org/downloads/product/Maemo5/gpodder/ gPodder] (<code>HeAboutDialog</code>)
* [http://maemo.org/downloads/product/Maemo5/panucci/ Panucci] (<code>HeAboutDialog</code>)
* [[Queen BeeCon Widget]] (<code>HeFont*</code>, <code>He*Color*</code>)
* [https://garage.maemo.org/projects/sticky-notes/ Sticky Notes] (<code>HeSimpleColorDialog</code>, <code>HeColorDialog</code>, and <code>HeAboutDialog</code> through <code>QtHeWrapper</code>)
* [https://extcalllog.garage.maemo.org/ Extended Call Log] (<code>HeAboutDialog</code>)
* [https://webtexter.garage.maemo.org/ WebTexter] (<code>HeAboutDialog</code>)
* [https://pidgin.garage.maemo.org/ Pidgin] (<code>HeMenuView</code>)
* ''(add yours here)''

==Widget Gallery==

Here is a list of widgets currently in Hildon-Extras.

===Dialogs===

Hildon-Extras has a nice collection of dialog windows that are optimized to be both good-looking and finger-friendly.

All of the dialogs support integration with Qt-based software via the <code>QtHeWrapper</code> class (in the "qt-he-wrapper.h" header).

====HeAboutDialog====

[[Image:HeAboutDialog.png|thumb|About dialog in MaePad]]

The <code>HeAboutDialog</code> is a replacement for <code>GtkAboutDialog</code> and provides a finger-friendly, good-looking about dialog with optional buttons for:

* Project website
* Bug tracker ("Enter new bug")
* Donations page

There is a [[:wikipedia:Wrapper_function|wrapper]] that can be used by Qt-based applications for this dialog in <code>QtHeWrapper</code>.

If you are writing a Python application, you might be interested in the Python port of <code>HeAboutDialog</code>: [http://repo.or.cz/w/gpodder.git/blob_plain/HEAD:/src/gpodder/gtkui/frmntl/about.py Download about.py]

====HeSimpleColorDialog====

[[Image:HeSimpleColorDialog.png|thumb|Simple color dialog]]

This dialog provides a finger-friendly, limited list of colors (a Tango-ish color palette) for the user to choose from. Especially useful when the color selection does not have to be "that special shade of green" but rather "a nice green" (for example to colorize categories or items).

There is also the possibility of an advanced mode for this dialog.
This presents an additional "Advanced" button above "Select". When clicked, it presents the user with a regular <code>HeColorDialog</code> to pick an exact colour.

Example code and use cases:

* MaePad uses it for coloring the text of checklist items and for the color in sketches ([http://repo.or.cz/w/maepad.git/blob/HEAD:/src/ui/callbacks.c src/ui/callbacks.c])

====HeColorDialog====

[[Image:HeColorDialog.png|thumb|Color dialog]]

This dialog lets the user to select a color by selecting the intensity of the red, green, and blue channels. Also provides hex input/output of colours.

It may come in handy when a developer wants his/her users to be able to pick an exact shade of an exact colour in a finger-friendly way.

====HeFontDialog====

[[Image:HeFontDialog.png|thumb|Font dialog]]

Lets the user choose a font together with a font size. It also offers bold and italic styles.

====HeMenuView====

[[Image:he-menu-view-before-and-after.png|thumb|Menu view]]

This widget allows you to display a GtkMenu as a series of columns in a dialog. In addition, you can hook into all your HildonWindow widgets and have those menus that are not HildonAppMenu widgets appear as HeMenuView dialogs.

===Buttons===

The buttons in Hildon-Extras provide commonly used behaviour and are looking nice.

====HeCheckButton====

[[Image:HeCheckButton.png|thumb|Check button]]

<code>HeCheckButton</code> is a check button with primary and secondary labels. The standard HildonCheckButton supports only one label.

This button can be very handy for developers who would like to provide some description about the functionality of a check box.

====HeFullscreenButton====

[[Image:HeFullscreenButton.png|thumb|The HeFullScreenButton]]

<code>HeFullscreenButton</code> is a button that allows users to '''leave''' full screen mode. It becomes visible after the user touched the screen or pressed a key and it vanishes after 5 seconds of inactivity.

It looks like the full screen button in the built-in applications of Maemo 5, so it is very good if a developer wants his/her application to blend in well with the rest of the platform.

====HeColorButton====

[[Image:HeColorButton.png|thumb|Color button]]

On tapping the <code>HeColorButton</code> opens the <code>HeColorDialog</code> and lets the user select a color. This color is then displayed on the <code>HeColorButton</code>.

====HeFontButton====

[[Image:HeFontButton.png|thumb|Font button]]

On tapping the <code>HeFontButton</code> displays a <code>HeFontDialog</code> that lets the user select a font. The selected font is then displayed on the <code>HeFontButton</code>.

[[Category:Development]]
[[Category:Documentation]]
[[Category:Fremantle]]

Packaging a Qt application

2010-06-18T14:12:45Z

192.100.124.219:

= Packaging a Qt application for Maemo=

{{main|Packaging}}

Packaging a Qt application for Maemo is very similar to packaging any other application, so this document only contains information on Qt-specific packaging issues.

== Creating a Maemo package from a qmake project ==

In order to create a new package for Maemo, from a qmake project, you will need to:
* Rename the source directory to <code>Package-Version</code> (for example myapp-0.1 for an application ‘myapp’ with a version of ‘0.1’)
* Create a ‘src’ directory in <code>Package-Version/</code>
* Copy all the files to the <code>src/</code> directory
* Rename <code>src/appname.pro</code> to <code>src/src.pro</code>
Please make sure that the directory name is <package-version> format and in small case letters.

<pre>
$mv myapp myapp-0.1
$cd myapp-0.1
$mkdir src
$cp * src
$mv src/appname.pro src/src.pro
</pre>

Append the following chunk to end of your <code>src/src.pro</code>. The chunk adds an install section to your qmakefile

<pre>
unix {
#VARIABLES
isEmpty(PREFIX) {
PREFIX = /usr/local
}
BINDIR = $$PREFIX/bin
DATADIR =$$PREFIX/share

DEFINES += DATADIR=\\\"$$DATADIR\\\" PKGDATADIR=\\\"$$PKGDATADIR\\\"

#MAKE INSTALL

INSTALLS += target desktop service iconxpm icon26 icon48 icon64

target.path =$$BINDIR

desktop.path = $$DATADIR/applications/hildon
desktop.files += $${TARGET}.desktop

service.path = $$DATADIR/dbus-1/services
service.files += $${TARGET}.service

iconxpm.path = $$DATADIR/pixmap
iconxpm.files += ../data/maemo/$${TARGET}.xpm

icon26.path = $$DATADIR/icons/hicolor/26x26/apps
icon26.files += ../data/26x26/$${TARGET}.png

icon48.path = $$DATADIR/icons/hicolor/48x48/apps
icon48.files += ../data/48x48/$${TARGET}.png

icon64.path = $$DATADIR/icons/hicolor/64x64/apps
icon64.files += ../data/64x64/$${TARGET}.png
}
</pre>

*Create a <code>myapp-0.1/myapp.pro</code> file like this:
<pre>
QMAKEVERSION = $$[QMAKE_VERSION]
ISQT4 = $$find(QMAKEVERSION, ^[2-9])
isEmpty( ISQT4 ) {
error("Use the qmake include with Qt4.4 or greater, on Debian that is qmake-qt4");
}

TEMPLATE = subdirs
SUBDIRS = src
</pre>
*Run dh_make to debianize the source archive, it creates:
**An archive with the unchanged upstream source (orig.tar.gz)
**Some basic files in the debian directory
**Some example files (*.EX *.ex)
<pre>
export DEBFULLNAME="maintainer first name and last name"
dh_make --createorig --single -e maintainer@email.org -c gpl
</pre>

== Editing the rules file ==
The rules file generated by <code>dh_make</code>, found in <code>debian/rules</code> will be modified in order to look like this one. We are using qmake, so there is no <code>configure</code> script to run. If you copy and paste the following file, notice the empty space at the beginning of the lines these are TAB characters, they are not multiple space characters. If you copy and paste the following chunk, you most propably get space's instead of tabs if this is true then the file will not work.

<pre>
#!/usr/bin/make -f
APPNAME := my_app_name
builddir:
mkdir -p builddir

builddir/Makefile: builddir
cd builddir && qmake-qt4 PREFIX=/usr ../$(APPNAME).pro

build: build-stamp

build-stamp: builddir/Makefile
dh_testdir
# Add here commands to compile the package.
cd builddir && $(MAKE)
touch $@

clean:
dh_testdir
dh_testroot
rm -f build-stamp
# Add here commands to clean up after the build process.
rm -rf builddir
dh_clean
install: build
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs

# Add here commands to install the package into debian/your_appname
cd builddir && $(MAKE) INSTALL_ROOT=$(CURDIR)/debian/$(APPNAME) install
# Build architecture-independent files here.
binary-indep: build install
# We have nothing to do by default.

# Build architecture-dependent files here.
binary-arch: build install
dh_testdir
dh_testroot
dh_installdocs
dh_installexamples
dh_installman
dh_link
dh_strip --dbg-package=my-application-dbg
dh_compress
dh_fixperms
dh_installdeb
dh_shlibdeps
dh_gencontrol
dh_md5sums
dh_builddeb

binary: binary-indep binary-arch
.PHONY: build clean binary-indep binary-arch binary install configure
</pre>

== Editing the control file ==
The control file generated by <code>dh_make</code>, found in <code>debian/control</code> will be modified substantially. Please refer to the general packaging guide for Maemo for details.

For Qt applications you need to make sure to add <code>libqt4-dev</code> as an additional entry in the field <code>Build-Depends</code>.

= Example =
You can download the [http://maemo.org/packages/view/qt-maemo-example/ source package of qt-maemo-example] from the [[extras-devel]] repository as follows, if you have source packages enabled in your <code>/etc/apt/sources.list</code> file:

apt-get source qt-maemo-example

This command will download the:

* unmodified source (.orig.tar.gz)
* debian dsc file (.dsc)
* diff file (.diff)

and will then automatically launch <code>dpkg -x file.dsc</code> in order to decompress the orig.tar.gz and apply the changes.

= Useful Links =

* [[Qt-Maemo|Qt for Maemo]]
* [[Packaging|Packaging guide for Maemo]]
* [http://doc.qt.nokia.com/qt-maemo-4.6/maemo5-with-qt-introduction.html#deploying-your-applications Deploying your Maemo 5 Qt application] Qt documentation

[[Category:Packaging]]
[[Category:Qt]]

MADDE/Packaging

2010-06-18T13:55:09Z

192.100.124.219:

{{MADDE}}

===Introduction===
This guide explains how to take a simple [[Qt-Maemo|Qt]] application and compile it so that it deploys to the [[Nokia N900|N900]] with an Icon. It is supposed to be step by step guide on how to take a (simple) Qt app and package and deploy it with an Icon using [[MADDE]].

=== Prerequisites ===

The project I have is simple, 1 window called mainwindow.

'''Note:''' As a convention I like to keep all my code together, so I have created any extra files in the "src" folder.

=== Steps ===

<ol>
<li>Create simple project through MADDE.
mad pscreate -t qt_simple projectname</li>

<li>Edit and test with Qt Creator (or whatever your favorite tool is).</li>

<li>Once ready to deploy create a clean empty top level folder <code><projectname>-0.x</code> where <code>x</code> is your revision number, for example <code>C:\Madde\0.5\home\shep\wwcalc-0.1</code> in the OS
'''Note: the following 3 steps apply each time you go to build.'''
<ol><li>ensure there is no <code>debian</code> folder at the same level as <code>src</code></li>
<li>ensure there is no folder structure called <code><projectname>-0.x-orig</code> left over from a failed compile</li>
<li>remove old compiles from the <code>Madde\home\user</code>, for example <code>C:\Madde\0.5\home\Shep</code> folder.</li></ol></li>

<li>Copy the <code>src</code> folder from the tested Qt project into the <code><projectname-0.x</code> folder</li>

<li>Create (or obtain) an application Icon. This should be a 64x64 PNG. Call it <code><projectname>.png</code> and place it in the <code>src</code> folder.</li>

<li>Again inside the <code>src</code> folder create a new file called <code><projectname>.desktop</code>
Code:
<pre>
[Desktop Entry]
Encoding=UTF-8
Version=0.x
Type=Application
Name=<Long Descriptive Project Name>
Exec=/usr/bin/<projectname>
Icon=<projectname>
X-HildonDesk-ShowInToolbar=true
X-Osso-Type=application/x-executable
</pre></li>

<li>Inside the <code>src</code> folder added a file called <code>src.pro</code>. Getting this right is the key to getting the Makefile correct and hence the install working. At the end of this file there is a section called <code>INSTALLS += ...</code> for every file you want installed in a location you need an entry here. In the example here we install the target, icon and desktop files.
Code:
<pre>
TARGET = wwcalc
TEMPLATE = app
SOURCES += qtmain.cpp \
mainwindow.cpp
HEADERS += mainwindow.h
FORMS += mainwindow.ui

unix {
PREFIX = /usr
BINDIR = $$PREFIX/bin
DATADIR =$$PREFIX/share

DEFINES += DATADIR=\"$$DATADIR\" PKGDATADIR=\"$$PKGDATADIR\"

#MAKE INSTALL

INSTALLS += target desktop icon64

target.path =$$BINDIR

desktop.path = $$DATADIR/applications/hildon
desktop.files += wwcalc.desktop

icon64.path = $$DATADIR/icons/hicolor/64x64/apps
icon64.files += wwcalc.png
}
</pre></li>

<li>Up one level and inside the top level folder (that is, <code>C:\Madde\0.5\home\<YOU!>\<projectname>-0.x</code> ) create a file called <code><projectname>.pro</code> with the following exact contents.
Code:
<pre>
TEMPLATE = subdirs
SUBDIRS = src
</pre></li>

<li>In Madde make sure the [[MADDE/Device runtime|runtime is up and connectible]] and then execute.
Code:
<pre>
mad dh_make --createorig --single -e foo.bar@gmail.com -c gpl
</pre>
''Several people have commented that mad qmake is not required, but I find there are times that it is, ignore this next line if you wish''
<pre>
mad qmake
mad dpkg-buildpackage
mad remote -r org.maemo.<projectname> send ../<projectname>_0.x-1_armel.deb
mad remote -r org.maemo.<projectname> install <projectname>_0.x-1_armel.deb</pre></li>

<li>Uninstalling - from an X_Terminal.
Code:
<pre>
sudo gainroot
dpkg -r <projectname></pre></li></ol>

== Additional information ==

* [[Packaging a Qt application]]
* [[Packaging]]

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

Documentation/Maemo 5 Final SDK Installation

2010-05-27T11:50:36Z

192.100.124.219: /* Fixed typo, and added few corrections */

=Introduction=

The following document describes the installation of the Maemo 5 Final SDK. Maemo SDK uses Scratchbox as the cross compilation environment into which Maemo specific development files are installed.

Before we begin with the installation, have a look at the minimum system requirements. We officially support x86-32 Debian based distributions, mainly Debian and Ubuntu though it is possible to install the SDK on other flavours of Linux too.

Once you are sure that your development machine fulfils these requirements, you can proceed with the following guidelines:

Maemo 5 SDK comes with two command line installation scripts and GUI installer (beta) to ease the SDK installation.
*Scratchbox installer script which downloads and installs the required version of Scratchbox onto your host machine.
*Maemo SDK installer which sets up two targets (armel and x86) inside Scratchbox, downloads the minimal rootstraps for both targets, and installs the open source development files based on the user selection during the installation process.
*GUI installer which combines both Scratchbox and SDK installation.

Maemo 5 SDK also provides the essential Nokia proprietary binary packages needed for Maemo development and additional Nokia applications in an authenticated repository. In order to have access to this repository, you will need to accept the End User License Agreement (EULA).   For the complete functionality and usability of the Maemo SDK, it is required to install Nokia proprietary binary packages in addition to the open source packages.

==What is not included in the Maemo SDK?==
Xephyr X11 server software is needed on your host machine before you can run any applications in the Maemo SDK. It is an X11 server that provides a device screen for the developer so that you can see all the Maemo application windows and visuals on your host machine. This software is not included in the SDK mainly because it is available on most linux distributions.

If you choose to install Maemo SDK using the GUI installer on Debian based systems, it will provide an option to install Xephyr for you.

If not, you can manually install Xephyr as follows:

On Debian based linux systems, Xephyr can be installed outside Scratchbox environment using apt with root permission:

$ sudo apt-get install xserver-xephyr

On a Gentoo system you need to install xorg-server with the kdrive useflag. This builds the Xephyr binary.

=Installing Maemo 5 SDK using GUI Installer=

Maemo 5 SDK installation is now made easy with GUI installer. This
installer will install Scratchbox and Maemo 5 SDK on Debian based
systems. This installer will allow installation of nokia closed packages and
applications provided that EULA at [http://tablets-dev.nokia.com/eula/index.php this webpage] is accepted.

'''GUI Installer has following features:'''
* Install/Upgrade Scratchbox
* Installation of Maemo 5 SDK
* Installation of nokia-binaries
* Installation of nokia-apps
* Installation of Xephyr, if missing
* Can create a launcher for Xephyr on Desktop
* Can create a shortcut to Scratchbox home folder on Desktop
* Can create Maemo 5 info page on Desktop that contains useful links for developers
* Uninstallation of scratchbox & targets (debian-based distros only)

GUI installer offers standard and custom installation modes in a wizard. Standard installation will use default settings, while custom offers more choices. Please note that standard mode will overwrite any of the standard targets (FREMANTLE_X86, FREMANTLE_ARMEL) if present, but contents of Scratchbox home will be preserved. Please use the custom mode if you don't want to overwrite your targets.

The GUI installer Qt application requires python bindings for Qt. GUI installer can install the required packages if not already installed.

The installer will use http_proxy environment variable if available. If
your connection doesn't seem to work, you will be asked to manually
enter proxy settings.

GUI installer has been tested on Ubuntu Karmic and Debian Lenny, both 32bit and 64bit versions. The GUI installer needs to download Maemo SDK so it requires a working Internet connection. On 64bit kernel, you need to disable VDSO for 32bit applications manually.

'''Starting installation with GUI installer:'''

There is some missing options in this python script if you run from non-debian linux systems you got errors, because it will not automatically define the installation path of scratchbox, to correct this errors you must patch this script.

Also you must uncheck Xephyr checkbox and install it manually.

129c129
< SB_PATH = "/scratchbox"
---
> SB_PATH = "/opt/scratchbox"
2297a2298
> opt = opt + "-s /opt/scratchbox"
2351a2353
> cmd = cmd +" -s /opt/scratchbox"

wget http://repository.maemo.org/stable/5.0/maemo-sdk-install-wizard_5.0.py
chmod a+x maemo-sdk-install-wizard_5.0.py

$ Installer requires root privileges
Ubuntu
sudo ./maemo-sdk-install-wizard_5.0.py
Debian
su -c ./maemo-sdk-install-wizard_5.0.py

'''Limitations:'''
*As the installer will do package installation, you should quit all package managers before running it.
*Please note that detecting scratchbox is not perfect and it will detect only if it is installed in /scratchbox path.
*Please note that python-qt features used in this installer might not be available in older ubuntu and debian distros.
*Due to differences in versions of Python Qt bindings, certain parts of installation can work differently on different systems.
*Installer only shows required settings on 64-bit machines but does not add them automatically.
*Installer will always use DISPLAY :2, if you want to use a different value, you need to change it manually.
*GUI installer doesn't work on SUSE Linux. You can use command line installers instead.

=Installing Maemo 5 SDK on x86-32 Debian based distribution=

1. Download the scratchbox installer and the Maemo SDK installer scripts. These are the same scripts as are available through Forum Nokia: [http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/Platforms/Maemo/ Maemo SDK at Forum Nokia].

$ wget http://repository.maemo.org/stable/5.0/maemo-scratchbox-install_5.0.sh http://repository.maemo.org/stable/5.0/maemo-sdk-install_5.0.sh

2. Set the permissions to execute the scripts.

$ chmod a+x ./maemo-scratchbox-install_5.0.sh ./maemo-sdk-install_5.0.sh

Users of Ubuntu 10.04 LTS will need to do the following to fix the installation, note that this may reduce system security! [http://talk.maemo.org/showpost.php?p=636394&postcount=8]

$ sudo su
$ echo "vm.mmap_min_addr = 0" >> /etc/sysctl.conf
$ sysctl -p
$ exit #to go back to user

3. Run the scratchbox installer with root permission specifying the username to be added to scratchbox users group and sbox group. The username should be an existing user name from the host linux system. This will download about 420 MB of material from the web, which is not resumeable if interrupted.

$ sudo ./maemo-scratchbox-install_5.0.sh -u $USER

4. The installation script adds the specified user to ‘sbox’ user group. For the group membership to be effective in the current terminal session, run the following command:

Note: This command will change the existing group ID during the current login session to ‘sbox’. If you do not want this change, just logout and log back in again for the group membership to be effective.

$ newgrp sbox

At this step, you should have a working Scratchbox environment ready.

5. Proceed further to run the Maemo SDK installer script. This script is run as 'user' outside the scratchbox environment. Set permission for 'user'before runing script.

$ sudo chmod +x ./maemo-sdk-install_5.0.sh
$ ./maemo-sdk-install_5.0.sh

If you have installed Scratchbox in a path alternative to /scratchbox, you will need to specify the path with ‘-s PATH’ option. More information on available command line options can be found with --help option
Follow the instructions on the go.

6. Once the script has successfully completed its execution, you can login into Scratchbox.

$ /scratchbox/login

If you are not able to login, take a look at the [[#Limitations of Scratchbox|limitations of Scratchbox]].

7. Proceed further to accept the EULA in order to obtain the Nokia proprietary binary packages. These Nokia binaries are essential for the complete functionality of the Maemo SDK.

7.1. Accept the EULA on [http://tablets-dev.nokia.com/eula/index.php this webpage] 
7.2. Copy the sources.list entry given to you after the license acceptance to your Scratchbox x86 and armel target’s /etc/apt/sources.list file. Execute the commands below on the _ARMEL and _X86 targets.

[sbox-FREMANTLE_X86: ~] > sb-conf select FREMANTLE_ARMEL
[sbox-FREMANTLE_ARMEL: ~] > nano /etc/apt/sources.list # add deb line
[sbox-FREMANTLE_ARMEL: ~] > apt-get update
[sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install nokia-binaries nokia-apps

[sbox-FREMANTLE_ARMEL: ~] > sb-conf select FREMANTLE_X86
[sbox-FREMANTLE_X86: ~] > nano /etc/apt/sources.list # add deb line
[sbox-FREMANTLE_X86: ~] > apt-get update
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install nokia-binaries nokia-apps

The above step installs all needed Nokia proprietary binary packages along with the open source binaries that have dependencies to Nokia proprietary binary packages.
With this, your Maemo 5 SDK environment is set up completely and ready for development.

=Installing Maemo 5 SDK on openSUSE=
There are instructions at [http://en.opensuse.org/Maemo5 opensuse.org].

=Installing Maemo 5 SDK on non-Linux operating systems=

If you do not have a Linux environment (Windows or Mac OS X), you can install a [[Documentation/Maemo_5_Developer_Guide/Development_Environment/Maemo_SDK_Virtual_Images|Maemo SDK virtual machine image]]
from [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php tablets-dev.nokia.com].
[http://www.vmware.com/products/player/ VMPlayer is required].

=Starting/Shutting down the SDK UI=

Before starting the UI framework, ensure that you have installed the following:
*Xephyr X11 server on the host machine outside the Scratchbox environment
*The SDK as described above
*The Nokia proprietary binary packages

1. Now, run Xephyr outside the scratchbox environment:

$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb &

Ubuntu 10.04 users using the package in the repositories will have to run the same command without the -host-cursor and -kb, however the terminal window will have to stay open.

2. Login to Scratchbox X86 target

$ /scratchbox/login

Welcome to Scratchbox, the cross-compilation toolkit!

Use 'sb-menu' to change your compilation target.

See /scratchbox/doc/ for documentation.

[sbox-FREMANTLE_X86: ~]>

3. Set the DISPLAY variable to match the display setting given for the Xephyr server.

[sbox-FREMANTLE_X86: ~] >export DISPLAY=:2

4. Start the UI framework .

[sbox-FREMANTLE_X86: ~] >af-sb-init.sh start

5. You will now see the UI framework up and running on the Xephyr window.

6. You can shut down the UI framework as follows:

[sbox-FREMANTLE_X86: ~] >af-sb-init.sh stop

=Installation of x86-64 Debian based distributions=
Since Scratchbox only supports x86-32 bit Linux host systems, we need to force the installation of x86-32 Scratchbox packages on the x86-64 bit machines. Using the -F option with the Scratchbox installation script can do this.

==Installation procedure==

*Download the Scratchbox installer and the Maemo SDK installer scripts.

$ wget -c http://repository.maemo.org/stable/5.0/maemo-scratchbox-install_5.0.sh http://repository.maemo.org/stable/5.0/maemo-sdk-install_5.0.sh

*Set permissions to execute the scripts.

$ chmod a+x ./maemo-scratchbox-install_5.0.sh ./maemo-sdk-install_5.0.sh

Users of Ubuntu 10.04 LTS will need to do the following to fix the installation, note that this may reduce system security! [http://talk.maemo.org/showpost.php?p=636394&postcount=8]

$ sudo su
$ echo "vm.mmap_min_addr = 0" >> /etc/sysctl.conf
$ sysctl -p
$ exit #to go back to user

*Run the Scratchbox installer script as 'root user' with -F option, specifying the username to be added to Scratchbox users group sbox group as follows:

$ sudo ./maemo-scratchbox-install_5.0.sh -F -u $USER

*If you are running squeeze or intrepid or later, read [[#Limitations_of_Scratchbox]] before continuing.

Upon successful installation of Scratchbox, continue to run the Maemo 5 Final SDK Installer as instructed in the x86-32 installation.

=Starting Scratchbox on non-Debian based systems=
If Scratchbox was installed from Debian packages, the /etc/init.d/scratchbox-core init script is installed and Scratchbox should start automatically when the system is rebooted. However, if you have installed Scratchbox from tarballs, then rebooting your machine will clear away all the mounts and binfmt_misc registrations that Scratchbox requires to work. To get your Scratchbox working again after reboot, you have to run the following command as root:

$ sudo /scratchbox/sbin/sbox_ctl start

Alternatively you can add sbox_ctl as an init script to the /etc/init.d directory and create the appropriate links at your system's runlevel directories. This procedure works on some systems:

$ ln -s /scratchbox/sbin/sbox_ctl /etc/init.d/scratchbox-core
$ /usr/sbin/update-rc.d scratchbox-core defaults

Refer to your system's documentation for the correct instructions.

=Upgrading from Maemo 5 Beta2 SDK=

A smooth upgrade from beta2 to Final SDK is unfortunately not possible. Hence it is advised to freshly install the Final SDK. Before you do so, read through the instructions below.

Some of the Nokia applications shipped with the final SDK use a hard coded path for user home directory which presents a problem since the default username on the device differs from the username on the developer’s machine. To make these applications work, it is required to create a home directory that matches the hard coded value. This needs to be done outside scratchbox using root privileges. The -u option in the Scratchbox installer has been updated to create the necessary symlinks. Running the installer with -u option when the Scratchbox has been already installed will just add the user and create symlinks. Running it for already existing user will check for the symlink and create it if needed.

Run the command below to create the symlink for existing Scratchbox user:

$ sudo ./maemo-scratchbox-install_5.0.sh -u <EXISTING_USER>

Alternatively, you can create the symlinks manually as follows, if Scratchbox is installed in the default location:

$ sudo ln -s /scratchbox/users/<username>/home/<username> /scratchbox/users/<username>/home/user

The Final SDK installer additionally creates a directory /opt under /target/<target_name>/.
'''Reason:''' In order to facilitate installing applications under /opt on the device, a symlink /opt has been created pointing to /home/opt. The SDK inherits this feature. Under Scratchbox, /opt points to /target/links/opt which in turn points to /targets/<target_name>/opt. Installing the rootstraps makes this point to /home/opt, which is not what we want, since we need /opt to be target specific. In order to resolve this situation, we have to manually check whether /targets/<target_name>/opt is a symlink and if it is, remove it and create a directory with the same name.

=Upgrading from Maemo 4.x/Diablo SDK=
Due to the fact that there are API breaks in Fremantle, we cannot upgrade Diablo SDK to Fremantle. We can however have Fremantle Scratchbox targets co-exist with Diablo targets.

For this, we need to first upgrade the Scratchbox installation on our host machine.

*Download the Maemo5 scratchbox installer.

*Set executable permissions and run it as follows:

$ chmod a+x ./maemo-scratchbox-install_5.0.sh
$ sudo ./maemo-scratchbox-install_5.0.sh -U -u <EXISTING_USER> -s /scratchbox

Once the Scratchbox installation is done, run the Maemo 5 Final SDK installer.

=Manual Installation=

'''On x86-32 Debian based systems:'''

*You can add the following line into your host machine's /etc/apt/sources.list file.

deb http://scratchbox.org/debian/ maemo5-sdk main

*Install the needed Scratchbox packages with root permission

$ sudo apt-get update
$ sudo apt-get install scratchbox-core scratchbox-libs scratchbox-devkit-qemu scratchbox-devkit-debian scratchbox-devkit-doctools scratchbox-devkit-perl scratchbox-toolchain-host-gcc scratchbox-toolchain-cs2007q3-glibc2.5-arm7 scratchbox-toolchain-cs2007q3-glibc2.5-i486 scratchbox-devkit-svn scratchbox-devkit-git scratchbox-devkit-apt-https

'''On x86-64 Debian based systems:'''

*Download the Scratchbox packages from [http://scratchbox.org/download/files/sbox-releases/branches/apophis/r4/deb/ here].

*Force the installation of the x86-32 packages with root permission as follows:

$ sudo dpkg -i --force-architecture scratchbox-core scratchbox-libs scratchbox-devkit-qemu scratchbox-devkit-debian scratchbox-devkit-doctools scratchbox-devkit-perl scratchbox-toolchain-host-gcc scratchbox-toolchain-cs2007q3-glibc2.5-arm7 scratchbox-toolchain-cs2007q3-glibc2.5-i486 scratchbox-devkit-svn scratchbox-devkit-git scratchbox-devkit-apt-https

The Scratchbox packages will be unpacked to /scratchbox directory and the installation procedure will ask you some questions about the group and user accounts. Default group to Scratchbox is 'sbox'.

*Users who will be using Scratchbox should be added using the following command with root permission:

$ sudo /scratchbox/sbin/sbox_adduser USER yes

It will automatically include the user to the Scratchbox group, create user directories under /scratchbox/users and mount several directories (/dev, /proc, /tmp) under the user directory.

*Some of the Nokia applications shipped with the final SDK use a hard coded path for user home directory which presents a problem since the default username on the device differs from the username on the developer’s machine. To make these applications work, it is required to create a home directory that matches the hard coded value. This needs to be done outside scratchbox using root privileges.

$ sudo ln -s /scratchbox/users/<username>/home/<username> /scratchbox/users/<username>/home/user

*For the group membership to be effective in the current terminal session, run the following command:

$ newgrp sbox

'''Note:''' This command will change the existing group ID during the current login session to 'sbox'. If you do not want to change, simply logout and log back in for the group membership to be effective.

*Log-in to Scratchbox.

$ /scratchbox/login

*Configure the scratchbox x86 and armel targets as follows:

[sbox->:~]>sb-conf st FREMANTLE_X86 -c cs2007q3-glibc2.5-i486 -d perl:debian-etch:doctools:svn:git -t none
[sbox->:~]>sb-conf st FREMANTLE_ARMEL -c cs2007q3-glibc2.5-arm7 -d qemu:perl:debian-etch:doctools:svn:git -t qemu-arm-sb

*Download the minimal rootstraps.

[sbox->:~]> wget http://repository.maemo.org/stable/5.0/armel/maemo-sdk-rootstrap_5.0_armel.tgz http://repository.maemo.org/stable/5.0/i386/maemo-sdk-rootstrap_5.0_i386.tgz

*Switch to x86 target, install the devkits, etc and fakeroot into the target, install the minimal rootstrap and finally the Maemo development files.

[sbox->:~]> sb-conf se FREMANTLE_X86
[sbox-FREMANTLE_X86: ~] > sb-conf rs maemo-sdk-rootstrap_5.0_i386.tgz

*Some users seem to have problems downloading all files with apt http pipelining enabled. If you want to make sure or you get download errors like "104 connection reset by peer" at the fakeroot steps below, then disable http pipelining with the next command:
[sbox-FREMANTLE_X86: ~] > echo 'Acquire::http::Pipeline-Depth "0";' >> /etc/apt/apt.conf.d/00maemo

*either way, continue here:
[sbox-FREMANTLE_X86: ~] > sb-conf in -edFL
[sbox-FREMANTLE_X86: ~] > apt-get update
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install maemo-sdk-debug

The meta-package 'maemo-sdk-debug' installs all needed open source runtime, development and debug pakcages into the target. Use maemo-sdk-runtime if you want only runtime packages to be installed or user maemo-sdk-dev if you want only the runtime + development packages to be installed.

*Accept the EULA from [http://tablets-dev.nokia.com/eula/index.php here] to obtain the URL to access the Nokia binaries repository.

*Add the URL thus obtained to the Scratchbox target's /etc/apt/sources.list and do the following:

[sbox-FREMANTLE_X86: ~] >apt-get update
[sbox-FREMANTLE_X86: ~] >fakeroot apt-get install nokia-binaries nokia-apps

*In order to facilitate installing applications under /opt on the device, a symlink /opt has been created pointing to /home/opt. The SDK inherits this feature. Under Scratchbox, /opt points to /target/links/opt which in turn points to /targets/<target_name>/opt. Installing the rootstraps makes this point to /home/opt, which is not what we want, since we need /opt to be target specific. In order to resolve this situation,

[sbox-FREMANTLE_X86: ~] >rm /targets/FREMANTLE_X86/opt
[sbox-FREMANTLE_X86: ~] >mkdir /targets/FREMANTLE_X86/opt

*Execute similar steps on the armel target too to set it up:

[sbox-FREMANTLE_X86: ~]> sb-conf se FREMANTLE_ARMEL
[sbox-FREMANTLE_ARMEL: ~] > sb-conf rs maemo-sdk-rootstrap_5.0_armel.tgz

*again,the next command disables http pipelining, if you like:
[sbox-FREMANTLE_X86: ~] > echo 'Acquire::http::Pipeline-Depth "0";' >> /etc/apt/apt.conf.d/00maemo

*pipelining disabled or not, here we go again...
[sbox-FREMANTLE_ARMEL: ~] > sb-conf in -edFL
[sbox-FREMANTLE_ARMEL: ~] > apt-get update
[sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install maemo-sdk-debug

*Add the same URL obtained above to access the Nokia binaries repository under /etc/apt/sources.list file of the Scratchbox armel target.

[sbox-FREMANTLE_ARMEL: ~] >apt-get update
[sbox-FREMANTLE_ARMEL: ~] >fakeroot apt-get install nokia-binaries nokia-apps

*Create the /opt directory.

[sbox-FREMANTLE_ARMEL: ~] >rm /targets/FREMANTLE_ARMEL/opt
[sbox-FREMANTLE_ARMEL: ~] >mkdir /targets/FREMANTLE_ARMEL/opt

With this, you must now have both the targets setup and ready to use.

[[#Starting/Shutting down the SDK UI|Start the UI framework]].

=Un-installation=

Make sure that you have no process running inside Scratchbox. Uninstalling Scratchbox will remove everything that is installed and saved inside Scratchbox. Please take a backup of your files from Scratchbox user home directory if needed.

On Debian based systems, do the following with root permissions:

$ sudo apt-get remove scratchbox-* --purge
$ sudo rm -rf /scratchbox

On non-Debian based systems, you need to stop scratchbox as follows before removing it.

$ sudo /scratchbox/sbin/sbox_ctl stop
$ sudo rm -rf /scratchbox

=Limitations of Scratchbox=

The following limitations have been noted in the usage of Scratchbox:

==VDSO support==
Scratchbox does not work when VDSO32 support is enabled in the host's kernel. We're working on making it possible, but at the moment there are some workarounds, which are presented here.

If your host has VDSO32 turned on you will get an error like this when trying to login to Scratchbox.

No directory, logging in with HOME=/
Inconsistency detected by ld.so: rtld.c: 1192: dl_main: Assertion `(void *)
ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed!

==x86-64 kernel==

x86-64 Linux kernels starting from version 2.6.25 enable VDSO32 by default. To temporarily disable VDSO32 execute

sysctl abi.vsyscall32=0

On Linux kernel 2.6.24 <= you can disable VDSO32 by executing

sysctl vm.vdso_enabled=0

or

sysctl kernel.vdso=0

The current setting of VDSO32 can be verified by using sysctl. Only values 0 and 2 are compatible with Scratchbox. In our examples we use 0 (disable). 2 enables compat mode.

You can set all of these permanently by adding the following lines to /etc/sysctl.conf

vm.vdso_enabled = 0
abi.vsyscall32 = 0
kernel.vdso = 0

Save the file and run the command:

$ sudo sysctl -p

Please note the correct line depends on your Linux kernel version. When you execute sysctl -p you may get a warning about unknown keys. You can safely ignore those warnings as long as one of the 3 settings works.

'''WARNING :''' You should try setting these values by echoing them to the given locations before adding them to sysctl.conf to see if they cause any problems. For example, in some Ubuntu Gutsy installations, it has been observed that changing the VDSO settings will hang the system and thus making permanent changes in sysctl.conf may, in these cases, make your system unbootable.

=Known Issues in the SDK=

*A list of issues and their solutions can be found in the [[Developer_FAQ#Maemo_SDK_and_Scratchbox|Developer FAQ]] article

*Unnecessary warnings and debugging messages are printed out when the hildon application framework is started.

*Armel target does not bring up the UI framework

*It has been noted that Xephyr dies with the application framework at times. The crash in question might even be Xephyr related since the application framework behaves differently with different versions/builds of Xephyr. The case seems to be worst on Xephyr that comes with Ubuntu Jaunty, there Xephyr will die when running any application that contains an input field and clicking on that field with a mouse to invoke the input method. On Fedora Code 10 the Xephyr does not mind the mouse clicks but dies when shutting down the application framework. On the other hand Xephyr on Ubuntu Intrepid or even the Intrepid version recompiled for Jaunty does not experience crashing in these situations.

A patch is already available for the Xephyr on Ubuntu Jaunty and can be found at http://bugs.freedesktop.org/show_bug.cgi?id=21591. Binaries packages for [http://launchpadlibrarian.net/30330126/xserver-xephyr_1.6.3-1ubuntu2_i386.deb xserver-xephyr] package and its dependencies ([http://launchpadlibrarian.net/27533744/libgpg-error0_1.6-1ubuntu1_i386.deb libgpg-error0] and [http://launchpadlibrarian.net/28623981/libgcrypt11_1.4.4-2ubuntu2_i386.deb libcrypt11]) can be download from Ubuntu Jaunty repositories.

*The performance of clutter can be improved by enabling hardware acceleration if not enabled already. In some cases, it would require installing restricted/proprietary drivers (Eg: on host machines with ATI or NVidia graphics card). Refer to [[Maemo5 clutter performance]] for more details.

*Running Xephyr with -kb option disables entry of “@” symbol. However, removing -kb option disables cursor keys.

*Running Xephyr with -host-cursor is causing Xephyr to crash in Ubuntu Lucid and Debian Squeeze when the Hildon Application Framework is closed.

*Xephyr in Ubuntu Lucid does not support the -kb option anymore. https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/531872

*In order to run ARMEL binaries in scratchbox the mmap_min_address needs to be set to 4096. Normally the SDK installer warns about that, but in Ubuntu Lucid the /proc entry is visible only to root, so the SDK installer can not see it. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/568844

[[Category:Scratchbox]]

Maemo 5/PR1.2

2010-05-26T09:50:05Z

192.100.124.219: /* New Features */

{{Firmware update}}

[[Maemo 5/PR1.1.1|PR 1.1.1]] was the preparatory release for PR1.2, which should be [http://conversations.nokia.com/2010/05/25/nokia-n900-software-update-release-1-2/ released on May 25/26, 2010].

The Maemo 5/PR1.2 SDK and tools has been updated on March 22nd, 2010 in order to give the developers time to adapt to the new firmware update and Qt 4.6.

= New Features =
* Skype video call (with PC and other skype video capable clients)
* Gtalk video call (with gtalk PC web client or other gtalk video capable clients like N900, N810, N800 etc., or GNOME desktop client). In general, with any xmpp video call capable client.
* SIP video call (with supported SIP video call clients)
* Skype multiuser chat
* Qt 4.6.2 is now preinstalled on the OS.
* Changes for the video recording in the Camera Application.
* Video calling can be accessed through contacts (skype and gtalk).
* Can dial USSD Codes.
* SS codes dialing available as ester egg (go figure).
* No more "More" menu in application launcher, and is rearrangeable.
* Virtual Keyboard has been modified and now looks different.
* File Manager is now able to share any file and/or folder.
* Typing in Application Manager starts a search (like it is in Contacts or Media Player).
* Status area is now reachable in portrait mode (not working here...)
* <s>Portrait mode Virtual Keyboard for browser. *Not yet confirmed* [http://talk.maemo.org/showpost.php?p=583355&postcount=206 (Source)]</s>

= Resolved bugs =

Please note that this list is not necessarily complete.

See [https://bugs.maemo.org/buglist.cgi?classification=Maemo%20Official%20Applications&classification=Maemo%20Official%20Platform&resolution=FIXED&target_milestone=5.0%2F%28PR1.2%29&order=map_products.name%2Cbugs.bug_id this] query for more accurate/up-to-date report.

== maemo.org Official Applications: ==

=== Browser ===
* [https://bugs.maemo.org/show_bug.cgi?id=1800 tapping browser rss icon lists two RSS feeds, one from an iframe]
* [https://bugs.maemo.org/show_bug.cgi?id=1801 tapping browser rss icon should list ATOM feed, not just RSS]
* [https://bugs.maemo.org/show_bug.cgi?id=5485 ""restart"" button after finishing download not localized (in Finnish)]
* [https://bugs.maemo.org/show_bug.cgi?id=5526 Type-to-find behaviour is inconsistent and suboptimal in browser]
* [https://bugs.maemo.org/show_bug.cgi?id=5684 History images do not match actual URLs under them]
* [https://bugs.maemo.org/show_bug.cgi?id=5705 Browser drawing issue in web pages with (multiple?) Flash applets]
* [https://bugs.maemo.org/show_bug.cgi?id=5783 Smooth scrolling not active using arrow keys until current page tapped]
* [https://bugs.maemo.org/show_bug.cgi?id=5829 ""Select user name"" dialog not finger friendly]
* [https://bugs.maemo.org/show_bug.cgi?id=5945 URL proposals in browser disappear after some hours]
* [https://bugs.maemo.org/show_bug.cgi?id=6066 Sticky shift & Fn not working for Flash text input fields: Impossible to use special characters palette]
* [https://bugs.maemo.org/show_bug.cgi?id=6184 Find on page causes page to reload]
* [https://bugs.maemo.org/show_bug.cgi?id=6269 Can't reuse the name of a bookmark that has been deleted]
* [https://bugs.maemo.org/show_bug.cgi?id=6342 Use Volume hardware key for adjust the device volume instead of zooming a website]
* [https://bugs.maemo.org/show_bug.cgi?id=6396 Zooming is not working right away when link clicked from desktop]
* [https://bugs.maemo.org/show_bug.cgi?id=6598 Browser should display passwords one character at a time like other applications]
* [https://bugs.maemo.org/show_bug.cgi?id=6743 Screen sometimes flickers when scrolling through bookmarks triggers rubber banding]
* [https://bugs.maemo.org/show_bug.cgi?id=6819 High CPU usage for 15 seconds after page loaded (Deleting History helps)]
* [https://bugs.maemo.org/show_bug.cgi?id=7174 specifying ""DejaVu Sans Mono"",""Courier New"",monospace,Freemono fonts break pre]
* [https://bugs.maemo.org/show_bug.cgi?id=7235 g_mozilla_parse_env_proxy limits proxy server names to about 20 characters [http_proxy]]
* [https://bugs.maemo.org/show_bug.cgi?id=7335 Browser shows strong font kerning bugs (esp. when zooming)]
* [https://bugs.maemo.org/show_bug.cgi?id=7445 mobile4arab.com: After zooming in, sometimes cannot drag to the right side]
* [https://bugs.maemo.org/show_bug.cgi?id=7566 Browser toolbar steals text focus in fullscreen mode when ""Auto focus address field"" is enabled]
* [https://bugs.maemo.org/show_bug.cgi?id=7567 Browser toolbar steals text focus in fullscreen mode with remapped arrow keys]
* [https://bugs.maemo.org/show_bug.cgi?id=7568 Sites in history overview that were loaded in portrait mode appear distorted]
* [https://bugs.maemo.org/show_bug.cgi?id=7620 Browser process opens ports on all interfaces.]
* [https://bugs.maemo.org/show_bug.cgi?id=7806 Browser crashes while sending a comment to Maemo.org]
* [https://bugs.maemo.org/show_bug.cgi?id=7890 Clicking on webcal:// link does nothing (not even an error dialog)]
* [https://bugs.maemo.org/show_bug.cgi?id=8010 browser repaints after switching from contacts]
* [https://bugs.maemo.org/show_bug.cgi?id=8091 Press and hold in Browser portrait mode does nothing]
* [https://bugs.maemo.org/show_bug.cgi?id=8104 Browser portrait mode makes it stop working after a while]
* [https://bugs.maemo.org/show_bug.cgi?id=8117 Browser doesn't show progress indicator when user selects url from urlbar completion list]
* [https://bugs.maemo.org/show_bug.cgi?id=8252 Browser addressbar refreshes/blanks shortly after new window opens]
* [https://bugs.maemo.org/show_bug.cgi?id=8276 Imported SSL Certificates not recognized after PR1.1]
* [https://bugs.maemo.org/show_bug.cgi?id=8362 Some combination of Maemo 5 + Nokia N900 results in improper onChange callbacks in the maemo browser]
* [https://bugs.maemo.org/show_bug.cgi?id=8385 New browser windows' contents are not updated when page loads in background]
* [https://bugs.maemo.org/show_bug.cgi?id=8601 Provide UI to enable/disable portrait mode]
* [https://bugs.maemo.org/show_bug.cgi?id=8606 Cannot scroll web bookmark folders if more than 5 folders]
* [https://bugs.maemo.org/show_bug.cgi?id=8683 Browser crashes when browsing some websites]
* [https://bugs.maemo.org/show_bug.cgi?id=8763 Back yields grayed page]
* [https://bugs.maemo.org/show_bug.cgi?id=8784 Browser crashes while changing system theme]
* [https://bugs.maemo.org/show_bug.cgi?id=8920 MicroB loses first keystroke]
* [https://bugs.maemo.org/show_bug.cgi?id=9362 Page view ""unstable"" (due to animated GIFs?)]
* [https://bugs.maemo.org/show_bug.cgi?id=9365 Maemo Browser does not honor CSS serif font specifications]
* [https://bugs.maemo.org/show_bug.cgi?id=9460 Disable show images leads to failure in opening links in a new window]
* [https://bugs.maemo.org/show_bug.cgi?id=9555 Only the address bar is visible on the bottom panel]
* [https://bugs.maemo.org/show_bug.cgi?id=9566 Browser doesn't stop flash or another plugins while device is locked]
* [https://bugs.maemo.org/show_bug.cgi?id=9926 No more search results loads new page]
* [https://bugs.maemo.org/show_bug.cgi?id=10101 browser: incorrect display then internal error (double access to the same buffer)]

=== Calendar ===
* [https://bugs.maemo.org/show_bug.cgi?id=6431 Alarm setting for Birthday is removed after adding photo to contact]
* [https://bugs.maemo.org/show_bug.cgi?id=6687 Calendar (and Calendar desktop Widget) can take up to 30 seconds to become responsive when a lot of Smart Calendar items are present]
* [https://bugs.maemo.org/show_bug.cgi?id=6909 Calendar launches automatically at 4:00 each night]
* [https://bugs.maemo.org/show_bug.cgi?id=8169 exported .ics calendars have bad line format (LF for empty lines)]
* [https://bugs.maemo.org/show_bug.cgi?id=8175 Exported calendars lack PRODID properties]
* [https://bugs.maemo.org/show_bug.cgi?id=8332 Day View doesn't display synced events with complex uneditable repeats]
* [https://bugs.maemo.org/show_bug.cgi?id=8448 tasks also displayed as notes]
* [https://bugs.maemo.org/show_bug.cgi?id=8463 libcalendar produces AALARM properties containing unescaped CRLF which prevents OSX synchronisation]
* [https://bugs.maemo.org/show_bug.cgi?id=8481 notes imported without DTSTART fields are not displayed]
* [https://bugs.maemo.org/show_bug.cgi?id=8678 Overdue tasks should be displayed as today's]
* [https://bugs.maemo.org/show_bug.cgi?id=8889 New event in calendar causes crash when using bg_BG locales]
* [https://bugs.maemo.org/show_bug.cgi?id=9048 ""Internal Error: Application 'Calendar' closed when importing ics file]

=== Chat & Call & SMS ===
* [https://bugs.maemo.org/show_bug.cgi?id=5357 Does not accept GSM (USSD) Codes starting with *#]
* [https://bugs.maemo.org/show_bug.cgi?id=6016 Can't see the number an SMS was sent to]
* [https://bugs.maemo.org/show_bug.cgi?id=6201 libnice violates Debian packaging policy for description of package ""libnice0""]
* [https://bugs.maemo.org/show_bug.cgi?id=6300 :/ in http:// is converted into an emoticon in some cases]
* [https://bugs.maemo.org/show_bug.cgi?id=6641 Sofia-SIP throws 500 Internal Server Error]
* [https://bugs.maemo.org/show_bug.cgi?id=6692 Unable to set a Google Talk account to Away]
* [https://bugs.maemo.org/show_bug.cgi?id=6733 gmail status set to away when skype status set to invisible]
* [https://bugs.maemo.org/show_bug.cgi?id=6769 Can't answer a phone call with a short caller ID]
* [https://bugs.maemo.org/show_bug.cgi?id=6857 USSD codes are not recognized in chat]
* [https://bugs.maemo.org/show_bug.cgi?id=6936 Caller voice gets minced after some time when taking call via SIP]
* [https://bugs.maemo.org/show_bug.cgi?id=7052 Unable to see the sender's phone number used for a received sms]
* [https://bugs.maemo.org/show_bug.cgi?id=7212 Sent text messages are shown as unsent]
* [https://bugs.maemo.org/show_bug.cgi?id=7227 Contact names do not resolve correctly when country code is prefixed.]
* [https://bugs.maemo.org/show_bug.cgi?id=7361 Make a phone call to a contact from the sms view]
* [https://bugs.maemo.org/show_bug.cgi?id=7375 account-plugin-butterfly - delete contacts doesn't work]
* [https://bugs.maemo.org/show_bug.cgi?id=7470 N900 does not support Skype Voicemail Settings]
* [https://bugs.maemo.org/show_bug.cgi?id=7856 Recent Call entries are shown in conversations]
* [https://bugs.maemo.org/show_bug.cgi?id=7886 Tapping 'Task Manager' shows 'Clear Conversation' option while in a conversation]
* [https://bugs.maemo.org/show_bug.cgi?id=7933 Conversation IM window is not responding when Select contact dialog is displayed in background]
* [https://bugs.maemo.org/show_bug.cgi?id=7952 GTalk contact offline text is shown in conversion even if contact is back online]
* [https://bugs.maemo.org/show_bug.cgi?id=8082 Voice can be heard only one way with Saunalahti Nettipuhelin]
* [https://bugs.maemo.org/show_bug.cgi?id=8428 Carrier doesn't stop attempting to send USSD codes that aren't received (automated balance receipt)]
* [https://bugs.maemo.org/show_bug.cgi?id=8441 Messages don't change to ""read"" status after being read]
* [https://bugs.maemo.org/show_bug.cgi?id=8454 Placing a call in portrait mode gets desktop stuck in portrait mode upon exit.]
* [https://bugs.maemo.org/show_bug.cgi?id=8573 Conversation doesn't respect aspect ratio in avatars]
* [https://bugs.maemo.org/show_bug.cgi?id=8581 Reduce XMPP data packets to save battery]
* [https://bugs.maemo.org/show_bug.cgi?id=8854 Jabber opens unnecessary proxy connections]
* [https://bugs.maemo.org/show_bug.cgi?id=8954 SMS Sort/Filter/Search does not allow numbers to be entered (Fn key does not work beyond first digit)]
* [https://bugs.maemo.org/show_bug.cgi?id=8958 portrait layout for receiving call shown in landscape mode (-> no Reject button)]
* [https://bugs.maemo.org/show_bug.cgi?id=9005 XMPP lacks option to require TLS (vulnerable to MITM attacks)]
* [https://bugs.maemo.org/show_bug.cgi?id=9231 Open contact card' broken for newly sent SMS]
* [https://bugs.maemo.org/show_bug.cgi?id=9243 Telephony uses 100% CPU for video call (using Google Talk)]
* [https://bugs.maemo.org/show_bug.cgi?id=9501 Phone UI not rotating to portrait mode]
* [https://bugs.maemo.org/show_bug.cgi?id=9973 SIP account can not be re-activated]

=== Contacts ===
* [https://bugs.maemo.org/show_bug.cgi?id=2962 Not able to open Maps application with contacts location as a search string]
* [https://bugs.maemo.org/show_bug.cgi?id=5510 Contact merge of number dialed manually via Skype fails due to internal error]
* [https://bugs.maemo.org/show_bug.cgi?id=5742 Contacts: Provide ""Fax"" field(s)]
* [https://bugs.maemo.org/show_bug.cgi?id=6375 Provides SMS buttons for ""Phone"" entries and not only ""Mobile"" entries]
* [https://bugs.maemo.org/show_bug.cgi?id=6503 only 2 Lines of Notes are visible in Contacts]
* [https://bugs.maemo.org/show_bug.cgi?id=6945 Skype: merged contact has duplicate phone number]
* [https://bugs.maemo.org/show_bug.cgi?id=7515 List of countries not shown on tapping the country picker button]
* [https://bugs.maemo.org/show_bug.cgi?id=8022 Making a SIP call crashes osso-addressbook]
* [https://bugs.maemo.org/show_bug.cgi?id=8159 Missing direct shortcut to use SIP/Skype again in Recent Calls list]
* [https://bugs.maemo.org/show_bug.cgi?id=8495 ""SIP audio"" buttons active with no SIP accounts active]
* [https://bugs.maemo.org/show_bug.cgi?id=9010 Merging contacts, unable to select neither as an option in conflict field]

=== Desktop Widgets ===
* [https://bugs.maemo.org/show_bug.cgi?id=5331 Add AVRCP support to the Media Player widget (and system-wide?)]
* [https://bugs.maemo.org/show_bug.cgi?id=5894 Play track button doesn't work]
* [https://bugs.maemo.org/show_bug.cgi?id=6748 Small line visible below media player widget]
* [https://bugs.maemo.org/show_bug.cgi?id=6907 Media Player widget suddenly starts music after Phone call ends]
* [https://bugs.maemo.org/show_bug.cgi?id=7996 Media player's desktop widget displays wrong metadata of internet radios]
* [https://bugs.maemo.org/show_bug.cgi?id=8002 Being offline, RSS Reader tries to connect for refresh unconditionally]

=== Email ===
* [https://bugs.maemo.org/show_bug.cgi?id=2582 Option to download messages but not attachments (""Messages only"")]
* [https://bugs.maemo.org/show_bug.cgi?id=2922 Want ability to delete POP mail from server]
* [https://bugs.maemo.org/show_bug.cgi?id=3387 Modest doesn't fetch GMX IMAP mail (issuing LIST """" instead of LIST ""*"")]
* [https://bugs.maemo.org/show_bug.cgi?id=4211 There should be a desktop widget for mail (like rss)]
* [https://bugs.maemo.org/show_bug.cgi?id=4834 Remove deprecated GTK+ symbols]
* [https://bugs.maemo.org/show_bug.cgi?id=4876 Remove libgnomeui dependency]
* [https://bugs.maemo.org/show_bug.cgi?id=4887 Use accessor functions instead direct access]
* [https://bugs.maemo.org/show_bug.cgi?id=4889 Use single GTK+ includes]
* [https://bugs.maemo.org/show_bug.cgi?id=4973 Support silent build rules with automake 1.11]
* [https://bugs.maemo.org/show_bug.cgi?id=4976 Add option in modest to add/not add new contact when replying to mail]
* [https://bugs.maemo.org/show_bug.cgi?id=5033 Select/Copy text within email is nonintuitive/broken]
* [https://bugs.maemo.org/show_bug.cgi?id=5161 Fix some compilation warnings in GNOME version]
* [https://bugs.maemo.org/show_bug.cgi?id=5266 Remove unneeded modest_osso_load_state () calls]
* [https://bugs.maemo.org/show_bug.cgi?id=5267 Remove unused modest-osso-autosave-callbacks.c/h files]
* [https://bugs.maemo.org/show_bug.cgi?id=5341 Can't disable email notification - makes notification unusable if you receive lots of mail]
* [https://bugs.maemo.org/show_bug.cgi?id=5417 Delete button greyed out when opening from notification popup]
* [https://bugs.maemo.org/show_bug.cgi?id=5503 Failed outgoing mails when using Nokia Messaging and Exchange]
* [https://bugs.maemo.org/show_bug.cgi?id=5634 Deleted IMAP messages are not expunged]
* [https://bugs.maemo.org/show_bug.cgi?id=5836 POP3 TCP connection is left open leading to locking issues]
* [https://bugs.maemo.org/show_bug.cgi?id=5870 Long emails can't be read - distorted output on screen after scrolling]
* [https://bugs.maemo.org/show_bug.cgi?id=6027 Only require libmodest-dbus-client in maemo platform]
* [https://bugs.maemo.org/show_bug.cgi?id=6048 Volume hardware key works only once; afterwards ""Unable to zoom"" in list of mail accounts, list of mail folders, New Mail editor]
* [https://bugs.maemo.org/show_bug.cgi?id=6279 Modest is very slow at loading images]
* [https://bugs.maemo.org/show_bug.cgi?id=6541 Polish Subject line violates RFC (""Odp."" prefix)]
* [https://bugs.maemo.org/show_bug.cgi?id=6570 Double-tapping ""Inbox"" sometimes opens 'empty' Inbox]
* [https://bugs.maemo.org/show_bug.cgi?id=6575 Tapping new Email notification does not bring up email message]
* [https://bugs.maemo.org/show_bug.cgi?id=6700 Semicolon in To field should be ignored when sending a message]
* [https://bugs.maemo.org/show_bug.cgi?id=6702 email application does not see folders on imap4 with namespace]
* [https://bugs.maemo.org/show_bug.cgi?id=7139 Replying to an email with non-ascii chars in From cuts name short]
* [https://bugs.maemo.org/show_bug.cgi?id=7485 Email message viewer window refreshes a second time when email opened from Notification icon]
* [https://bugs.maemo.org/show_bug.cgi?id=7701 Arabic language not shown or encoded in Modest]
* [https://bugs.maemo.org/show_bug.cgi?id=7718 Unable to save attachment from e-mail without e-mail body]
* [https://bugs.maemo.org/show_bug.cgi?id=8230 cannot move message anywhere]
* [https://bugs.maemo.org/show_bug.cgi?id=8574 Subfolders of Zimbra IMAP server not appearing/not available]
* [https://bugs.maemo.org/show_bug.cgi?id=8604 Type-to-find behaviour is inconsistent and suboptimal in modest]
* [https://bugs.maemo.org/show_bug.cgi?id=10108 hyperlinks in email program terminates on &]

=== Games ===
* [https://bugs.maemo.org/show_bug.cgi?id=3748 Erroneous ""Game not started yet"" message]
* [https://bugs.maemo.org/show_bug.cgi?id=5276 hildon-games-wrapper crashes in hgw_conf_request_string if gconf key has no value]
* [https://bugs.maemo.org/show_bug.cgi?id=5868 Games do not respect master volume (""sound effects"" enabled though)]
* [https://bugs.maemo.org/show_bug.cgi?id=5869 Chess game over dialog button is unreadable in some themes]
* [https://bugs.maemo.org/show_bug.cgi?id=6616 Mahjong: Łamigłówka (Confounding cross) does not display high score time in Polish]

=== Images and Camera ===
* [https://bugs.maemo.org/show_bug.cgi?id=4053 Confusing behaviour when saving to a file that matches an existing directory]
* [https://bugs.maemo.org/show_bug.cgi?id=6194 Shutter release button does not always work]
* [https://bugs.maemo.org/show_bug.cgi?id=6372 Sometimes photos are not deleted if you delete directly after taking them]
* [https://bugs.maemo.org/show_bug.cgi?id=7060 Sometimes photos are very green]
* [https://bugs.maemo.org/show_bug.cgi?id=7160 Camera app hardcodes and requires FAT partition]
* [https://bugs.maemo.org/show_bug.cgi?id=7394 Some photos are missing EXIF DateTimeOriginal data]
* [https://bugs.maemo.org/show_bug.cgi?id=7559 Old image displayed as a new one when swiping]
* [https://bugs.maemo.org/show_bug.cgi?id=7758 Daily image counter in photo filenames not incrementing in some cases]
* [https://bugs.maemo.org/show_bug.cgi?id=8087 Photo autorotation issue]
* [https://bugs.maemo.org/show_bug.cgi?id=8310 Image Viewer shows only black screen]
* [https://bugs.maemo.org/show_bug.cgi?id=8698 camera does not have the night mode function]
* [https://bugs.maemo.org/show_bug.cgi?id=8877 Volume buttons should work in camera window when lens cover is not opened]

=== Map ===
* [https://bugs.maemo.org/show_bug.cgi?id=5337 Ovi Maps gives up finding GPS lock too soon]
* [https://bugs.maemo.org/show_bug.cgi?id=5391 Virtual keyboard doesn't appear in Maps]
* [https://bugs.maemo.org/show_bug.cgi?id=5905 ovi maps brings up ""Select connection"" dialog relentlessly]
* [https://bugs.maemo.org/show_bug.cgi?id=8850 Ovi Maps search history]
* [https://bugs.maemo.org/show_bug.cgi?id=9532 Search: can input numbers and other ""blue"" characters only with -holding- ""alt"" key]

=== Media player ===
* [https://bugs.maemo.org/show_bug.cgi?id=5318 Missing ""Remove from Playlist"" option]
* [https://bugs.maemo.org/show_bug.cgi?id=5319 Ugly ""now playing"" animation]
* [https://bugs.maemo.org/show_bug.cgi?id=5522 Plays next radio station when current station cuts out / has playback issues]
* [https://bugs.maemo.org/show_bug.cgi?id=5805 Album art disappears when next song is played and you unlock the device]
* [https://bugs.maemo.org/show_bug.cgi?id=6067 Media player becomes unusable if a dialog is open when opening a stream link from browser]
* [https://bugs.maemo.org/show_bug.cgi?id=6823 media player won't play any video files now (.avi) divx / xvid]
* [https://bugs.maemo.org/show_bug.cgi?id=7124 media player loses cover art if song changes while screen is locked]
* [https://bugs.maemo.org/show_bug.cgi?id=7211 ""Unable to play media. Media format not supported"" for recently recorded video]
* [https://bugs.maemo.org/show_bug.cgi?id=7353 RDS station name should not contain album (esp. when its unknown)]
* [https://bugs.maemo.org/show_bug.cgi?id=7464 mediaplayer treats youtube mp4 urls as audio streams]
* [https://bugs.maemo.org/show_bug.cgi?id=7536 Can't search album titles (GtkIconView) by typing on keyboard]
* [https://bugs.maemo.org/show_bug.cgi?id=7634 Media player volume bar doesn't work when a browser with youtube played is opened in background.]
* [https://bugs.maemo.org/show_bug.cgi?id=7802 Media Player Streaming: Elapsed time advances by 1sec when playback is paused and reduced by 1sec when the playback is resumed.]
* [https://bugs.maemo.org/show_bug.cgi?id=7995 Internet radio (ogg) stream metadata not displayed]
* [https://bugs.maemo.org/show_bug.cgi?id=8035 Selecting song in media player doesn't cause song to play]
* [https://bugs.maemo.org/show_bug.cgi?id=8043 AVI Streaming broken. Local playback works fine.]
* [https://bugs.maemo.org/show_bug.cgi?id=8050 Media Player displays stop button during the playback of an AAC stream. It should display pause button.]
* [https://bugs.maemo.org/show_bug.cgi?id=8189 Strange black box icon in media player's album list]
* [https://bugs.maemo.org/show_bug.cgi?id=8438 Media player playlist icon when not playing is difficult to notice]
* [https://bugs.maemo.org/show_bug.cgi?id=8499 Music stops when ""low battery"" hildon banner is displayed]
* [https://bugs.maemo.org/show_bug.cgi?id=8525 Media Player is not playing WMV Video streams but KMPlayer can]
* [https://bugs.maemo.org/show_bug.cgi?id=8653 Media Player crashed when viewing UPNP contents.]
* [https://bugs.maemo.org/show_bug.cgi?id=9020 Media player crashes when trying to search in ''All songs'']
* [https://bugs.maemo.org/show_bug.cgi?id=9084 Media Player bridge_work-que battery drain]
* [https://bugs.maemo.org/show_bug.cgi?id=9182 No video shown, only audio, when streaming over upnp]
* [https://bugs.maemo.org/show_bug.cgi?id=9308 Media Player doesn't allow to search russian tags]
* [https://bugs.maemo.org/show_bug.cgi?id=9809 Scrolling animation on jump-to-song is too CPU heavy]

=== RSS feed reader ===
* [https://bugs.maemo.org/show_bug.cgi?id=304 Automatic proxy configuration URL not obeyed by RSS feed reader]
* [https://bugs.maemo.org/show_bug.cgi?id=5625 Feed list (Folder tree) uses non-finger friendly classic scrollbars]

=== Settings and Maintenance ===
* [https://bugs.maemo.org/show_bug.cgi?id=5546 In Certificate manager, ""Authorities"" title is shown two times]
* [https://bugs.maemo.org/show_bug.cgi?id=5560 Application manager shows ""ai_ib_unable_edit"" instead of proper, localised string when it has a repository of which it cannot change the details of]
* [https://bugs.maemo.org/show_bug.cgi?id=5746 symlink /var/cache/apt/archives to /home/apt-archives]
* [https://bugs.maemo.org/show_bug.cgi?id=6392 Unable to filter/search applcations' name in Application Manager]
* [https://bugs.maemo.org/show_bug.cgi?id=7446 Unlocking SIM card from control panel fails]
* [https://bugs.maemo.org/show_bug.cgi?id=7483 ""Enter code for unlocking SIM card"" button visible even if phone is not SIM locked]
* [https://bugs.maemo.org/show_bug.cgi?id=8194 General locale settings for new users does not set the correct locale for text input]
* [https://bugs.maemo.org/show_bug.cgi?id=8696 Search results window is not responding when search dialog is displayed in background]
* [https://bugs.maemo.org/show_bug.cgi?id=9229 Upgrade from PR1.1 to PR1.1.1 produces 'Operation failed' error]
* [https://bugs.maemo.org/show_bug.cgi?id=9621 Cannot perform a new search after an initial search in Uninstall section]
* [https://bugs.maemo.org/show_bug.cgi?id=9738 Popup ""Search complete"" blocks view, not useful]
* [https://bugs.maemo.org/show_bug.cgi?id=9794 Missing a searchfunction to select Ringtone]

=== Utilities ===
* [https://bugs.maemo.org/show_bug.cgi?id=4852 Remove Scratchboxism in wpeditor packaging]
* [https://bugs.maemo.org/show_bug.cgi?id=5300 Support sending files via Bluetooth in file manager]
* [https://bugs.maemo.org/show_bug.cgi?id=5810 automatically update date/time did not update after plane journey]
* [https://bugs.maemo.org/show_bug.cgi?id=5824 Maximum number of pseudo terminals too low (4)]
* [https://bugs.maemo.org/show_bug.cgi?id=6351 Context menu isn't thumbable/hildonized - options too small]
* [https://bugs.maemo.org/show_bug.cgi?id=6481 Buenos Aires, Argentina time off by 1 hour]
* [https://bugs.maemo.org/show_bug.cgi?id=6553 Calculator should remember mode setting]
* [https://bugs.maemo.org/show_bug.cgi?id=6882 Deletes file to move if destination filename already exists and choosing to not overwrite]
* [https://bugs.maemo.org/show_bug.cgi?id=8115 Having a modal dialog in background, Alarm dialog blocks entire UI => battery removal]
* [https://bugs.maemo.org/show_bug.cgi?id=8198 FIle manager should filter view if somethings is written on the keyboard]

== maemo.org Official Platform: ==

=== Connectivity ===
* [https://bugs.maemo.org/show_bug.cgi?id=1635 Eduroam (EAP-TTLS+PAP) WiFi auth]
* [https://bugs.maemo.org/show_bug.cgi?id=4789 ipctest.c input_cb seems to pass a reference to a freed pointer to sscanf]
* [https://bugs.maemo.org/show_bug.cgi?id=5550 ""Not enough memory in target location"" when receiving image from Nokia SU-1B using Bluetooth]
* [https://bugs.maemo.org/show_bug.cgi?id=6502 Control Panel: Cannot change Network mode when Network selection is ""Automatic""]
* [https://bugs.maemo.org/show_bug.cgi?id=7843 BH-103 - Annoying Beeps when calling or receiving a phone call or SMS]
* [https://bugs.maemo.org/show_bug.cgi?id=8004 PR1.1 has introduced a battery drain bug (not wifi related)]
* [https://bugs.maemo.org/show_bug.cgi?id=8133 dnsmasq segfaults when connecting to a certain WLAN AP]
* [https://bugs.maemo.org/show_bug.cgi?id=9057 Wifi wont connect to Dlink DI-524 using WEP]
* [https://bugs.maemo.org/show_bug.cgi?id=9117 Wrong IAP set for SFR (France)]
* [https://bugs.maemo.org/show_bug.cgi?id=9272 TDC (Denmark) GPRS settings are ""incorrect"" (or could be better)]
* [https://bugs.maemo.org/show_bug.cgi?id=9662 DHCP with redundant Gateway does not configure any routes]

=== Core ===
* [https://bugs.maemo.org/show_bug.cgi?id=5712 Ad-hoc wifi leaks kernel memory, puts N900 into unusable swap hell]
* [https://bugs.maemo.org/show_bug.cgi?id=5917 Not possible to answer incoming call with wired headset buttons.]
* [https://bugs.maemo.org/show_bug.cgi?id=6088 Very low touchscreen sensivitivity in the area near the left edge of the screen]
* [https://bugs.maemo.org/show_bug.cgi?id=6176 bashism in bash uninstall script causes busybox error]
* [https://bugs.maemo.org/show_bug.cgi?id=6450 libglslcompiler crashes when fragment shader contains a for-loop]
* [https://bugs.maemo.org/show_bug.cgi?id=7029 Device reboots when trying to connect to WIFI due to Oops in rate_control_get_rate()]
* [https://bugs.maemo.org/show_bug.cgi?id=8268 Unable to authenticate on light.webmoney.ru with user's SSL certificate.]
* [https://bugs.maemo.org/show_bug.cgi?id=9577 Reboot caused by bluetooth probe]
* [https://bugs.maemo.org/show_bug.cgi?id=9688 GL textures may get corrupted on upload]

=== Desktop platform ===
* [https://bugs.maemo.org/show_bug.cgi?id=1163 GtkCellRendererText: Can not edit with virtual keyboard]
* [https://bugs.maemo.org/show_bug.cgi?id=3659 Changing icon theme requires reboot to be applied correctly]
* [https://bugs.maemo.org/show_bug.cgi?id=3890 Missing libhildonmime API documentation]
* [https://bugs.maemo.org/show_bug.cgi?id=3910 Allow transparent desktop (wallpaper)]
* [https://bugs.maemo.org/show_bug.cgi?id=4579 HildonWindowClipboardOperation is completely undocumented]
* [https://bugs.maemo.org/show_bug.cgi?id=4608 HildonBanner does not except NULL value for deprecated icon argument]
* [https://bugs.maemo.org/show_bug.cgi?id=4619 Panning and selecting are mutually exclusive]
* [https://bugs.maemo.org/show_bug.cgi?id=4638 HildonPannableArea description should mention mov-mode property]
* [https://bugs.maemo.org/show_bug.cgi?id=4640 hildon_touch_selector_get_active_iter() needed.]
* [https://bugs.maemo.org/show_bug.cgi?id=4658 Documentation: HildonTouchSelectorEntry is unclear about auto-completion/text column]
* [https://bugs.maemo.org/show_bug.cgi?id=4695 HildonAnimationActor defines are passively documented in function descriptions]
* [https://bugs.maemo.org/show_bug.cgi?id=4718 GtkButton + hildon_gtk_widget_set_theme_size() has wrong style when created via GtkBuilder]
* [https://bugs.maemo.org/show_bug.cgi?id=4845 Remove Scratchboxism in libosso packaging]
* [https://bugs.maemo.org/show_bug.cgi?id=4851 libosso assumes that all ARM platforms has VFP instructions.]
* [https://bugs.maemo.org/show_bug.cgi?id=5173 HildonPickerDialog selects the first item always if appended into shown widget]
* [https://bugs.maemo.org/show_bug.cgi?id=5284 HildonPannableArea: size-request-policy property should be deprecated]
* [https://bugs.maemo.org/show_bug.cgi?id=5349 Can't organize applications menu]
* [https://bugs.maemo.org/show_bug.cgi?id=5388 Allow keyboard input to jump to an entry in a list (""type ahead"")]
* [https://bugs.maemo.org/show_bug.cgi?id=5421 keys when long pressed should give the blue symbol/number]
* [https://bugs.maemo.org/show_bug.cgi?id=5445 Status menu not available in portrait mode]
* [https://bugs.maemo.org/show_bug.cgi?id=5482 missing: system-wide ""start typing to eliminate items from list""]
* [https://bugs.maemo.org/show_bug.cgi?id=5496 HildonTouchSelector: No hint that there are more items]
* [https://bugs.maemo.org/show_bug.cgi?id=5609 Displays very small fonts (happened once)]
* [https://bugs.maemo.org/show_bug.cgi?id=5716 Popup menus with rounded corners missing transparency]
* [https://bugs.maemo.org/show_bug.cgi?id=5743 Show ALL installed applications in application menu; get rid of ""More...""]
* [https://bugs.maemo.org/show_bug.cgi?id=5838 Certain directory entries are duplicated (listed twice / doubled)]
* [https://bugs.maemo.org/show_bug.cgi?id=6017 Clicking the dashboard icon highlights it but does not open the dashboard]
* [https://bugs.maemo.org/show_bug.cgi?id=6060 Application manager finishing an installation in background blocks keyboard input]
* [https://bugs.maemo.org/show_bug.cgi?id=6069 Documentation missing on HildonNote vs ""Cancel"" button]
* [https://bugs.maemo.org/show_bug.cgi?id=6099 Incremental search function is case sensitive for ""select objects"" dialogue in html form elements like drop-down menus]
* [https://bugs.maemo.org/show_bug.cgi?id=6193 Browser: Tap is treated as input even if device was in standby mode (screen off)]
* [https://bugs.maemo.org/show_bug.cgi?id=6233 HildonPickerButton opens HildonPickerDialog dialog in landscape mode]
* [https://bugs.maemo.org/show_bug.cgi?id=6268 The required #include directives are not documented for Hildon]
* [https://bugs.maemo.org/show_bug.cgi?id=6361 base' and 'more' applications are visible sametime (messed)]
* [https://bugs.maemo.org/show_bug.cgi?id=6494 Can't change desktop Background]
* [https://bugs.maemo.org/show_bug.cgi?id=6545 HildonAppMenu doesn't show when another top level widget is around]
* [https://bugs.maemo.org/show_bug.cgi?id=6931 After installation of software last icon in ""More..."" view has default icon instead of own one]
* [https://bugs.maemo.org/show_bug.cgi?id=7126 Notification messages not displayed when optional ""category"" not set]
* [https://bugs.maemo.org/show_bug.cgi?id=7285 VKB has strange behavior when using the browser in portrait mode]
* [https://bugs.maemo.org/show_bug.cgi?id=7694 FN/Shift Locks get disabled by inserting a symbol with Sym]
* [https://bugs.maemo.org/show_bug.cgi?id=7852 After every boot the phone switches to the default theme]
* [https://bugs.maemo.org/show_bug.cgi?id=8038 Unlocking screen using power button/touch slide tops last application when on the desktop]
* [https://bugs.maemo.org/show_bug.cgi?id=8069 Cannot see the track time after black fill covers the white time font]
* [https://bugs.maemo.org/show_bug.cgi?id=8390 Fast search on the desktop doesn't work with cyrillic (Русский) layout]
* [https://bugs.maemo.org/show_bug.cgi?id=8731 Memory leaks in widget HildonAnimationActor]
* [https://bugs.maemo.org/show_bug.cgi?id=9059 Status bar icons shown on top of the virtual keyboard.]
* [https://bugs.maemo.org/show_bug.cgi?id=9194 hildon_pannable_area_scroll_to example is wrong (pointer instead of struct)]
* [https://bugs.maemo.org/show_bug.cgi?id=9552 Polish virtual keyboard: Cannot enter CAPITAL chars with diacritical signs]
* [https://bugs.maemo.org/show_bug.cgi?id=10041 Calender and Clock crash in Arabic localizition]

=== Location ===
* [https://bugs.maemo.org/show_bug.cgi?id=6284 Documentation in header files inaccurate - what unit does altitude have?]

=== Multimedia ===
* [https://bugs.maemo.org/show_bug.cgi?id=5524 PulseAudio clients are muted and hang on exit when media player is playing music]
* [https://bugs.maemo.org/show_bug.cgi?id=5554 Embedded windows media stream (ASF) at omroep.nl doesn't work]
* [https://bugs.maemo.org/show_bug.cgi?id=6365 maemo-xinput-sounds uses all available CPU]
* [https://bugs.maemo.org/show_bug.cgi?id=6506 Hardware keys do not change volume when status menu in foreground & browser in background]
* [https://bugs.maemo.org/show_bug.cgi?id=6792 FM radio transmitter does not play while USB cord is connected]
* [https://bugs.maemo.org/show_bug.cgi?id=6868 Pulseaudio uses cpu constantly after a phone call.]
* [https://bugs.maemo.org/show_bug.cgi?id=7082 mafw-dbus-daemon killed by podcast]
* [https://bugs.maemo.org/show_bug.cgi?id=7133 Shuffle all songs often plays a non-random sequence after the first song]
* [https://bugs.maemo.org/show_bug.cgi?id=7147 After playing video and canceling a couple of applications crashes and N900 slows down]
* [https://bugs.maemo.org/show_bug.cgi?id=7271 Can't change FM TX radio station name]
* [https://bugs.maemo.org/show_bug.cgi?id=7327 Xvid encoded videos unwatchable]
* [https://bugs.maemo.org/show_bug.cgi?id=7552 fmtx_client should pad station names shorter than 8 chars with spaces]
* [https://bugs.maemo.org/show_bug.cgi?id=7642 Playback of MP3 files might be cut-off at the end after seeking in file]
* [https://bugs.maemo.org/show_bug.cgi?id=8011 Changing volume without unlocking the phone no longer works]
* [https://bugs.maemo.org/show_bug.cgi?id=8172 PR 1.1 Regression: MP4 files with chapters hang playback]
* [https://bugs.maemo.org/show_bug.cgi?id=8396 FM Transmitter displays gibberish text in Radio player]

=== Synchronization ===
* [https://bugs.maemo.org/show_bug.cgi?id=6576 Alarm for a dropped occurrence of a recurring event]
* [https://bugs.maemo.org/show_bug.cgi?id=6582 exchange sync cant handle certificate exceptions]
* [https://bugs.maemo.org/show_bug.cgi?id=6703 MfE calendar sync causes dummy email sync account to appear]
* [https://bugs.maemo.org/show_bug.cgi?id=7971 mail for exchange freezes when trying to sync calendar and tasks]
* [https://bugs.maemo.org/show_bug.cgi?id=8373 N900 no longer accepting updates from Outlook 2007]
* [https://bugs.maemo.org/show_bug.cgi?id=8552 URLs in emails from Exchange are parsed incorrectly]
* [https://bugs.maemo.org/show_bug.cgi?id=8671 Deletion of messages should move first those items to ""Deleted Items"" folder]
* [https://bugs.maemo.org/show_bug.cgi?id=9296 Exchange event invitations scheduled without a prompt]

=== System software ===
* [https://bugs.maemo.org/show_bug.cgi?id=5530 Device autolock switches on the display]
* [https://bugs.maemo.org/show_bug.cgi?id=5674 Autobuilder fails to use opt-ified packages]
* [https://bugs.maemo.org/show_bug.cgi?id=5982 Phone unlocked when receiving call]
* [https://bugs.maemo.org/show_bug.cgi?id=6558 ohmd fails if discover_plugins cannot open plugin directory]
* [https://bugs.maemo.org/show_bug.cgi?id=6746 USB mass storage enabled when connected while device is off]
* [https://bugs.maemo.org/show_bug.cgi?id=7432 /opt and /home/user not cleared after firmware reflash]
* [https://bugs.maemo.org/show_bug.cgi?id=9270 Device unlockable if it get locked when being in portrait mode]

=== Telephony ===
* [https://bugs.maemo.org/show_bug.cgi?id=5457 Skype: ""Incorrect address"" for phone numbers missing the country code in Contacts]
* [https://bugs.maemo.org/show_bug.cgi?id=9073 callerid displays as ""Unknown number"" even though it is received by the N900]

=== Translations ===
* [https://bugs.maemo.org/show_bug.cgi?id=5602 IP address field in WiFi advanced settings partially hidden (""Recuperar automáticamente direccíon IP"" string too long)]
* [https://bugs.maemo.org/show_bug.cgi?id=5819 Some sentences in the User Guide don't make sense]
* [https://bugs.maemo.org/show_bug.cgi?id=5820 Wrong profile names in the User Guide]
* [https://bugs.maemo.org/show_bug.cgi?id=6261 Delete dialog text missing a space]
* [https://bugs.maemo.org/show_bug.cgi?id=6476 Email: Awkward text: ""Connecting Nokia servers to check service availability""]
* [https://bugs.maemo.org/show_bug.cgi?id=6662 Wrong Danish translation: ""Programmet 1 er installeret""]
* [https://bugs.maemo.org/show_bug.cgi?id=6736 Polish string too long in UPnP browsing menu bar]
* [https://bugs.maemo.org/show_bug.cgi?id=6982 Spanish: ""Tipo de fuente cambiado a %s"" when switching input languages]
* [https://bugs.maemo.org/show_bug.cgi?id=6997 Camera: Wrong translation ""Hochformat"" of ""Portrait"" in German UI]
* [https://bugs.maemo.org/show_bug.cgi?id=7274 Settings menu: String doesn't fit the button (""Inserir código para desbloquear cartão SIM"")]
* [https://bugs.maemo.org/show_bug.cgi?id=7345 Context menu in file manager should say ""Sformatuj"" or ""Formatuj"" instead of ""Format""]
* [https://bugs.maemo.org/show_bug.cgi?id=7476 Truncation of Flickr sharing introductory text in Polish]
* [https://bugs.maemo.org/show_bug.cgi?id=7477 ""sparowane"", ""paruj"", ""Paruj"", ""Parowanie"" in Bluetooth settings]
* [https://bugs.maemo.org/show_bug.cgi?id=7639 Wrong PO Box translation for CZ language]
* [https://bugs.maemo.org/show_bug.cgi?id=7687 Clock: Incorrect Danish translation of the phrase 'Remote time']
* [https://bugs.maemo.org/show_bug.cgi?id=8052 ""Dane sieci komórkowej niedostępne"" sounds strange]
* [https://bugs.maemo.org/show_bug.cgi?id=8257 ""Prześlij ponownie"" button label truncated (MicroB)]
* [https://bugs.maemo.org/show_bug.cgi?id=8560 Dutch translation in ""Settings"" doesnt fit on the screen]
* [https://bugs.maemo.org/show_bug.cgi?id=8713 Incorrect Danish translation of 'Extras' in Settings]
* [https://bugs.maemo.org/show_bug.cgi?id=8742 New E-mail Format translated illogically]
* [https://bugs.maemo.org/show_bug.cgi?id=9144 pl-PL: ""Nazwa autora"" in camera general settings should be ""Autor"" or ""Imię autora""]

=== UI Specification ===
* [https://bugs.maemo.org/show_bug.cgi?id=5420 Don't show hildon banner every tap when browsing UPnP shares]
* [https://bugs.maemo.org/show_bug.cgi?id=5516 Image Viewer: Dealing with ""occupied"" images is confusing]
* [https://bugs.maemo.org/show_bug.cgi?id=5610 ""Regional settings"" items sorted by languages instead of countries]
* [https://bugs.maemo.org/show_bug.cgi?id=7054 Cannot set ""Regional Settings"" to ""English (Australia)"" or ""English (New Zealand)""]
* [https://bugs.maemo.org/show_bug.cgi?id=8201 (metabug) Make more use of the keyboard in the dialogs / lists]

= Updated packages =

* +alarmd 1.1.16+0m5
* +apt 0.7.20.2maemo13.1+0m5
* +base-files 3.1.osso2+3.1.10.osso25+0m5
* +bash 2.05b-2-26osso8+0m5
* +bluez 4.60-0maemo1.4+0m5
* +browser-eal 0.5.5-6.1+0m5
* +cairo 1.8.8-0maemo1+0m5
* +clinkc 2.0-0osso17+0m5
* +clutter 0.8.2-0maemo66+0m5
* +dbus 1.2.14-0maemo4+0m5
* +dbus-glib 0.78-0maemo7+0m5
* +desktop-file-utils 0.12-2osso7+0m5
* +dnsmasq 2.45-1+lenny1+maemo3+0m5
* +dosfstools 3.0.1-1maemo6+0m5
* +dpkg 1.14.25maemo3+0m5
* +dsme 0.60.44+0m5
* +eds-backend-telepathy 0.4.62-1+0m5
* +evolution-data-server 1.4.2.1-20100226+0m5
* +farsight2 0.0.17-0maemo13+0m5
* +gcc-4.2 4.2.1-4maemo12+0m5
* +gconf2 2.16.0-2osso6.2+0m5
* +gdigicam 0.3.5.1+0m5
* +glib2.0 2.20.3-1maemo4+0m5
* +glibc 2.5.1-1eglibc23+0m5
* +gnome-menus 2.23.3-2maemo+0m5
* +gssdp 0.7.1-0maemo2+0m5
* +gst-openmax 0.10.0.6~1-0maemo17+0m5
* +gst-plugins-bad0.10 0.10.14-git265-0maemo10+0m5
* +gst-plugins-base0.10 0.10.25-0maemo14+0m5
* +gst-plugins-good0.10 0.10.16-git276-0maemo14+0m5
* +gstreamer0.10 0.10.25-0maemo4+0m5
* +gstreamer0.10-plugins-camera 0.79-1+0m5
* +gtk+2.0 2:2.14.7-1maemo29+0m5
* +gtkhtml3.14 3.24.4-osso18+0m5
* +gupnp 0.13.2-0maemo2+0m5
* +gupnp-av 0.5.2-0maemo2+0m5
* +gupnp-igd 0.1.4-0maemo3+0m5
* +hal 0.5.12~git20090219-0maemo7+0m5
* +hildon-application-manager 1:2.2.60-1+0m5
* +hildon-application-manager-l10n-public 6.0+r7611+0m5
* +hildon-control-panel 1:2.2.27-2+0m5
* +hildon-control-panel-l10n-public 6.0+r7640+0m5
* +hildon-desktop 1:2.2.135-2+0m5
* +hildon-fm-l10n-public 6.0+r7483+0m5
* +hildon-games-wrapper 1.9.4-5+0m5
* +hildon-home 0.3.66-2+0m5
* +hildon-input-method 1:2.1.46-1+0m5
* +hildon-input-method-framework 1:2.1.56-1+0m5
* +hildon-input-method-l10n-public 6.0+r7520+0m5
* +hildon-libs-l10n-public 6.0+r7510+0m5
* +hildon-status-menu 0.3.34+0m5
* +hildon-theme-layout-5 0.15.0-1+0m5
* +hildon-thumbnail 3.0.44+0m5
* +ke-recv-l10n-public 6.0+r7611+0m5
* +kernel 2.6.28-20100903+0m5
* +libcanberra 0.14-0maemo4+0m5
* +libcomapp 1.8.03-01+0m5
* +libconbtui 1.4.3+0m5
* +libconic 0.24+0m5
* +libdsme 0.60.30+0m5
* +libexif 0.6.17-1maemo3+0m5
* +libffi 3.0.7-2maemo2+0m5
* +libgtkadi 0.7.13-1+0m5
* +libgtkmozembed 1.8.7-2.1+0m5
* +libhildon 2.2.15-1+0m5
* +libhildondesktop 2.1.40+0m5
* +libhildonfm 1:2.28.17+0m5
* +libhildonmime 2.1.5-1+0m5
* +libical 1.43-101+0m5
* +libmafw 0.2.2010.06-1+0m5
* +libmlocknice 0.1+0m5
* +libmodest-dbus-client 4:3.2.5-0+0m5
* +libnice 1:0.0.9-0maemo8.0rtc+0m5
* +libosso 2.31-1+0m5
* +librtcom-telepathy-glib 0.1.49+0m5
* +libsoup2.4 2.26.3-0maemo3+0m5
* +libunwind 0.99+git20080421-2+0m5
* +libwidgetutils 1.4.1-6+0m5
* +libwww-perl 5.803-4osso1+0m5
* +loudmouth 1.4.1-0osso10+0m5
* +maemo-af-desktop-l10n-public 6.0+r7640+0m5
* +maemo-maf 5.0+3+0m5
* +maemo-mmf 5.0+3+0m5
* +maemopad 2.6-3
* +maemo-version 5.0update5+0m5
* +mafw-gst-renderer 0.2.2010.07-2+0m5
* +mafw-iradio-source 0.2.2010.06-1+0m5
* +mafw-shared 0.2.2010.06-1+0m5
* +mafw-test-gui 0.2.2010.06-1+0m5
* +mafw-tracker-source 0.2.2010.06-1+0m5
* +mafw-upnp-source 0.2.2010.07-2+0m5
* +matchbox-window-manager-2 0.2.89-1+0m5
* +mce-dev 1.8.17+0m5
* +microb-eal 2.9.5-1.15+0m5
* +microb-engine 20091230-1.9.2-6.8+0m5
* +mini-rc 0.2.67+0m5
* +modest 3.2.13-3+0m5
* +obexd 0.18-0maemo5+0m5
* +ohm 0.1.2-0maemo33+0m5
* +osso-af-utils 2.12-1+0m5
* +osso-app-killer 1.33-3+0m5
* +osso-filemanager-l10n-public 6.0+r7611+0m5
* +osso-games-startup 1.7.49-1+0m5
* +osso-gnome-vfs2 2.16.3-2osso11+0m5
* +osso-gwobex 0.64+0m5
* +osso-rss-feed-reader 1.8.03-3+0m5
* +osso-rss-feed-reader-applet 1.7.03-1+0m5
* +osso-rss-feed-reader-lib 1.8.01-1+0m5
* +osso-system-lock-l10n-public 6.0+r7585+0m5
* +osso-uri-l10n-public 6.0+r7510+0m5
* +pango1.0 1.24.2-0maemo4+0m5
* +pixman 0.16.2-4+0m5
* +poppler 0.4.5-5.1etch3maemo1+0m5
* +posix-locales 2.7.2-1maemo7-binonly0+0m5
* +pulseaudio 0.9.15-1maemo38+0m5
* +qt4-x11 4.6.2~git20100224-0maemo1+0m5
* +rtcom-eventlogger 1.3-4+0m5
* +rtcom-eventlogger-plugins 1.4-1+0m5
* +rtcom-eventlogger-ui 1.4-2+0m5
* +sapwood 3.1.1-10+0m5
* +sqlite3 3.6.14-1maemo3+0m5
* +telepathy-farsight 0.0.13-0maemo5+0m5
* +telepathy-gabble 0.8.11-0maemo2+0m5
* +telepathy-mission-control 5.2.7-0maemo6+0m5
* +tetex-bin 3.0-30maemo2+0m5
* +tiff 1:3.8.2-11maemo5+0m5
* +tinymail 1.1.90-svn4193+0m5
* +totem-pl-parser 2.27.2-1maemo2+0m5
* +tracker 0.6.95-25maemo1+0m5
* +upstart 0.3.8-64+0m5
* +wpeditor 3.53-1+0m5
* +xkeyboard-config 1.5-2maemo15+0m5
* +xorg-server 2:1.6.99.1-0osso20090208.108+0m5
* +xserver-xorg-video-fbdev 1:0.4.0-180+0m5

[[Category:Fremantle]]
[[Category:N900]]

Qt-Maemo

2010-05-10T08:56:42Z

192.100.124.219: /* Image:Ktorrent.png‎ Installing Qt */

__NOTOC__

=[[Image:Kblogger.png‎ ]] News=
7 May 10 - Qt 4.7 Beta1 packages for Maemo available [http://labs.trolltech.com/blogs/2010/05/06/new-experimental-qt-47-packages-for-the-n900/ read more] 
22 Mar 10 - Qt 4.6.2 has replaced Qt 4.5.3 into SDK PR 1.2. Run apt-get update && apt-get upgrade to update it. 
25 Feb 10 - [http://labs.trolltech.com/blogs/2010/02/24/qt-for-maemo-5-home-screen-widgets/ How to make Qt Desktop Widgets] 
15 Feb 10 - Qt 4.6.2 is out. Qt Mobility (beta1) packages are in extras-devel. 
20 Jan 10 - [http://www.anselmolsm.org/blog/qt-mobile-demos-in-extras-devel/ Qt Mobile Demos in extras-devel] 
19 Jan 10 - [http://qt.nokia.com/developer/qt-for-maemo-developers Qt 4.6 for Maemo 5 going Beta] 
15 Jan 10 - New Qt 4.5.3~git20090723-0maemo6 packages are now in Fremantle [[Maemo_5/PR1.1|PR 1.1]] 
22 Dec 09 - [http://wiki.maemo.org/MADDE/Qt_Example Qt example] for [http://wiki.maemo.org/MADDE MADDE ] ([http://talk.maemo.org/showthread.php?t=38075 talk thread]) 
17 Dec 09 - [http://labs.trolltech.com/blogs/2009/12/17/qt-declarative-for-maemo-5/Qt declarative hits Maemo extras-devel repository] 
11 Dec 09 - Bye bye old static web pages.. all our pages are now in the Maemo Wiki. Old website is [http://qt4.garage.maemo.org/index-old.html here] 

=[[Image:Intro.png]] What is Qt?=
Qt (pronounced as the English word "cute") is a cross-platform application development framework. More information is available at the [http://qt.nokia.com/ Qt website].

=[[Image:Rocket.png]] Maemo Qt main features=
* Hildon Style, so applications look like Hildon/GTK+ applications
* Hildon Input Method, so applications can use the virtual keyboard
* Hildon-specific widgets
** partial support in Qt 4.5
** Qt 4.6 will have full support, and is currently a technology preview

= [[Image:Fileview-preview.png]] Maemo Qt in Action =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS

=[[Image:Pda.png]] Supported Maemo devices=
* [[Nokia N800]]/[[Nokia N810|N810]] (OS2008/Maemo4.1/Diablo)
* [[Nokia N900]] (OS2009/Maemo5/[[Open development/Maemo roadmap/Fremantle|Fremantle]])

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

Qt can be [http://wiki.maemo.org/Qt4_Hildon#Getting_started installed in scratchbox] for development. For applications that use Qt and are installed via the application manager, the necessary Qt packages will automatically be installed.

=[[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.. [[Qt4HildonApplications|this]] is the place you would like to check;

=[[Image:Help-contents.png]] Documentation=

== Qt ==

* [[Qt4 development]] developing with Qt for Maemo
* [[QML]]
* [[QtRuby]]

== Non-Qt documentation ==

* 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

== Further reading ==

* [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
* [http://wiki.forum.nokia.com/index.php/Qt_for_Maemo_Developers_Guide Qt for Maemo Developers Guide, Forum Nokia]
* [http://www.forum.nokia.com/Tools_Docs_and_Code/Documentation/Maemo.xhtml Maemo documentation, mostly about Qt, Forum Nokia]
* [http://doc.trolltech.com/qt-maemo-4.6/how-to-learn-qt.html How to learn Qt, Trolltech]
* [http://qt.nokia.com/developer/books Books] listed at qt.nokia.com
* [http://talk.maemo.org/showthread.php?t=39879 Qt4 hello world with python in 30 minutes]
* [http://wiki.forum.nokia.com/index.php/Qt_application_for_Maemo_with_DBus_support Install D-Bus Service with Qt]
* [[University Course]] (in progress): A syllabus for teaching Qt as an intensive two-week course.

=[[Image:Bug.png]] Bug tracking=
* Diablo & Fremantle 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

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Qt for Maemo Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Old qt4.garage.maemo.org forum]
* IRC
** Official Qt for Maemo IRC Channel
** 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]

[[Category:Qt]]

Qt-Maemo

2010-05-10T08:55:39Z

192.100.124.219: /* Image:Ktorrent.png‎ Installing Qt */

__NOTOC__

=[[Image:Kblogger.png‎ ]] News=
7 May 10 - Qt 4.7 Beta1 packages for Maemo available [http://labs.trolltech.com/blogs/2010/05/06/new-experimental-qt-47-packages-for-the-n900/ read more] 
22 Mar 10 - Qt 4.6.2 has replaced Qt 4.5.3 into SDK PR 1.2. Run apt-get update && apt-get upgrade to update it. 
25 Feb 10 - [http://labs.trolltech.com/blogs/2010/02/24/qt-for-maemo-5-home-screen-widgets/ How to make Qt Desktop Widgets] 
15 Feb 10 - Qt 4.6.2 is out. Qt Mobility (beta1) packages are in extras-devel. 
20 Jan 10 - [http://www.anselmolsm.org/blog/qt-mobile-demos-in-extras-devel/ Qt Mobile Demos in extras-devel] 
19 Jan 10 - [http://qt.nokia.com/developer/qt-for-maemo-developers Qt 4.6 for Maemo 5 going Beta] 
15 Jan 10 - New Qt 4.5.3~git20090723-0maemo6 packages are now in Fremantle [[Maemo_5/PR1.1|PR 1.1]] 
22 Dec 09 - [http://wiki.maemo.org/MADDE/Qt_Example Qt example] for [http://wiki.maemo.org/MADDE MADDE ] ([http://talk.maemo.org/showthread.php?t=38075 talk thread]) 
17 Dec 09 - [http://labs.trolltech.com/blogs/2009/12/17/qt-declarative-for-maemo-5/Qt declarative hits Maemo extras-devel repository] 
11 Dec 09 - Bye bye old static web pages.. all our pages are now in the Maemo Wiki. Old website is [http://qt4.garage.maemo.org/index-old.html here] 

=[[Image:Intro.png]] What is Qt?=
Qt (pronounced as the English word "cute") is a cross-platform application development framework. More information is available at the [http://qt.nokia.com/ Qt website].

=[[Image:Rocket.png]] Maemo Qt main features=
* Hildon Style, so applications look like Hildon/GTK+ applications
* Hildon Input Method, so applications can use the virtual keyboard
* Hildon-specific widgets
** partial support in Qt 4.5
** Qt 4.6 will have full support, and is currently a technology preview

= [[Image:Fileview-preview.png]] Maemo Qt in Action =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS

=[[Image:Pda.png]] Supported Maemo devices=
* [[Nokia N800]]/[[Nokia N810|N810]] (OS2008/Maemo4.1/Diablo)
* [[Nokia N900]] (OS2009/Maemo5/[[Open development/Maemo roadmap/Fremantle|Fremantle]])

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

Qt can be [[http://wiki.maemo.org/Qt4_Hildon#Getting_started|installed in scratchbox]] for development. For applications that use Qt and are installed via the application manager, the necessary Qt packages will automatically be installed.

=[[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.. [[Qt4HildonApplications|this]] is the place you would like to check;

=[[Image:Help-contents.png]] Documentation=

== Qt ==

* [[Qt4 development]] developing with Qt for Maemo
* [[QML]]
* [[QtRuby]]

== Non-Qt documentation ==

* 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

== Further reading ==

* [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
* [http://wiki.forum.nokia.com/index.php/Qt_for_Maemo_Developers_Guide Qt for Maemo Developers Guide, Forum Nokia]
* [http://www.forum.nokia.com/Tools_Docs_and_Code/Documentation/Maemo.xhtml Maemo documentation, mostly about Qt, Forum Nokia]
* [http://doc.trolltech.com/qt-maemo-4.6/how-to-learn-qt.html How to learn Qt, Trolltech]
* [http://qt.nokia.com/developer/books Books] listed at qt.nokia.com
* [http://talk.maemo.org/showthread.php?t=39879 Qt4 hello world with python in 30 minutes]
* [http://wiki.forum.nokia.com/index.php/Qt_application_for_Maemo_with_DBus_support Install D-Bus Service with Qt]
* [[University Course]] (in progress): A syllabus for teaching Qt as an intensive two-week course.

=[[Image:Bug.png]] Bug tracking=
* Diablo & Fremantle 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

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Qt for Maemo Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Old qt4.garage.maemo.org forum]
* IRC
** Official Qt for Maemo IRC Channel
** 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]

[[Category:Qt]]

Qt-Maemo

2010-05-07T11:12:45Z

192.100.124.219: /* Image:Kblogger.png‎ News */

__NOTOC__

=[[Image:Kblogger.png‎ ]] News=
7 May 10 - Qt 4.7 Beta1 packages for Maemo available [http://labs.trolltech.com/blogs/2010/05/06/new-experimental-qt-47-packages-for-the-n900/ read more] 
22 Mar 10 - Qt 4.6.2 has replaced Qt 4.5.3 into SDK PR 1.2. Run apt-get update && apt-get upgrade to update it. 
25 Feb 10 - [http://labs.trolltech.com/blogs/2010/02/24/qt-for-maemo-5-home-screen-widgets/ How to make Qt Desktop Widgets] 
15 Feb 10 - Qt 4.6.2 is out. Qt Mobility (beta1) packages are in extras-devel. 
20 Jan 10 - [http://www.anselmolsm.org/blog/qt-mobile-demos-in-extras-devel/ Qt Mobile Demos in extras-devel] 
19 Jan 10 - [http://qt.nokia.com/developer/qt-for-maemo-developers Qt 4.6 for Maemo 5 going Beta] 
15 Jan 10 - New Qt 4.5.3~git20090723-0maemo6 packages are now in Fremantle [[Maemo_5/PR1.1|PR 1.1]] 
22 Dec 09 - [http://wiki.maemo.org/MADDE/Qt_Example Qt example] for [http://wiki.maemo.org/MADDE MADDE ] ([http://talk.maemo.org/showthread.php?t=38075 talk thread]) 
17 Dec 09 - [http://labs.trolltech.com/blogs/2009/12/17/qt-declarative-for-maemo-5/Qt declarative hits Maemo extras-devel repository] 
11 Dec 09 - Bye bye old static web pages.. all our pages are now in the Maemo Wiki. Old website is [http://qt4.garage.maemo.org/index-old.html here] 

=[[Image:Intro.png]] What is Qt?=
Qt (pronounced as the English word "cute") is a cross-platform application development framework. More information is available at the [http://qt.nokia.com/ Qt website].

=[[Image:Rocket.png]] Maemo Qt main features=
* Hildon Style, so applications look like Hildon/GTK+ applications
* Hildon Input Method, so applications can use the virtual keyboard
* Hildon-specific widgets
** partial support in Qt 4.5
** Qt 4.6 will have full support, and is currently a technology preview

= [[Image:Fileview-preview.png]] Maemo Qt in Action =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS

=[[Image:Pda.png]] Supported Maemo devices=
* [[Nokia N800]]/[[Nokia N810|N810]] (OS2008/Maemo4.1/Diablo)
* [[Nokia N900]] (OS2009/Maemo5/[[Open development/Maemo roadmap/Fremantle|Fremantle]])

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

Qt can be [[Qt4_Hildon#Installing_Qt_packages_in_Scratchbox|installed in scratchbox]] for development. For applications that use Qt and are installed via the application manager, the necessary Qt packages will automatically be installed.

=[[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.. [[Qt4HildonApplications|this]] is the place you would like to check;

=[[Image:Help-contents.png]] Documentation=

== Qt ==

* [[Qt4 development]] developing with Qt for Maemo
* [[QML]]
* [[QtRuby]]

== Non-Qt documentation ==

* 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

== Further reading ==

* [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
* [http://wiki.forum.nokia.com/index.php/Qt_for_Maemo_Developers_Guide Qt for Maemo Developers Guide, Forum Nokia]
* [http://www.forum.nokia.com/Tools_Docs_and_Code/Documentation/Maemo.xhtml Maemo documentation, mostly about Qt, Forum Nokia]
* [http://doc.trolltech.com/qt-maemo-4.6/how-to-learn-qt.html How to learn Qt, Trolltech]
* [http://qt.nokia.com/developer/books Books] listed at qt.nokia.com
* [http://talk.maemo.org/showthread.php?t=39879 Qt4 hello world with python in 30 minutes]
* [http://wiki.forum.nokia.com/index.php/Qt_application_for_Maemo_with_DBus_support Install D-Bus Service with Qt]
* [[University Course]] (in progress): A syllabus for teaching Qt as an intensive two-week course.

=[[Image:Bug.png]] Bug tracking=
* Diablo & Fremantle 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

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Qt for Maemo Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Old qt4.garage.maemo.org forum]
* IRC
** Official Qt for Maemo IRC Channel
** 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]

[[Category:Qt]]

Device management using Bcfg2

2010-04-15T11:04:55Z

192.100.124.219: /* Scope and terminology */

This article contains information about using [http://trac.mcs.anl.gov/projects/bcfg2 Bcfg2], an open source configuration management system in management of Maemo based devices.

Note! At this phase, although the title says otherwise, instructions given in this article do NOT constitute a device management solution. At the moment these instructions only guide to '''experiment''' device management using Bcfg2.

== Scope and terminology ==

Scope of the article is using Bcfg2 to manage Maemo devices of employees at a fairly large company, where the number of devices is counted on hundreds or thousands. In a private use, or in small companies things covered here hardly make any sense.

In the remainder if this document, following terminology is used

{| class="wikitable" border="1"
|-
! Term
! Description
|-
| Device
| Maemo based handset, such as [[Nokia N900]]
|-
| Device management
| Generally used term for configuration management which takes place on Devices
|-
| Enterprise
| A large company or other organization that wants employees to ba able to acces company IT systems using Maemo based devices
|-
| Desktop computer
| A full-size computer (traditional desktop or laptop) used to access corporate IT systems
|-
| Enterprise configuration
| A set of applications and configuration values which the Enterprise wants to deploy into the Device as a prerequisite for accessing corporate IT systems. Usually includes hardening the device security.
|-
| Provisioning
| The process which equips the Device with Enterprise configuration
|}

Instructions given in this article are tested on [[Open development/Maemo roadmap/Fremantle|Fremantle]]. They may work on other releases as well, but probably not.

=== Recommended reading ===

Basic use and concepts of Bcfg2 are not in the scope of this article. To get familiar with Bcfg2, following reading is recommended:

*[http://www.linuxlinks.com/article/20100222155850632/ConfigurationManagement.html 7 of the Best Free Linux Configuration Management Tools]
* [http://trac.mcs.anl.gov/projects/bcfg2/wiki/Bcfg2Doc Bcfg2 documentation]

== Device management? Why bother? ==

Provisioning Devices without management is like standing on the waterfront, throwing rocks in to a lake trying to get them land into a bucket at a bottom. The throwing movement can be very controlled and calculated, but once the rock is released from hand, all control and traceability is lost. As a result, we do not really know if it ever hit the bucket. And if it did not, there is no way to get it there. Not to mention ability to move it into another bucket if so desired. Over time, we also inevitably lose track of how many rocks have we have thrown.

Hence, Provisioning-only approach leads at least following shortcomings
* No statistics about Devices Provisioned
* No information about success of the Provisioning
* No method to fix failed Provisioning
* No method for managing changes at Enterprise configuration (other than publish a new release hoping users will pick it up)

Using the rock analogy, in Device management approach we never completely release the rock. We tie a thin nylon line into each rock before throwing it. Now we can follow the line and track whether the rock did hit the bucket or not. We can use the line to lift misses to the bucket. We can also use the line to move them to another bucket if so desired. We can also easily have statistics about the rocks thrown; just count the lines.

It should be also noted that there are legislations such as Sarbanes-Oxley which mandate keeping track of computers able to access and store corporate data.

== Why Bcfg2? ==

Openness is at heart of the Maemo philosophy. Thus, using an Open Source configuration management system seems a logical choice to try out.

Bcfg2 was chosen as the first candidate to try-out because

* Architecture is server-centric. Processing is performed at the server end as much as possible. This makes the client lightweight. It makes it also simpler and less frequently changing.
* Device management is a special use case for a software like this. They are all geared more for server and desktop management. Thus, fair amount of customization is anticipated. Bcfg2 has very flexible plugin architecture where most of it's core functionality implemented as plugins. This makes it very customization-friendly, nearly all components are replaceable
* Anticipation of customization puts lot of weight to implementation language. Bcfg2 is written in Python, which suits the author best.

That said, there is no reason why other configuration management systems such as CFEngine or Puppet wouldn't work as well. (Actually, Puppet was tried out, got successfully running at the Device. Only it did not communicate with the server. This is possibly caused by the SSL problem discussed later. That's was the point where lack of author's Ruby skills kicked in :)

== Getting Bcfg2 up and running ==

A word of warning: Configuration management is complicated task. Learning Bcfg2 and the concepts behind it does take some time and effort. Do NOT by try to manage Maemo clients as your first Bcfg2 rehearsal. Instead, familiarize yourself with Bcfg2 first using "ordinary" computers as clients.

=== Problems with Bcfg2 in Maemo ===

At the moment there are some problems we need to work around in order to install Bcfg2 client into Device.

# Lack of proper SSL support
#* Bcfg2 prior to 1.0 used Python implementation of SSL called tlslite. At 1.0 tlslite war replaced with Python 2.6 built-in SSL module
#* Bcfg2 has internal fallback to use M2crypto module if SSL module fails
#* Maemo (Fremantle), however, has Python 2.5, which has no SSL module and no M2crypto module either
#** There is actually already [https://bugs.maemo.org/show_bug.cgi?id=5102 bug report] filed about the problem. However, the original problem (importing SSL module) was never solved, the problem the reporter faces seems to be worked around other way
#* Possible workarounds:
#** Compile [http://pypi.python.org/pypi/ssl/SSL SSL 1.15] module into Python 2.5
#** Compile M2crypto module into Python 2.5
#*** Both fail into lack of complete set of OpenSSL development headers
#** Re-include tlslib into Bcfg2
#*** Possible, however there will be no server identity validation
#** Use Bcfg2 prior to 1.0 in Device
#*** Possible, however there will be no server identity validation
#* Contributions welcome
# Bcfg2 is not packaged for Maemo
#* Must be installed from source
# There is no good way for bootstrapping right now
#* Installation must be performed from Device command line

=== Server installation ===

Download and install version 1.0.1 following instructions found at [http://trac.mcs.anl.gov/projects/bcfg2/wiki/Download Bcfg2 web site]

Note that the server should reside in a network the Device is able to access.

=== Client installation ===

==== Option 1: Install old version ====

Download [http://ftp.mcs.anl.gov/pub/bcfg/archive/bcfg2-0.9.6.tar.gz bcfg2-0.9.6] in to the Device. Open terminal window and install Bcfg2 by entering following commands

apt-get install python
tar zxvf bcfg2-0.9.6.tar.gz
cd bcfg2-0.9.6
python setup.py install --install-layout deb --record /root/bcfg2files

==== Option 2: Install current version ====

This option is somewhat more complicated since we need to re-include tlslib into Bcfg2

Download [http://ftp.mcs.anl.gov/pub/bcfg/archive/bcfg2-0.9.6.tar.gz bcfg2-0.9.6] and [http://ftp.mcs.anl.gov/pub/bcfg/archive/bcfg2-1.0.1.tar.gz bcfg2-1.0.1] both. Extract them:

tar zxvf bcfg2-0.9.6.tar.gz
tar zxvf bcfg2-1.0.1.tar.gz

Get tlslib and from older version

cp -r bcfg2-0.9.6/src/lib/tlslite bcfg2-1.0.1/src/lib

Download [http://trac.mcs.anl.gov/projects/bcfg2/browser/trunk/bcfg2/src/lib/Proxy.py?rev=5168&format=txt this version] of Proxy.py from Bcfg2 site and save it as <code>bcfg2-1.0.1/src/lib/Proxy.py</code>

Edit <code>bcfg2-1.0.1/src/lib/Proxy.py</code>. Add dummy placeholders <code>ca</code> and <code>allowedServerCNs</code> into ComponentProxy definition so it looks like below:

def ComponentProxy (url, user=None, password=None, fingerprint=None,
key=None, ca=None, allowedServerCNs=None, cert=None):

Edit <code>bcfg2-1.0.1/setup.py</code>
Add the packages <code>Bcfg2.tlslite</code>, <code>Bcfg2.tlslite.integration</code>, and <code>Bcfg2.tlslite.utils</code> back into the packages list in setup.py, as seen in [https://trac.mcs.anl.gov/projects/bcfg2/browser/trunk/bcfg2/setup.py?rev=5182 here]

Repackage the source directory

tar zcvf bcfg2-1.0.1-mod.tar.gz bcfg2-1.0.1

Transfer <code>bcfg2-1.0.1-mod.tar.gz</code> to the Device. Open (at Device) terminal window and install Bcfg2 by entering following commands

apt-get install python
tar zxvf bcfg2-1.0.1-mod.tar.gz
cd bcfg2-1.0.1
python setup.py install --install-layout deb --record /root/bcfg2files

=== Installation notes ===

Reinstalling Bcfg2: Remove <code>bcfg2-1.0.1/build</code> directory before re-run of <code>setup.py</code>

Removing Bcfg2: remove files listed at <code>/root/bcfg2files</code>

=== Simple sample configuration ===

In the following we create a simple configuration at the Bcfg2 server, just to make you get on board quicker (empty configurations are not very illustrative). In the sample configuration we do three things:
* Manage the content of a simple file <code>/etc/simple</code>
* Manage the content of a file <code>/etc/bcfg2.info</code> using template
* Run a simple action, a shell command <code>ls / > /tmp/foobar</code>

Throughout this article we assume the configuration repository is at default location <code>/var/lib/bcfg2</code>.

Edit file <code>/var/lib/bcfg2/Metadata/groups.xml</code> to contain following:

<Groups>
<Group name='armel'/>
<Group name='linux'/>
<Group name='deb'>
<Group name='linux'/>
</Group>
<Group name='maemo'>
<Group name='deb'/>
<Bundle name='sample'/>
</Group>
<Group name='fremantle'>
<Group name='maemo'/>
</Group>
</Groups>

Edit file <code>/var/lib/bcfg2/Bundler/sample.xml</code> to contain following:

<Bundle name='sample'>
<ConfigFile name='/etc/simple'/>
<ConfigFile name='/etc/bcfg2.info'/>
<BoundAction name="simple" timing='post' when='always' status='check' command="ls / > /tmp/foobar"/>
</Bundle>

Edit file <code>/var/lib/bcfg2/Cfg/etc/simple/simple</code> to contain following (Create directories as needed):

This is a simple file

Edit file <code>/var/lib/bcfg2/Cfg/etc/simple/simple</code> to contain following:

<FileInfo>
<Info owner='root' group='root' perms='0644' encoding='ascii'/>
</FileInfo>

Edit file <code>/var/lib/bcfg2/TCheetah/etc/bcfg2.info/template</code> to contain following (Create directories as needed):

Hostname: $self.metadata.hostname
Uuid: $self.metadata.uuid
Password: $self.metadata.password
Profile: $self.metadata.profile
Groups: #echo ','.join($self.metadata.groups)#
Bundles: #echo ','.join($self.metadata.bundles)#

Edit file <code>/var/lib/bcfg2/TCheetah/etc/bcfg2.info/info.xml</code> to contain following:

<FileInfo>
<Info owner='root' group='root' perms='0644' encoding='ascii'/>
</FileInfo>

==== Some explanation: ====

Bcfg2 builds the configuration using layered approach:

* Metadata (roughly: "which kind of configuration should be where")
* Abstract (roughly: what should be configured)
* Literal (roughly: how exactly that "what" should be achieved)

In this example, we have two instances of the same abstract configuration item (ConfigFile). They are however handled by two different literal configuration generators, Cfg, which handles simple files and TCheetah which handles more complicated files using built-in Cheetah templating engine.

One thing to like in Bcfg2 is that it does not mandate things too much. Third item is an example of that. Bcfg2 allows short-circuiting the Literal layer processing altogether by adding "Bound" in front of the keyword. In a simple cases where what we want exactly is already known already at abstract level this can simplify things.

=== Hooking the Device and Bcfg2 server together ===

At server, add following line into <code>/var/lib/bcfg2/Metadata/clients.xml</code>

<Client uuid="foo" name="bar" profile="maemo" password="xyzzy" pingable="N" location="floating" auth="cert+password"/>

No need to restart the Bcfg2 server, it picks the changes on the fly. Next, at the Device, edit the file <code>/etc/bcfg2.conf</code> to look like following:

[communication]
protocol = xmlrpc/ssl
user = foo
password = xyzzy

[components]
bcfg2 = https://bcfg2server.example.com:6789

Now you should be able to invoke Bcfg2 client and make first connection to the server using command

bcfg2 -I

You should now be prompted a confirmation for three configuration item defined in the sample configuration, due to use of <code>-I</code> option.

<hr/>

== Appendix: Hints on Bcfg2 usage ==

=== Autogroup probe ===

Bcfg2 is able to automatically determine group memberships using probes. [http://wiki.maemo.org/Image:Autogroup.sh Here] is a sample probe code which recognizes Maemo devices among many other computers. Just put the code into a file at Probes directory, for example, <code>/var/lib/bcfg2/Probes/autogroup</code>

At Bcfg2 web site is another [http://trac.mcs.anl.gov/projects/bcfg2/wiki/Plugins/Probes/examples/group example] of autogroup probe code. This code does not recognize Maemo but might do better work with some other platforms.

<hr/>

== TODO ==

This is the "dont look here" part, stuff under construction

=== APT package driver ===

==== Problems ====

# Maemo does not have debsums utility
#* Causes APT package driver not to load
# Maemo has no Python bindings to APT cache
#* Causes APT package driver not to load/work
# APT package driver is too "control freak" for the purpose
#* Wants to check package versions and even verify all the files
#* Suitable approach for servers but brings tiny device at it's knees
#* We probably only want to control that package X is installed and let package manager take care of the rest (updates & such)
# No any form of proxy handling (odds being inside corporate firewall are good)

==== Opportunities ====

Hildon application manager is not able to go through proxies, but APT is

==== Proposed solution ====

We need to write a "APTlite" client driver. Probably modifying an simple existing driver like <code>FreeBSDPackage.py</code> would do. Some notes about the task:

* <code>RefreshPackages</code> method needs to be modified to include only packages received from server and ignore the rest. Looks like following piece of code generates the list we need
desired = [entry.get('name') for struct in self.config for entry in struct if entry.tag == 'Package']

* Then, we could run something like this for each pkg in desired list to fill up the <code>self.installed</code> dictionary:

/usr/bin/dpkg-query -W --showformat='${Version}\t${Status}\n' <pkg>

* <code>VerifyPackage</code> method needs probably to be made a bit more liberal, like returning true if <code>entry.attrib['version']</code> equals <code>'auto'</code> or <code>'any'</code>

* <code>pkgtool</code> could probably be copied from <code>APT.py</code>

* Proxies could be copied from shell environment by adding them into <code>pkgtool</code>. Something like

proxies = ""
for p in ('http','https','ftp'):
if os.environ.has_key('%s_proxy' % p):
proxies += '%s=%s ' % ('%s_proxy' % p, os.environ.get('%s_proxy' % p))
pkgtool = proxies + ' ' + pkgtool

And how to get proxies into shell variables? One option is to use Bcfg2 to manage some file which is sourced by shell

[[Category:Power users]]

Qt-Maemo

2010-03-26T10:36:31Z

192.100.124.219: /* Image:Kblogger.png‎ News */

__NOTOC__

=[[Image:Kblogger.png‎ ]] News=
22 Mar 10 - Qt 4.6.2 has replaced Qt 4.5.3 into SDK PR 1.2. Run apt-get update && apt-get upgrade to update it. 
25 Feb 10 - [http://labs.trolltech.com/blogs/2010/02/24/qt-for-maemo-5-home-screen-widgets/ How to make Qt Desktop Widgets] 
15 Feb 10 - Qt 4.6.2 is out. Qt Mobility (beta1) packages are in extras-devel. 
20 Jan 10 - [http://www.anselmolsm.org/blog/qt-mobile-demos-in-extras-devel/ Qt Mobile Demos in extras-devel] 
19 Jan 10 - [http://qt.nokia.com/developer/qt-for-maemo-developers Qt 4.6 for Maemo 5 going Beta] 
15 Jan 10 - New Qt 4.5.3~git20090723-0maemo6 packages are now in Fremantle [[Maemo_5/PR1.1|PR 1.1]] 
22 Dec 09 - [http://wiki.maemo.org/MADDE/Qt_Example Qt example] for [http://wiki.maemo.org/MADDE MADDE ] ([http://talk.maemo.org/showthread.php?t=38075 talk thread]) 
17 Dec 09 - [http://labs.trolltech.com/blogs/2009/12/17/qt-declarative-for-maemo-5/Qt declarative hits Maemo extras-devel repository] 
11 Dec 09 - Bye bye old static web pages.. all our pages are now in the Maemo Wiki. Old website is [http://qt4.garage.maemo.org/index-old.html here] 

=[[Image:Intro.png]] What is Qt?=
Qt (pronounced as the English word "cute") is a cross-platform application development framework. More information is available at the [http://qt.nokia.com/ Qt website].

=[[Image:Rocket.png]] Maemo Qt main features=
* Hildon Style, so applications look like Hildon/GTK+ applications
* Hildon Input Method, so applications can use the virtual keyboard
* Hildon-specific widgets
** partial support in Qt 4.5
** Qt 4.6 will have full support, and is currently a technology preview

= [[Image:Fileview-preview.png]] Maemo Qt in Action =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS

=[[Image:Pda.png]] Supported Maemo devices=
* [[Nokia N800]]/[[Nokia N810|N810]] (OS2008/Maemo4.1/Diablo)
* [[Nokia N900]] (OS2009/Maemo5/[[Open development/Maemo roadmap/Fremantle|Fremantle]])

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

Qt can be [[Qt4_Hildon#Installing_Qt_packages_in_Scratchbox|installed in scratchbox]] for development. For applications that use Qt and are installed via the application manager, the necessary Qt packages will automatically be installed.

=[[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.. [[Qt4HildonApplications|this]] is the place you would like to check;

=[[Image:Help-contents.png]] Documentation=

== Qt ==

* [[Qt4 Hildon|Qt 4 Hildon]] developing with Qt for Maemo
* [[QML]]

== Non-Qt documentation ==

* 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

== Further reading ==

* [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
* [http://wiki.forum.nokia.com/index.php/Qt_for_Maemo_Developers_Guide Qt for Maemo Developers Guide, Forum Nokia]
* [http://www.forum.nokia.com/Tools_Docs_and_Code/Documentation/Maemo.xhtml Maemo documentation, mostly about Qt, Forum Nokia]
* [http://doc.trolltech.com/3.2/how-to-learn-qt.html How to learn Qt, Trolltech]
* [http://qt.nokia.com/developer/books Books] listed at qt.nokia.com
* [http://talk.maemo.org/showthread.php?t=39879 Qt4 hello world with python in 30 minutes]

=[[Image:Bug.png]] Bug tracking=
* Diablo & Fremantle 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

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Qt for Maemo Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Old qt4.garage.maemo.org forum]
* IRC
** Official Qt for Maemo IRC Channel
** 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]

[[Category:Qt]]

Qt-Maemo

2010-03-26T10:36:11Z

192.100.124.219: /* Image:Kblogger.png‎ News */

__NOTOC__

=[[Image:Kblogger.png‎ ]] News=
22 Mar 10 - Qt 4.6.2 has replaced Qt 4.5.3 into SDK PR 1.2. Run apt-get update && apt-get upgrade to update it.
25 Feb 10 - [http://labs.trolltech.com/blogs/2010/02/24/qt-for-maemo-5-home-screen-widgets/ How to make Qt Desktop Widgets] 
15 Feb 10 - Qt 4.6.2 is out. Qt Mobility (beta1) packages are in extras-devel. 
20 Jan 10 - [http://www.anselmolsm.org/blog/qt-mobile-demos-in-extras-devel/ Qt Mobile Demos in extras-devel] 
19 Jan 10 - [http://qt.nokia.com/developer/qt-for-maemo-developers Qt 4.6 for Maemo 5 going Beta] 
15 Jan 10 - New Qt 4.5.3~git20090723-0maemo6 packages are now in Fremantle [[Maemo_5/PR1.1|PR 1.1]] 
22 Dec 09 - [http://wiki.maemo.org/MADDE/Qt_Example Qt example] for [http://wiki.maemo.org/MADDE MADDE ] ([http://talk.maemo.org/showthread.php?t=38075 talk thread]) 
17 Dec 09 - [http://labs.trolltech.com/blogs/2009/12/17/qt-declarative-for-maemo-5/Qt declarative hits Maemo extras-devel repository] 
11 Dec 09 - Bye bye old static web pages.. all our pages are now in the Maemo Wiki. Old website is [http://qt4.garage.maemo.org/index-old.html here] 

=[[Image:Intro.png]] What is Qt?=
Qt (pronounced as the English word "cute") is a cross-platform application development framework. More information is available at the [http://qt.nokia.com/ Qt website].

=[[Image:Rocket.png]] Maemo Qt main features=
* Hildon Style, so applications look like Hildon/GTK+ applications
* Hildon Input Method, so applications can use the virtual keyboard
* Hildon-specific widgets
** partial support in Qt 4.5
** Qt 4.6 will have full support, and is currently a technology preview

= [[Image:Fileview-preview.png]] Maemo Qt in Action =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS

=[[Image:Pda.png]] Supported Maemo devices=
* [[Nokia N800]]/[[Nokia N810|N810]] (OS2008/Maemo4.1/Diablo)
* [[Nokia N900]] (OS2009/Maemo5/[[Open development/Maemo roadmap/Fremantle|Fremantle]])

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

Qt can be [[Qt4_Hildon#Installing_Qt_packages_in_Scratchbox|installed in scratchbox]] for development. For applications that use Qt and are installed via the application manager, the necessary Qt packages will automatically be installed.

=[[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.. [[Qt4HildonApplications|this]] is the place you would like to check;

=[[Image:Help-contents.png]] Documentation=

== Qt ==

* [[Qt4 Hildon|Qt 4 Hildon]] developing with Qt for Maemo
* [[QML]]

== Non-Qt documentation ==

* 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

== Further reading ==

* [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
* [http://wiki.forum.nokia.com/index.php/Qt_for_Maemo_Developers_Guide Qt for Maemo Developers Guide, Forum Nokia]
* [http://www.forum.nokia.com/Tools_Docs_and_Code/Documentation/Maemo.xhtml Maemo documentation, mostly about Qt, Forum Nokia]
* [http://doc.trolltech.com/3.2/how-to-learn-qt.html How to learn Qt, Trolltech]
* [http://qt.nokia.com/developer/books Books] listed at qt.nokia.com
* [http://talk.maemo.org/showthread.php?t=39879 Qt4 hello world with python in 30 minutes]

=[[Image:Bug.png]] Bug tracking=
* Diablo & Fremantle 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

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Qt for Maemo Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Old qt4.garage.maemo.org forum]
* IRC
** Official Qt for Maemo IRC Channel
** 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]

[[Category:Qt]]

Qt4 Hildon Legacy

2010-03-23T17:30:53Z

192.100.124.219: /* Fremantle */

= [[Image:Intro.png]] Introduction =

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 ==

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.

Read more about [http://maemo.org/intro/platform/ the Maemo platform] and a [http://maemo.org/intro/developer_overview/ developer overview].

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

To start to develop with Maemo Qt, we need to [[Documentation/Maemo_5_Final_SDK_Installation|install the Maemo SDK]].

== Installing Qt packages in Scratchbox ==
Maemo Qt developers offers a set of Qt packages for [[Open development/Maemo roadmap/Fremantle|Fremantle]] (Maemo5 - OS2009) and Diablo (Maemo4.1 - OS2008).

== Fremantle ==
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 ===
Since PR 1.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:
fakeroot apt-get update
fakeroot apt-get dist-upgrade

== Diablo ==
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==
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:
# 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 ===

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.

CMake projects usually have a <code>CMakeLists.txt</code> 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 default in [[:Category:Scratchbox|scratchbox]]. You can install it with the command:
fakeroot apt-get install cmake

== Running a Qt application in: ==
=== 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:

# Run Xephyr. It is able to run a [http://en.wikipedia.org/wiki/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: run-standalone.sh sets some variable needed by Qt to use the Hildon style.

=== Device ===
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, /home/user or /opt in Fremantle).

Fore example, if we want to run quassel (Qt IRC Client) we have to launch it with:
su -c ./quassel user

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

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.

==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:
./qt-test-application -style windows

* 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 using method ''statusBar()->show()'' in your class derived from QMainWindow.

===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:

* Qt 4.5 (Diablo and Fremantle)
#ifdef Q_WS_HILDON
//Specific hildon/Maemo5 code here
#endif

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)
contains(QT_CONFIG, hildon): {
message("Hello Hildon")
SOURCE += hildon.cpp
HEADER += hildon.h
FORMS += hildon.ui
}

* Qt 4.6 (Fremantle)
Q_WS_HILDON has been replaced by Q_WS_MAEMO_5 in Qt 4.6 and Qt 4.5 "contains(QT_CONFIG, hildon):{}" does same job of Qt 4.6 "maemo5 {}".

#ifdef Q_WS_MAEMO_5
//specific hildon/maemo5 code here
#endif

maemo5 {
message("Hello Hildon")
SOURCE += hildon.cpp
HEADER += hildon.h
FORMS += hildon.ui
}

== Home widget interaction ==
{{main|Qt4 and Hildon home widget interaction}}

==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].

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

{{main|Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide}}

'''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.
[http://chaos.troll.no/~harald/gdb7/ Here you can find GDB7 for fremantle x86 and armel].
/usr/local/bin/gdb7 ./myapp

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

== OProfile ==

{{main|Documentation/devtools/maemo5/oprofile}}

== Valgrind ==

{{main|Documentation/devtools/maemo5/valgrind}}

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

{{main|Packaging a Qt application}}

= [[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 (Qt 4.5)=

==Kinetic scrolling==
Kinetic scrolling is enabled by default in QListWidgets and is supported by any Qt widget that inherits QScrollArea.
Any item view widgets (QTreeView/QTreeWidget, QListView, QTableView/QTableWidget...) can use fingerscroll if it has "FingerScrollable" dynamic property set to true.
Eg:
QTableWidget *table = new QTableWidget(this);
table->setProperty("FingerScrollable", true);

NOTE: Available in Qt > 4.5.3-xxxxx-maemo4

==Hildon-Desktop widgets==

{{main|/Qt Hildon Widgets}}

They are supported by Qt. An example (qt-example-hildondesktopwidget) is available in extras-devel.

==Hildon menus==
Maemo5 menus are created using QActions available in menu bar.
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.
* Pkgs > qt-4.5.3-xxxx-maemo4 shows Maemo5 menus automatically

Note: Maemo5 policy doesn't allow application to have more than 10 items.

==Stackable windows==
http://maemomm.garage.maemo.org/docs/tutorial/figures/stackable-window.png
Are supported by Qt. To create them you need to create a MainWindow child of another Main window.

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);

''Note: this is not entirely accurate, see''

http://qt.nokia.com/doc/qt-maemo-4.6/maemo5-stackedwindows.html

==Raise a Qt application in background==
QWidget::activateWindow() does the job.

Implemented in Qt packages >= qt-4.5.3-xxxx-maemo6
== How to minimize a Qt application? ==
QDBusConnection c = QDBusConnection::sessionBus();
QDBusMessage m = QDBusMessage::createSignal("/","com.nokia.hildon_desktop","exit_app_view");
c.send(m);

==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.

#ifdef Q_WS_HILDON
//Includes for portrait mode support
# include <X11/Xlib.h>
# include <X11/Xatom.h>
# include <QtGui/QX11Info>
#endif

#ifndef Q_WS_HILDON
int value = 1;
Atom portraitSupport = XInternAtom(QX11Info::display(), "_HILDON_PORTRAIT_MODE_SUPPORT", false);
Atom portraitRequest = XInternAtom(QX11Info::display(), "_HILDON_PORTRAIT_MODE_REQUEST", false);
XChangeProperty(QX11Info::display(), winId(), portraitSupport, XA_CARDINAL, 32, PropModeReplace, (uchar *)&value, 1);
XChangeProperty(QX11Info::display(), winId(), portraitRequest, XA_CARDINAL, 32, PropModeReplace, (uchar *)&value, 1);
#endif

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.

== QDockWidgets ==
QDockWidgets are not finger friendly widgets. They should not be used in Maemo.
In case you are porting an application to Maemo maybe you want to do
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.

== QPrint* and QSystemTray support missing ==
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.

== QSplashScreen not fully compatible with Hildon-Desktop ==
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.

As a workaround for the problem you can set a window property that tells HD to skip the transitions:

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);
}

== QToolBar limitations ==
Adding a QToolBar to a QMainWindow will always result in a toolbar at the
bottom of the screen. (Justification/Workarounds?)

 

=FREMANTLE (Qt 4.6)=
Here an example that shows several maemo5 Qt widgets in Qt 4.6.

http://qt.nokia.com/doc/qt-maemo-4.6/examples-maemo5.html

http://qt.gitorious.org/+qt-developers/qt/x11-maemo/trees/986340bb5e4b69ceb0a959c2a067a1ed5e504d50/examples/maemo5/widgets

==Finger Scrolling==

Kinetic scrolling is present by default in most scrolling widgets, eg. <code>QTextBrowser</code>, <code>QTableView</code>. If you want to tweak the kinetic scrolling parameters like inertia and acceleration then you can instaniate a <code>QAbstractKineticScroller</code> object like this:

QAbstractKineticScroller ks =
scrollArea->property("kineticScroller").value<QAbstractKineticScroller *>();

where scrollArea could be <code>QScrollArea</code> with some widgets added to it, or you could use implementations like <code>QTextBrowser</code>.

You can tweak scrolling like this:
ks->setDragInertia( (double)value / 100.0)
ks->setMode(QAbstractKineticScroller::PushMode)

etc., refer to the examples here for details: http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/examples/maemo5/kineticscroller/main.cpp

==QSplashScreen==
Should be fixed in Qt 4.6. SplashWindow type is not supported by Fremantle WM. Qt 4.6 display splash screen using popup window type.

==Orientation==
[http://qt.nokia.com/doc/qt-maemo-4.6/maemo5-rotation.html Official documentation]

==Maemo5 Readme file==
There is a [http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/README.maemo5 README file in Qt 4.6 source tree].

= [[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.

==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.

== 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==

{{main|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 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==
[[QML]] is a GUI interface building scripting language for Qt. Check out the [[QML-EnhancedCalcExample | QML calculator example]].

=[[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?''
: <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?
: <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
: 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.
: <pre>http://qt4.garage.maemo.org/patches/qt4-missing-header.tgz</pre>

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

Qt4 Hildon Legacy

2010-03-23T17:30:16Z

192.100.124.219: /* Using Qt 4.6 in Fremantle */

= [[Image:Intro.png]] Introduction =

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 ==

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.

Read more about [http://maemo.org/intro/platform/ the Maemo platform] and a [http://maemo.org/intro/developer_overview/ developer overview].

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

To start to develop with Maemo Qt, we need to [[Documentation/Maemo_5_Final_SDK_Installation|install the Maemo SDK]].

== Installing Qt packages in Scratchbox ==
Maemo Qt developers offers a set of Qt packages for [[Open development/Maemo roadmap/Fremantle|Fremantle]] (Maemo5 - OS2009) and Diablo (Maemo4.1 - OS2008).

== Fremantle ==
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-gui libqt4-dev

=== Using Qt 4.6 in Fremantle ===
Since PR 1.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:
fakeroot apt-get update
fakeroot apt-get dist-upgrade

== Diablo ==
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==
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:
# 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 ===

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.

CMake projects usually have a <code>CMakeLists.txt</code> 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 default in [[:Category:Scratchbox|scratchbox]]. You can install it with the command:
fakeroot apt-get install cmake

== Running a Qt application in: ==
=== 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:

# Run Xephyr. It is able to run a [http://en.wikipedia.org/wiki/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: run-standalone.sh sets some variable needed by Qt to use the Hildon style.

=== Device ===
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, /home/user or /opt in Fremantle).

Fore example, if we want to run quassel (Qt IRC Client) we have to launch it with:
su -c ./quassel user

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

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.

==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:
./qt-test-application -style windows

* 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 using method ''statusBar()->show()'' in your class derived from QMainWindow.

===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:

* Qt 4.5 (Diablo and Fremantle)
#ifdef Q_WS_HILDON
//Specific hildon/Maemo5 code here
#endif

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)
contains(QT_CONFIG, hildon): {
message("Hello Hildon")
SOURCE += hildon.cpp
HEADER += hildon.h
FORMS += hildon.ui
}

* Qt 4.6 (Fremantle)
Q_WS_HILDON has been replaced by Q_WS_MAEMO_5 in Qt 4.6 and Qt 4.5 "contains(QT_CONFIG, hildon):{}" does same job of Qt 4.6 "maemo5 {}".

#ifdef Q_WS_MAEMO_5
//specific hildon/maemo5 code here
#endif

maemo5 {
message("Hello Hildon")
SOURCE += hildon.cpp
HEADER += hildon.h
FORMS += hildon.ui
}

== Home widget interaction ==
{{main|Qt4 and Hildon home widget interaction}}

==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].

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

{{main|Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide}}

'''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.
[http://chaos.troll.no/~harald/gdb7/ Here you can find GDB7 for fremantle x86 and armel].
/usr/local/bin/gdb7 ./myapp

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

== OProfile ==

{{main|Documentation/devtools/maemo5/oprofile}}

== Valgrind ==

{{main|Documentation/devtools/maemo5/valgrind}}

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

{{main|Packaging a Qt application}}

= [[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 (Qt 4.5)=

==Kinetic scrolling==
Kinetic scrolling is enabled by default in QListWidgets and is supported by any Qt widget that inherits QScrollArea.
Any item view widgets (QTreeView/QTreeWidget, QListView, QTableView/QTableWidget...) can use fingerscroll if it has "FingerScrollable" dynamic property set to true.
Eg:
QTableWidget *table = new QTableWidget(this);
table->setProperty("FingerScrollable", true);

NOTE: Available in Qt > 4.5.3-xxxxx-maemo4

==Hildon-Desktop widgets==

{{main|/Qt Hildon Widgets}}

They are supported by Qt. An example (qt-example-hildondesktopwidget) is available in extras-devel.

==Hildon menus==
Maemo5 menus are created using QActions available in menu bar.
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.
* Pkgs > qt-4.5.3-xxxx-maemo4 shows Maemo5 menus automatically

Note: Maemo5 policy doesn't allow application to have more than 10 items.

==Stackable windows==
http://maemomm.garage.maemo.org/docs/tutorial/figures/stackable-window.png
Are supported by Qt. To create them you need to create a MainWindow child of another Main window.

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);

''Note: this is not entirely accurate, see''

http://qt.nokia.com/doc/qt-maemo-4.6/maemo5-stackedwindows.html

==Raise a Qt application in background==
QWidget::activateWindow() does the job.

Implemented in Qt packages >= qt-4.5.3-xxxx-maemo6
== How to minimize a Qt application? ==
QDBusConnection c = QDBusConnection::sessionBus();
QDBusMessage m = QDBusMessage::createSignal("/","com.nokia.hildon_desktop","exit_app_view");
c.send(m);

==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.

#ifdef Q_WS_HILDON
//Includes for portrait mode support
# include <X11/Xlib.h>
# include <X11/Xatom.h>
# include <QtGui/QX11Info>
#endif

#ifndef Q_WS_HILDON
int value = 1;
Atom portraitSupport = XInternAtom(QX11Info::display(), "_HILDON_PORTRAIT_MODE_SUPPORT", false);
Atom portraitRequest = XInternAtom(QX11Info::display(), "_HILDON_PORTRAIT_MODE_REQUEST", false);
XChangeProperty(QX11Info::display(), winId(), portraitSupport, XA_CARDINAL, 32, PropModeReplace, (uchar *)&value, 1);
XChangeProperty(QX11Info::display(), winId(), portraitRequest, XA_CARDINAL, 32, PropModeReplace, (uchar *)&value, 1);
#endif

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.

== QDockWidgets ==
QDockWidgets are not finger friendly widgets. They should not be used in Maemo.
In case you are porting an application to Maemo maybe you want to do
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.

== QPrint* and QSystemTray support missing ==
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.

== QSplashScreen not fully compatible with Hildon-Desktop ==
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.

As a workaround for the problem you can set a window property that tells HD to skip the transitions:

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);
}

== QToolBar limitations ==
Adding a QToolBar to a QMainWindow will always result in a toolbar at the
bottom of the screen. (Justification/Workarounds?)

 

=FREMANTLE (Qt 4.6)=
Here an example that shows several maemo5 Qt widgets in Qt 4.6.

http://qt.nokia.com/doc/qt-maemo-4.6/examples-maemo5.html

http://qt.gitorious.org/+qt-developers/qt/x11-maemo/trees/986340bb5e4b69ceb0a959c2a067a1ed5e504d50/examples/maemo5/widgets

==Finger Scrolling==

Kinetic scrolling is present by default in most scrolling widgets, eg. <code>QTextBrowser</code>, <code>QTableView</code>. If you want to tweak the kinetic scrolling parameters like inertia and acceleration then you can instaniate a <code>QAbstractKineticScroller</code> object like this:

QAbstractKineticScroller ks =
scrollArea->property("kineticScroller").value<QAbstractKineticScroller *>();

where scrollArea could be <code>QScrollArea</code> with some widgets added to it, or you could use implementations like <code>QTextBrowser</code>.

You can tweak scrolling like this:
ks->setDragInertia( (double)value / 100.0)
ks->setMode(QAbstractKineticScroller::PushMode)

etc., refer to the examples here for details: http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/examples/maemo5/kineticscroller/main.cpp

==QSplashScreen==
Should be fixed in Qt 4.6. SplashWindow type is not supported by Fremantle WM. Qt 4.6 display splash screen using popup window type.

==Orientation==
[http://qt.nokia.com/doc/qt-maemo-4.6/maemo5-rotation.html Official documentation]

==Maemo5 Readme file==
There is a [http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/README.maemo5 README file in Qt 4.6 source tree].

= [[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.

==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.

== 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==

{{main|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 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==
[[QML]] is a GUI interface building scripting language for Qt. Check out the [[QML-EnhancedCalcExample | QML calculator example]].

=[[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?''
: <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?
: <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
: 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.
: <pre>http://qt4.garage.maemo.org/patches/qt4-missing-header.tgz</pre>

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

Qt-Maemo

2010-02-25T08:18:20Z

192.100.124.219: /* Image:Kblogger.png‎ News */

__NOTOC__

=[[Image:Kblogger.png‎ ]] News=
25 Feb 10 - [http://labs.trolltech.com/blogs/2010/02/24/qt-for-maemo-5-home-screen-widgets/ How to make Qt Desktop Widgets] 
15 Feb 10 - Qt 4.6.2 is out. Qt Mobility (beta1) packages are in extras-devel. 
20 Jan 10 - [http://www.anselmolsm.org/blog/qt-mobile-demos-in-extras-devel/ Qt Mobile Demos in extras-devel] 
19 Jan 10 - [http://qt.nokia.com/developer/qt-for-maemo-developers Qt 4.6 for Maemo 5 going Beta] 
15 Jan 10 - New Qt 4.5.3~git20090723-0maemo6 packages are now in Fremantle [[Maemo_5/PR1.1|PR 1.1]] 
22 Dec 09 - [http://wiki.maemo.org/MADDE/Qt_Example Qt example] for [http://wiki.maemo.org/MADDE MADDE ] ([http://talk.maemo.org/showthread.php?t=38075 talk thread]) 
17 Dec 09 - [http://labs.trolltech.com/blogs/2009/12/17/qt-declarative-for-maemo-5/Qt declarative hits Maemo extras-devel repository] 
11 Dec 09 - Bye bye old static web pages.. all our pages are now in the Maemo Wiki. Old website is [http://qt4.garage.maemo.org/index-old.html here] 

=[[Image:Intro.png]] What is Qt?=
Qt (pronounced as the English word "cute") is a cross-platform application development framework. More information is available at the [http://qt.nokia.com/ Qt website].

=[[Image:Rocket.png]] Maemo Qt main features=
* Hildon Style, so applications look like Hildon/GTK+ applications
* Hildon Input Method, so applications can use the virtual keyboard
* Hildon-specific widgets
** partial support in Qt 4.5
** Qt 4.6 will have full support, and is currently a technology preview

= [[Image:Fileview-preview.png]] Maemo Qt in Action =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS

=[[Image:Pda.png]] Supported Maemo devices=
* [[Nokia N800]]/[[Nokia N810|N810]] (OS2008/Maemo4.1/Diablo)
* [[Nokia N900]] (OS2009/Maemo5/[[Open development/Maemo roadmap/Fremantle|Fremantle]])

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

Qt can be [[Qt4_Hildon#Installing_Qt_packages_in_Scratchbox|installed in scratchbox]] for development. For applications that use Qt and are installed via the application manager, the necessary Qt packages will automatically be installed.

=[[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.. [[Qt4HildonApplications|this]] is the place you would like to check;

=[[Image:Help-contents.png]] Documentation=

== Qt ==

* [[Qt4 Hildon|Qt 4 Hildon]] developing with Qt for Maemo
* [[QML]]

== Non-Qt documentation ==

* 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

== Further reading ==

* [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
* [http://wiki.forum.nokia.com/index.php/Qt_for_Maemo_Developers_Guide Qt for Maemo Developers Guide, Forum Nokia]
* [http://www.forum.nokia.com/Tools_Docs_and_Code/Documentation/Maemo.xhtml Maemo documentation, mostly about Qt, Forum Nokia]
* [http://doc.trolltech.com/3.2/how-to-learn-qt.html How to learn Qt, Trolltech]
* [http://qt.nokia.com/developer/books Books] listed at qt.nokia.com
* [http://talk.maemo.org/showthread.php?t=39879 Qt4 hello world with python in 30 minutes]

=[[Image:Bug.png]] Bug tracking=
* Diablo & Fremantle 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

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Qt for Maemo Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Old qt4.garage.maemo.org forum]
* IRC
** Official Qt for Maemo IRC Channel
** 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]

[[Category:Qt]]

Qt4 Hildon Legacy

2010-01-20T07:23:32Z

192.100.124.219: /* FREMANTLE (Qt 4.6) */

[[Image:MaemoQtPicture.png]]
 
== [[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...]

 

== [[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
apt-get update
4. Install Qt packages with
apt-get install libqt4-dev

==== Fremantle ====
You don't need to add any extra repository for Fremantle since Qt packages are already available into the SDK. You can find more information on installing Qt on Fremantle, and help improve Qt on Maemo, [[QT/Testing | on the Qt testing page]].

Then you can install Qt with:
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install libqt4-gui libqt4-dev

==== Using Qt 4.6 Betas in Fremantle ====
If you want to test your applications with the latest Qt 4.6 Beta version, either compile it [[Qt_Maemo_Git_Process|directly from the git repos]] or install the libqt4-maemo5-dev package.

For the latter you need to enable access to the extra devel repositories first (if you haven't done so yet). Inside of scratchbox, for your i486 target (ARM is very similar), do the following:

[sbox-FREMANTLE_X86: ~] > fakeroot echo "deb http://repository.maemo.org/extras/ fremantle free non-free" >> /etc/apt/sources.list
[sbox-FREMANTLE_X86: ~] > fakeroot echo "deb-src http://repository.maemo.org/extras/ fremantle free" >> /etc/apt/sources.list
[sbox-FREMANTLE_X86: ~] > fakeroot echo "deb http://repository.maemo.org/extras-devel fremantle free non-free" >> /etc/apt/sources.list
[sbox-FREMANTLE_X86: ~] > fakeroot echo "deb-src http://repository.maemo.org/extras-devel fremantle free" >> /etc/apt/sources.list

To install the tech preview:
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get update
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get remove libqt4*
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install libqt4-maemo5-dev

Qt is installed to /opt/qt4-maemo5.

If you happen to use autotools, this will recompile the code against the beta:
[sbox-FREMANTLE_X86: ~] > cd ~/your/project/folder
[sbox-FREMANTLE_X86: ~] > make distclean #dont worry if it fails
[sbox-FREMANTLE_X86: ~] > ./autogen.sh QT_PATH=/opt/qt4-maemo5/bin
[sbox-FREMANTLE_X86: ~] > make

For qmake you might have to set the QT_INSTALL_PREFIX correctly.

===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]
qmake -project
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 (on the device at least).

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 default in [[scratchbox]]. You can install it with
fakeroot apt-get install cmake

===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.
Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb

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

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

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

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:
Nokia-N900-44-1:/home/user# su -c ./quassel user

 

== [[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:
./qt-test-application -style windows

* 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 using method ''statusBar()->show()'' in your class derived from QMainWindow.

====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:

* Qt 4.5 (Diablo and Fremantle)
#ifdef Q_WS_HILDON
//Specific hildon/Maemo5 code here
#endif

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)
contains(QT_CONFIG, hildon): {
message("Hello Hildon")
SOURCE += hildon.cpp
HEADER += hildon.h
FORMS += hildon.ui
}

* Qt 4.6 (Fremantle)
Q_WS_HILDON has been replaced by Q_WS_MAEMO_5 in Qt 4.6 and Qt 4.5 "contains(QT_CONFIG, hildon):{}" does same job of Qt 4.6 "maemo5 {}".

#ifdef Q_WS_MAEMO_5
//specific hildon/maemo5 code here
#endif

maemo5 {
message("Hello Hildon")
SOURCE += hildon.cpp
HEADER += hildon.h
FORMS += hildon.ui
}

===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].

 
 

== [[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====
=====Using gdb=====
Fast way is running gdb ./your app.

=====Using gdb & gdbserver=====
<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>

'''Note''': Fremantle Gdb 6.8 crashes in x86 and gives messed up backtraces onto the device. Using gdb 7.0 is recommended. You can get gdb 7.0 sources fromhttp://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.
[http://chaos.troll.no/~harald/gdb7/ Here you can find GDB7 for fremantle x86 and armel]

===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]

 

== [[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 ===
Valgrind runs programs on a virtual processor and can detect memory errors (e.g., misuse of malloc and free) and race conditions in multithread programs.

It performs a [http://en.wikipedia.org/wiki/Dynamic_program_analysis Dynamic program analysis] (In a few words,dynamic stands for analysis performed while executing the program).

It's very useful tool to track memory leaks

run-standalone.sh valgrind --tool=memcheck --leak-check=yes ./Application
or
run-standalone.sh valgrind --leak-check=full ./Application

You can learn more about valngrind at http://www.cprogramming.com/debugging/valgrind.html

 

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

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

* TODO
 

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

{{main|Packaging a Qt application}}

 
== [[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 (Qt 4.5)===

====Kinetic scrolling====
Kinetic scrolling is enabled by default in QListWidgets and is supported by any Qt widget that inherits QScrollArea.
Any item view widgets (QTreeView/QTreeWidget, QListView, QTableView/QTableWidget...) can use fingerscroll if it has "FingerScrollable" dynamic property set to true.
Eg:
QTableWidget *table = new QTableWidget(this);
table->setProperty("FingerScrollable", true);

NOTE: Available in Qt > 4.5.3-xxxxx-maemo4

====Hildon-Desktop widgets====
They are supported by Qt. An example (qt-example-hildondesktopwidget) is available in extras-devel.

====Hildon menus====
Maemo5 menus are created using QActions available in menu bar.
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.
* Pkgs > qt-4.5.3-xxxx-maemo4 shows Maemo5 menus automatically

Note: Maemo5 policy doesn't allow application to have more than 10 items.

====Stackable windows====
http://maemomm.garage.maemo.org/docs/tutorial/figures/stackable-window.png
Are supported by Qt. To create them you need to create a MainWindow child of another Main window.

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);

====Raise a Qt application in background====
QWidget::activateWindow() does the job.

Implemented in Qt packages >= qt-4.5.3-xxxx-maemo6
==== How to minimize a Qt application? ====
QDBusConnection c = QDBusConnection::sessionBus();
QDBusMessage m = QDBusMessage::createSignal("/","com.nokia.hildon_desktop","exit_app_view");
c.send(m);

====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.

#ifdef Q_WS_HILDON
//Includes for portrait mode support
# include <X11/Xlib.h>
# include <X11/Xatom.h>
# include <QtGui/QX11Info>
#endif

#ifndef Q_WS_HILDON
int value = 1;
Atom portraitSupport = XInternAtom(QX11Info::display(), "_HILDON_PORTRAIT_MODE_SUPPORT", false);
Atom portraitRequest = XInternAtom(QX11Info::display(), "_HILDON_PORTRAIT_MODE_REQUEST", false);
XChangeProperty(QX11Info::display(), winId(), portraitSupport, XA_CARDINAL, 32, PropModeReplace, (uchar *)&value, 1);
XChangeProperty(QX11Info::display(), winId(), portraitRequest, XA_CARDINAL, 32, PropModeReplace, (uchar *)&value, 1);
#endif

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.

==== QDockWidgets ====
QDockWidgets are not finger friendly widgets. They should not be used in Maemo.
In case you are porting an application to Maemo maybe you want to do
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.

==== QPrint* and QSystemTray support missing ====
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.

==== QSplashScreen not fully compatible with Hildon-Desktop ====
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.

 

===FREMANTLE (Qt 4.6)===
Here an example that shows several maemo5 Qt widgets in Qt 4.6.

http://qt.nokia.com/doc/qt-maemo-4.6/examples-maemo5.html

http://qt.gitorious.org/+qt-developers/qt/x11-maemo/trees/986340bb5e4b69ceb0a959c2a067a1ed5e504d50/examples/maemo5/widgets

====Finger Scrolling====
* Qt 4.6 tp2
<s>QListView listView;
new QMaemo5KineticScroller(&listView);</s>

<s>The ctor for QMaemo5KineticScroller for widgets seems protected now, hence the above cant be done.
So to have Kinetic Scrolling we can do this :

QAbstractScrollArea areaToScroll
new QMaemo5KineticScroller(&areaToScroll);</s>

Kinetic scrolling is *now* present by default in most scrolling widgets
eg. QTextBrowser, QTableView

If you want to tweak the kinetic scrolling parameters like inertia and acceleration
then you can instaniate a QAbstractKineticScroller object like this.

QAbstractKineticScroller ks =
scrollArea->property("kineticScroller").value<QAbstractKineticScroller *>();

where scrollArea could be QScrollArea with some widgets added to it
or you could use implementations like QTextBrowser

you can tweak scrolling like this
ks->setDragInertia( (double)value / 100.0)
ks->setMode(QAbstractKineticScroller::PushMode)

etc... , refer to the examples here for details ==> [http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/examples/maemo5/kineticscroller/main.cpp]

====QSplashScreen====
Should be fixed in Qt 4.6. SplashWindow type is not supported by Fremantle WM. Qt 4.6 display splash screen using popup window type.

====Orientation====
[http://qt.nokia.com/doc/qt-maemo-4.6/maemo5-rotation.html Official documentation]
====Maemo5 Readme file====
There is a README file in Qt 4.6 source tree. You could check it clicking [http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/README.maemo5 Here].

== [[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+w34 origin/qt-n900+w34
git checkout -b qt-mer origin/qt-mer

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

===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.
 

==[[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

===QML===
http://wiki.maemo.org/QML

== References ==

<references/>

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

Qt-Maemo

2010-01-20T07:17:03Z

192.100.124.219: /* Image:Kblogger.png‎ News */

__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">
20 Gen 09 - [http://www.anselmolsm.org/blog/qt-mobile-demos-in-extras-devel/ Qt Mobile Demos in extras-devel] 

19 Gen 09 - Qt 4.6 for Maemo 5 going Beta 
15 Gen 09 - New Qt 4.5.3~git20090723-0maemo6 packages are now in Fremantle PR 1.1. 

22 Dec 09 - [http://wiki.maemo.org/MADDE/Qt_Example Qt example] for [http://wiki.maemo.org/MADDE MADDE ] ([http://talk.maemo.org/showthread.php?t=38075 talk thread]) 

17 Dec 09 - Qt declarative hits Maemo extras-devel repository [http://labs.trolltech.com/blogs/2009/12/17/qt-declarative-for-maemo-5/ more info here] 

11 Dec 09 - 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>
<li>
[[Image:OtherNews.jpg‎]] 
<rss title="off" desc="off" number="5" time="3600" text>http://labs.trolltech.com/blogs/feed/rss/</rss>
</li>
<li>
[[Image:LastCommits.jpg‎]] 
<rss title="off" desc="off" number="5" time="3600" text>http://pipes.yahoo.com/pipes/pipe.run?_id=249549b5f3ea9af37a077bb103af6614&_render=rss</rss>
</li>
</ul>
</div></div></div></div></div></div></div></div></div>
 
 
.

=[[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.
 
 

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

= [[Image:Fileview-preview.png]] Maemo Qt in Actions =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Qt for Maemo Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Old qt4.garage.maemo.org forum]
* IRC
** Official Qt for Maemo IRC Channel
** 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]

Qt4 Hildon Legacy

2010-01-19T15:14:09Z

192.100.124.219: /* Checking out all the remote branches */

[[Image:MaemoQtPicture.png]]
 
== [[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...]

 

== [[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
apt-get update
4. Install Qt packages with
apt-get install libqt4-dev

==== Fremantle ====
You don't need to add any extra repository for Fremantle since Qt packages are already available into the SDK. You can find more information on installing Qt on Fremantle, and help improve Qt on Maemo, [[QT/Testing | on the Qt testing page]].

Then you can install Qt with:
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install libqt4-gui libqt4-dev

==== Using Qt 4.6 Betas in Fremantle ====
If you want to test your applications with the latest Qt 4.6 Beta version, either compile it [[Qt_Maemo_Git_Process|directly from the git repos]] or install the libqt4-maemo5-dev package.

For the latter you need to enable access to the extra devel repositories first (if you haven't done so yet). Inside of scratchbox, for your i486 target (ARM is very similar), do the following:

[sbox-FREMANTLE_X86: ~] > fakeroot echo "deb http://repository.maemo.org/extras/ fremantle free non-free" >> /etc/apt/sources.list
[sbox-FREMANTLE_X86: ~] > fakeroot echo "deb-src http://repository.maemo.org/extras/ fremantle free" >> /etc/apt/sources.list
[sbox-FREMANTLE_X86: ~] > fakeroot echo "deb http://repository.maemo.org/extras-devel fremantle free non-free" >> /etc/apt/sources.list
[sbox-FREMANTLE_X86: ~] > fakeroot echo "deb-src http://repository.maemo.org/extras-devel fremantle free" >> /etc/apt/sources.list

To install the tech preview:
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get update
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get remove libqt4*
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install libqt4-maemo5-dev

Qt is installed to /opt/qt4-maemo5.

If you happen to use autotools, this will recompile the code against the beta:
[sbox-FREMANTLE_X86: ~] > cd ~/your/project/folder
[sbox-FREMANTLE_X86: ~] > make distclean #dont worry if it fails
[sbox-FREMANTLE_X86: ~] > ./autogen.sh QT_PATH=/opt/qt4-maemo5/bin
[sbox-FREMANTLE_X86: ~] > make

For qmake you might have to set the QT_INSTALL_PREFIX correctly.

===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]
qmake -project
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 (on the device at least).

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 default in [[scratchbox]]. You can install it with
fakeroot apt-get install cmake

===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.
Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb

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

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

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

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:
Nokia-N900-44-1:/home/user# su -c ./quassel user

 

== [[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:
./qt-test-application -style windows

* 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 using method ''statusBar()->show()'' in your class derived from QMainWindow.

====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:

* Qt 4.5 (Diablo and Fremantle)
#ifdef Q_WS_HILDON
//Specific hildon/Maemo5 code here
#endif

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)
contains(QT_CONFIG, hildon): {
message("Hello Hildon")
SOURCE += hildon.cpp
HEADER += hildon.h
FORMS += hildon.ui
}

* Qt 4.6 (Fremantle)
Q_WS_HILDON has been replaced by Q_WS_MAEMO_5 in Qt 4.6 and Qt 4.5 "contains(QT_CONFIG, hildon):{}" does same job of Qt 4.6 "maemo5 {}".

#ifdef Q_WS_MAEMO_5
//specific hildon/maemo5 code here
#endif

maemo5 {
message("Hello Hildon")
SOURCE += hildon.cpp
HEADER += hildon.h
FORMS += hildon.ui
}

===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].

 
 

== [[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====
=====Using gdb=====
Fast way is running gdb ./your app.

=====Using gdb & gdbserver=====
<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>

'''Note''': Fremantle Gdb 6.8 crashes in x86 and gives messed up backtraces onto the device. Using gdb 7.0 is recommended. You can get gdb 7.0 sources fromhttp://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.
[http://chaos.troll.no/~harald/gdb7/ Here you can find GDB7 for fremantle x86 and armel]

===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]

 

== [[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 ===
Valgrind runs programs on a virtual processor and can detect memory errors (e.g., misuse of malloc and free) and race conditions in multithread programs.

It performs a [http://en.wikipedia.org/wiki/Dynamic_program_analysis Dynamic program analysis] (In a few words,dynamic stands for analysis performed while executing the program).

It's very useful tool to track memory leaks

run-standalone.sh valgrind --tool=memcheck --leak-check=yes ./Application
or
run-standalone.sh valgrind --leak-check=full ./Application

You can learn more about valngrind at http://www.cprogramming.com/debugging/valgrind.html

 

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

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

* TODO
 

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

{{main|Packaging a Qt application}}

 
== [[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 (Qt 4.5)===

====Kinetic scrolling====
Kinetic scrolling is enabled by default in QListWidgets and is supported by any Qt widget that inherits QScrollArea.
Any item view widgets (QTreeView/QTreeWidget, QListView, QTableView/QTableWidget...) can use fingerscroll if it has "FingerScrollable" dynamic property set to true.
Eg:
QTableWidget *table = new QTableWidget(this);
table->setProperty("FingerScrollable", true);

NOTE: Available in Qt > 4.5.3-xxxxx-maemo4

====Hildon-Desktop widgets====
They are supported by Qt. An example (qt-example-hildondesktopwidget) is available in extras-devel.

====Hildon menus====
Maemo5 menus are created using QActions available in menu bar.
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.
* Pkgs > qt-4.5.3-xxxx-maemo4 shows Maemo5 menus automatically

Note: Maemo5 policy doesn't allow application to have more than 10 items.

====Stackable windows====
http://maemomm.garage.maemo.org/docs/tutorial/figures/stackable-window.png
Are supported by Qt. To create them you need to create a MainWindow child of another Main window.

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);

====Raise a Qt application in background====
QWidget::activateWindow() does the job.

Implemented in Qt packages >= qt-4.5.3-xxxx-maemo6
==== How to minimize a Qt application? ====
QDBusConnection c = QDBusConnection::sessionBus();
QDBusMessage m = QDBusMessage::createSignal("/","com.nokia.hildon_desktop","exit_app_view");
c.send(m);

====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.

#ifdef Q_WS_HILDON
//Includes for portrait mode support
# include <X11/Xlib.h>
# include <X11/Xatom.h>
# include <QtGui/QX11Info>
#endif

#ifndef Q_WS_HILDON
int value = 1;
Atom portraitSupport = XInternAtom(QX11Info::display(), "_HILDON_PORTRAIT_MODE_SUPPORT", false);
Atom portraitRequest = XInternAtom(QX11Info::display(), "_HILDON_PORTRAIT_MODE_REQUEST", false);
XChangeProperty(QX11Info::display(), winId(), portraitSupport, XA_CARDINAL, 32, PropModeReplace, (uchar *)&value, 1);
XChangeProperty(QX11Info::display(), winId(), portraitRequest, XA_CARDINAL, 32, PropModeReplace, (uchar *)&value, 1);
#endif

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.

==== QDockWidgets ====
QDockWidgets are not finger friendly widgets. They should not be used in Maemo.
In case you are porting an application to Maemo maybe you want to do
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.

==== QPrint* and QSystemTray support missing ====
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.

==== QSplashScreen not fully compatible with Hildon-Desktop ====
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.

 

===FREMANTLE (Qt 4.6)===
Here an example that shows several maemo5 Qt widgets in Qt 4.6.

http://qt.gitorious.org/+qt-developers/qt/x11-maemo/trees/986340bb5e4b69ceb0a959c2a067a1ed5e504d50/examples/maemo5/widgets

====Finger Scrolling====
* Qt 4.6 tp2
<s>QListView listView;
new QMaemo5KineticScroller(&listView);</s>

<s>The ctor for QMaemo5KineticScroller for widgets seems protected now, hence the above cant be done.
So to have Kinetic Scrolling we can do this :

QAbstractScrollArea areaToScroll
new QMaemo5KineticScroller(&areaToScroll);</s>

Kinetic scrolling is *now* present by default in most scrolling widgets
eg. QTextBrowser, QTableView

If you want to tweak the kinetic scrolling parameters like inertia and acceleration
then you can instaniate a QAbstractKineticScroller object like this.

QAbstractKineticScroller ks =
scrollArea->property("kineticScroller").value<QAbstractKineticScroller *>();

where scrollArea could be QScrollArea with some widgets added to it
or you could use implementations like QTextBrowser

you can tweak scrolling like this
ks->setDragInertia( (double)value / 100.0)
ks->setMode(QAbstractKineticScroller::PushMode)

etc... , refer to the examples here for details ==> [http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/examples/maemo5/kineticscroller/main.cpp]

====QSplashScreen====
Should be fixed in Qt 4.6. SplashWindow type is not supported by Fremantle WM. Qt 4.6 display splash screen using popup window type.

====Maemo5 Readme file====
There is a README file in Qt 4.6 source tree. You could check it clicking [http://qt.gitorious.org/+qt-developers/qt/x11-maemo/blobs/4.6-fremantle/README.maemo5 Here].

== [[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+w34 origin/qt-n900+w34
git checkout -b qt-mer origin/qt-mer

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

===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.
 

==[[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

===QML===
http://wiki.maemo.org/QML

== References ==

<references/>

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

Qt-Maemo

2010-01-19T12:30:45Z

192.100.124.219: /* Image:Kblogger.png‎ News */

__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">
19 Gen 09 - Qt 4.6 for Maemo 5 going Beta 
15 Gen 09 - New Qt 4.5.3~git20090723-0maemo6 packages are now in Fremantle PR 1.1. 

22 Dec 09 - [http://wiki.maemo.org/MADDE/Qt_Example Qt example] for [http://wiki.maemo.org/MADDE MADDE ] ([http://talk.maemo.org/showthread.php?t=38075 talk thread]) 

17 Dec 09 - Qt declarative hits Maemo extras-devel repository [http://labs.trolltech.com/blogs/2009/12/17/qt-declarative-for-maemo-5/ more info here] 

11 Dec 09 - 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>
<li>
[[Image:OtherNews.jpg‎]] 
<rss title="off" desc="off" number="5" time="3600" text>http://labs.trolltech.com/blogs/feed/rss/</rss>
</li>
<li>
[[Image:LastCommits.jpg‎]] 
<rss title="off" desc="off" number="5" time="3600" text>http://pipes.yahoo.com/pipes/pipe.run?_id=249549b5f3ea9af37a077bb103af6614&_render=rss</rss>
</li>
</ul>
</div></div></div></div></div></div></div></div></div>
 
 
.

=[[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.
 
 

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

= [[Image:Fileview-preview.png]] Maemo Qt in Actions =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Qt for Maemo Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Old qt4.garage.maemo.org forum]
* IRC
** Official Qt for Maemo IRC Channel
** 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]

Qt-Maemo

2010-01-18T10:10:50Z

192.100.124.219: /* Image:Kblogger.png‎ News */

__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">
15 Gen 09 - New Qt 4.5.3~git20090723-0maemo6 packages are now in Fremantle PR 1.1. 

22 Dec 09 - [http://wiki.maemo.org/MADDE/Qt_Example Qt example] for [http://wiki.maemo.org/MADDE MADDE ] ([http://talk.maemo.org/showthread.php?t=38075 talk thread]) 

17 Dec 09 - Qt declarative hits Maemo extras-devel repository [http://labs.trolltech.com/blogs/2009/12/17/qt-declarative-for-maemo-5/ more info here] 

11 Dec 09 - 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>
<li>
[[Image:OtherNews.jpg‎]] 
<rss title="off" desc="off" number="5" time="3600" text>http://labs.trolltech.com/blogs/feed/rss/</rss>
</li>
<li>
[[Image:LastCommits.jpg‎]] 
<rss title="off" desc="off" number="5" time="3600" text>http://pipes.yahoo.com/pipes/pipe.run?_id=249549b5f3ea9af37a077bb103af6614&_render=rss</rss>
</li>
</ul>
</div></div></div></div></div></div></div></div></div>
 
 
.

=[[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.
 
 

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

= [[Image:Fileview-preview.png]] Maemo Qt in Actions =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Qt for Maemo Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Old qt4.garage.maemo.org forum]
* IRC
** Official Qt for Maemo IRC Channel
** 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]

Talk:Documentation/Maemo 5 Developer Guide/Using Generic Platform Components/Using Address Book API

2010-01-12T09:15:49Z

192.100.124.219: New page: This page seems ok, but info about even the existance of OssoABookSelfContact to get your own contact from abook is missing. It is ofcourse in the apidoc, but a example would be nice as we...

This page seems ok, but info about even the existance of OssoABookSelfContact to get your own contact from abook is missing. It is ofcourse in the apidoc, but a example would be nice as well.

Qt-Maemo

2010-01-11T12:15:08Z

192.100.124.219: /* Image:Kblogger.png‎ News */

__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">
22 Dec 09 - [http://wiki.maemo.org/MADDE/Qt_Example Qt example] for [http://wiki.maemo.org/MADDE MADDE ] ([http://talk.maemo.org/showthread.php?t=38075 talk thread]) 

17 Dec 09 - Qt declarative hits Maemo extras-devel repository [http://labs.trolltech.com/blogs/2009/12/17/qt-declarative-for-maemo-5/ more info here] 

11 Dec 09 - 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>
<li>
News from Qt blog... 
<rss title="off" desc="off" number="5" time="3600" text>http://labs.trolltech.com/blogs/feed/rss/</rss>
</li>
<li>
Latest Maemo Qt 4.6 commits 
<rss title="off" desc="off" number="5" time="3600" text>http://pipes.yahoo.com/pipes/pipe.run?_id=249549b5f3ea9af37a077bb103af6614&_render=rss</rss>
</li>
</ul>
</div></div></div></div></div></div></div></div></div>
 
 
.

=[[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.
 
 

=[[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
 
 

= [[Image:Fileview-preview.png]] Maemo Qt in Actions =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Qt for Maemo Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Old qt4.garage.maemo.org forum]
* IRC
** Official Qt for Maemo IRC Channel
** 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]

Qt-Maemo

2009-12-18T13:15:48Z

192.100.124.219: /* 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>
11 Dec 09 - 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>
 
 
.

=[[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.
 
 

=[[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
 
 

= [[Image:Fileview-preview.png]] Maemo Qt in Actions =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Qt for Maemo Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Old qt4.garage.maemo.org forum]
* IRC
** Official Qt for Maemo IRC Channel
** 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]

Qt-Maemo

2009-12-18T12:55:31Z

192.100.124.219: /* Image:Preferences-desktop-user.png Get Help */

__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>
11 Dec 09 - 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>
 
 
.

=[[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.
 
 

=[[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
 
 

= [[Image:Fileview-preview.png]] Maemo Qt in Actions =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Qt for Maemo Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Old qt4.garage.maemo.org forum]
* IRC
** Official Qt for Maemo IRC Channel
** 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]

Qt-Maemo

2009-12-18T12:54:03Z

192.100.124.219: /* Image:Preferences-desktop-user.png Get Help */

__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>
11 Dec 09 - 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>
 
 
.

=[[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.
 
 

=[[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
 
 

= [[Image:Fileview-preview.png]] Maemo Qt in Actions =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[Image:Preferences-desktop-user.png]] Get Help=
* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Click here to enter Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Click here to enter Old garage.maemo.org Forum]
* 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]

Qt-Maemo

2009-12-18T12:53:05Z

192.100.124.219: /* Image:Preferences-desktop-user.png Contacting us */

__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>
11 Dec 09 - 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>
 
 
.

=[[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.
 
 

=[[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
 
 

= [[Image:Fileview-preview.png]] Maemo Qt in Actions =
* Diablo Maemo Qt
ADD_HERE_SOME_PICS
* Fremantle Maemo Qt
ADD HERE SOME PICS
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[Image:Preferences-desktop-user.png]] Get Help=
* 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]

* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Click here to enter Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Click here to enter Old garage.maemo.org Forum]

Qt-Maemo

2009-12-17T13:39:13Z

192.100.124.219: /* Maemo Qt in Actions */

__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>
11 Dec 09 - 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>
 
 
.

=[[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.
 
 

=[[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
 
 

= Maemo Qt in Actions =
* Diablo Maemo Qt
ADD_HERE_SOME_THUMBS
* Fremantle Maemo Qt
ADD HERE SOME THUMBS
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[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]

* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Click here to enter Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Click here to enter Old garage.maemo.org Forum]

Qt-Maemo

2009-12-17T13:38:53Z

192.100.124.219: /* Image:Rocket.png Maemo Qt main features */

__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>
11 Dec 09 - 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>
 
 
.

=[[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.
 
 

=[[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
 
 

= Maemo Qt in Actions =
* Diablo Maemo Qt
ADD_HERE_SOME_THUMBS
* Fremantle Maemo Qt
ADD HERE SOME THUMBS

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[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]

* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Click here to enter Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Click here to enter Old garage.maemo.org Forum]

Qt-Maemo

2009-12-17T13:35:49Z

192.100.124.219: /* Image:Preferences-desktop-user.png Contacting us */

__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>
11 Dec 09 - 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>
 
 
.

=[[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.
 
 

=[[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
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[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]

* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Click here to enter Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Click here to enter Old garage.maemo.org Forum]

Qt-Maemo

2009-12-17T13:35:26Z

192.100.124.219: /* Image:Preferences-desktop-user.png Contacting us */

__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>
11 Dec 09 - 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>
 
 
.

=[[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.
 
 

=[[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
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[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]

* Forums
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Click here to enter the Forum Nokia Discussion board]
** [https://garage.maemo.org/forum/?group_id=424 Click here to enter Old garage.maemo.org Forum]

Qt-Maemo

2009-12-17T13:27:42Z

192.100.124.219: /* Image:Preferences-desktop-user.png Contacting us */

__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>
11 Dec 09 - 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>
 
 
.

=[[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.
 
 

=[[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
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[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]

* Forums
** [https://garage.maemo.org/forum/?group_id=424 Click here to enter the Forum]
** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Click here to enter the Forum Nokia]

Qt-Maemo

2009-12-17T13:27:10Z

192.100.124.219: /* Image:Preferences-desktop-user.png Contacting us */

__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>
11 Dec 09 - 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>
 
 
.

=[[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.
 
 

=[[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
 
 

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

=[[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: 
deb http://repository.maemo.org/extras/ diablo free non-free

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

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

Install Qt binaries and development packages into the SDK:
fakeroot apt-get install libqt4-dev
</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: sudo gainroot && apt-get install libqt4-gui

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

'''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.

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

- Run apt-get update

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

- Install dev packages into the SDK with: fakeroot apt-get install libqt4-maemo5-dev

Note:

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

=[[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;
 
 

=[[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.
 
 

=[[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
 
 

=[[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]

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

** [http://discussion.forum.nokia.com/forum/forumdisplay.php?f=220 Click here to enter the Forum Nokia]

Maemo-Barcelona Long Weekend/UX meets Code

2009-12-02T08:05:35Z

192.100.124.219: /* Participants */

This wiki page is complemented by [http://talk.maemo.org/showthread.php?p=393329 this discussion thread]

About 50 community developers and user experience professionals work together during 3 days.

=== 3 goals ===

* Improve the usability and visual appeal of great Maemo apps.
* Improve the UX documentation for Maemo developers.
* Get a critical mass of people interested in pushing forward UX meets Code activities online and face to face.

=== Way of working ===

All the activity happens in a big room (official capacity for 70 people).

The group activity on a project can happen in one side and you can be doing your own thing on the other side if you prefer. Free flow!

You should be able to find some time during the day to get some opinions and help from one of the experts about specific details of your project.

Every day has a similar flexible structure:
* 9:00 - Starting with a briefing about the topic: presentation + Q&A.
* 11:00 - About 2h discussion and collaboration on a real project.
* 13:00 - Lunch
* 14:00 - 2nd real project.
* 16:00 - Everybody: hard work. Other projects feel free to share your plans and problems
* 18:00 - Recap
* 18:30-ish - Enjoy the city!

===Projects===

6 projects have been selected to get get special attention during the Long Weekend. The group will do its best to have a Before and After for them. Participants in the hackfest can join the discussion/work of a specific project or can you their time to work on their own projects.

{|width=100%
!width=10%|
!width=30% align=center style="background-color:#efe;"|Friday concepting
!width=30% align=center style="background-color:#fee;"|Saturday interaction
!width=30% align=center style="background-color:#eef;"|Sunday graphics
|-
|align=right style="padding:10px;"|11:00-12:00
|style="padding:10px;background-color:#efe;"|[http://www.youtube.com/watch?v=9rEZxWjVvGo liqbase Calendar]
|style="padding:10px;background-color:#fee;"|[[Maemo-Barcelona_Long_Weekend/UX_meets_Code/MaemoMapper|Mapper]]
|style="padding:10px;background-color:#eef;"|[http://maemo.org/downloads/product/Maemo5/gpodder/ gPodder]
|-
|align=right style="padding:10px;"|14:00-16:00
|style="padding:10px;background-color:#efe;"|Video editor
|style="padding:10px;background-color:#fee;"|[http://maemo.org/downloads/product/Maemo5/xournal/ Xournal]
|style="padding:10px;background-color:#eef;"|MaStory
|}

List here other projects with developers participants in the hackfest. Please provide links to the project and your thought on what would you like to improve and what do you plan to achieve during the whole weekend. Add your names!

* [http://maemo.org/downloads/product/Maemo5/fmradio/ FM Radio] - Martin Grimme - general UI overhaul for a better user experience
* [http://maemo.org/downloads/product/Maemo5/conboy/ Conboy] - Cornelius Hald - Fixing settings UI / Polishing synchronization work flow and dialogs / Making control file translatable / Getting ideas for next version
* [http://maemo.org/downloads/product/OS2008/diskusage/ DiskUsage], [http://maemo.org/downloads/product/OS2008/kandis/ Kandis], [http://maemo.org/downloads/product/OS2008/PackageView/ PackageView], [http://maemo.org/downloads/product/OS2008/weightjinni/ WeightJinni], [http://maemo.org/downloads/product/OS2008/wifiinfo/ WifiInfo], [http://maemo.org/downloads/product/OS2008/mathjinni/ MathJinni], [http://maemo.org/downloads/product/OS2008/dicejinni/ DiceJinni], [http://maemo.org/downloads/product/OS2008/findmine/ FindMine], [http://maemo.org/downloads/product/OS2008/pushit/ PushIt], [http://maemo.org/downloads/product/OS2008/givemefive/ GiveMeFive], [http://maemo.org/downloads/product/OS2008/gpsjinni/ GPSJinni] - Tim Teulings - Usage of tables with table headers and multiple columns vs. one table column with complex layout (general), general usability improvements (MathJinni, WeightJinni, DiceJinni, Kandis, GPSJinni) replacement suggestions for tree view (MathJinni), thumbable gaming interaction (FindMine, PushIt, GiveMeFive) and technical support for Gtk/hildon theming alignment and Qt know how (general) - all applications also available in maemo5 extras-devel!

=== Participants ===
Please add your names and a link to your maemo.org profile. Please edit your profile adding all the relevant info about you and links to your website, blog, etc.

* [http://maemo.org/profile/view/martin/ Martin Schuele] - Principal UI designer for N900
* [http://maemo.org/profile/view/msoini/ Mox Soini] - Interaction Designer, Concepting, Maemo-as-platform
* Steffen Halme - Graphic Designer specializing in icons
* [http://personal.inet.fi/koti/mgimpl/ Martin Gimpl] - Graphic Designer, Concepting, Transitions, Graphics
* [http://maemo.org/profile/view/asimula/ Adele Simula] - UX Graphic Designer, Concepting, Layout Design, Graphics
* Sanna Nordling - Interaction designer, Concepting, Application UX design
* [http://maemo.org/profile/view/jmaaniit/ Jussi Maaniitty] - UX Management, Concepting
* Juha Vartiainen - Interaction Design, Concepting, Application UI design
* Jaakko Viitanen - Interaction Design, Concepting, Application UI design
* [http://blogs.forum.nokia.com/blog/arabella-davids-forum-nokia-blog Arabella David], Design & User Experience Program Manager @ Forum Nokia
* [http://maemo.org/profile/view/sannah/ Sanna Häivalainen] - UX Specialist @ Forum Nokia
* [http://maemo.org/profile/view/tigert/ Tuomas Kuosmanen] - Senior Designer @ Nokia
* [http://maemo.org/profile/view/patifa/ Patricia Montenegro] - Lead User Experience Designer @ INdT
* [http://maemo.org/profile/view/allsomm/ Alysson Santos] - Senior Designer @ INdT - interested in the video editor
* Annu-Maaria Nivala
* Jan Krebber
* Kirsi Rönkkö
* Ulla Niemelä

===Help with specific technologies===

====Developers willing to help====
Please list technologies you are using and working with here. This makes it easier for other people to quickly find a person to ask specific technical questions.

* Thomas Perl: PyMaemo, GTK+, Hildon, PyGTK, Python
* [http://maemo.org/profile/view/andy80/ Andrea Grandi]: Pymaemo, Python, UI design concepts
* [http://maemo.org/profile/view/anidel/ Aniello Del Sorbo]: GTK, C, Debian packaging. Not an expert.
* Jesus Sanchez-Palencia: Qt 4.6, libqt4-maemo5 (Qt 4.6 for Maemo5)
* Zaheer Abbas Merali: GStreamer, Python, PyGTK
* [http://maemo.org/profile/view/vdvsx/ Valério Valério]: Python, C/C++, EFL, PyGTK, Qt (not an expert).
* [http://maemo.org/profile/view/mardy/ Alberto Mardegan]: GTK, Hildon, C/C++, Qt, Clutter (just basics).
* [http://maemo.org/profile/view/marcoil/ Marc Ordinas i Llopis]: C, Gtk+, Hildon, Hildon-desktop.
* [http://maemo.org/profile/view/pycage/ Martin Grimme]: PyMaemo, GDK, UPnP with Python, V4L2 in Python, controlling N800 & N900 FM receivers, D-Bus services with GObject (C)
* [http://maemo.org/profile/view/mikhas/ Michael Hasselmann]: Qt 4.6 for Maemo5 (novice), autotroll
* [http://maemo.org/profile/view/bilboed/ Edward Hervey]: Video Editing, GStreamer, PiTiVi, GStreamer Editing Services, GNonLin
* [http://maemo.org/profile/view/conny/ Cornelius Hald]: C, Gtk+, Hildon, Eclipse, transifex.net, hildon-extras
* ''<Your name here>: <Your technologies here>''

====How to get help====

# Look up developers who work with the technology you need help with in the list above
# Approach the developers and ask them for help/advice :)
# In the neighbor room there will be [[Maemo-Barcelona_Long_Weekend/Formaci%C3%B3n|a developer
training track]]. Feel free jumping there to ask questions, too!

=== Interested? ===

If you want to be invited please provide in [http://talk.maemo.org/showthread.php?t=33719 this thread]:

* Your [http://maemo.org/profile/list/ maemo.org profile] making sure that there one can find info about or links to your current projects and your interests in Code or UX.
* If you are more into Code, a link to the app hosted in maemo.org, either under [http://maemo.org/packages/ Fremantle packages] or [http://maemo.org/downloads/OS2008/ OS2008 Downloads].
* If you are more into UX, a link to wherever your work can be seen.

Forward this to your colleagues working on great stuff!

For budgeting and also practical purposes we will keep the number of participants around 50 people even if we get more requests. The criteria will be defined more or less by fast response, travel costs, community involvement and of course Maemo excellence in Code or UX.

Using Fremantle widgets

2009-11-12T09:28:36Z

192.100.124.219: /* Portrait Mode */

This document should help developers to port the user interface from [[Diablo]] to [[Fremantle]]. The document mirrors what was discussed on the mailing lists, forum and bug reports. It is based completely on the Fremantle Beta SDK which is the most recent SDK at the moment.
in addition, please check the growing [http://wiki.maemo.org/index.php?title=Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines Human Interface Guidelines] and the official hildon documentation:
* [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]

Please feel totally free to add/update/change/remix this document. Many aspects are currently not discussed here but will hopefully be added by you!

Note: The casts of all code examples haven been removed for better readability.

= Toggle Buttons Vs. Radio Buttons =
The use of radio buttons in Fremantle is discouraged because they don't fit the visual style quite well. Instead you should use toggle buttons.

So if you need the behavior of radio buttons (which is that only one can be selected at a time) simply create them as usually and then call <code>gtk_toggle_button_set_mode()</code>. This will create a button that acts like a radio button, but is displayed as a toggle button.

Example:
<pre>
GtkWidget *b1 = gtk_radio_button_new_with_label("One");
GtkWidget *b2 = gtk_radio_button_new_with_label_from_widget(b1, "Two");
gtk_toggle_button_set_mode(b1, FALSE);
gtk_toggle_button_set_mode(b2, FALSE);
</pre>

[[Image:Fle_tut_radio_buttons.jpg|frame|Above you see how radio buttons are displayed in Fremantle. There is a bug in this screenshot, normally of course only one of the four options would be selected.]]

[[image:Fle_tut_toggle_buttons.jpg|frame|Here you can see four radio buttons which are displayed as toggle buttons using the <code>gtk_toggle_button_set_mode()</code> function mentioned above.]]

= Widget Sizes =
For some widgets there is now an enum which provides three different values: <code>HILDON_SIZE_FINGER_HEIGHT</code>, <code>HILDON_SIZE_THUMB_HEIGHT</code> and <code>HILDON_SIZE_AUTO_HEIGHT</code>. You can use them, for example, like that:
<pre>
GtkWidget but* = hildon_gtk_button_new(HILDON_SIZE_FINGER_HEIGHT);
</pre>
You should always use the finger or the thumb size, don't use HILDON_SIZE_AUTO_HEIGHT as the outcome is not totally clear (see below for screenshots).

If you have a button where you cannot provide a size with the constructor, for example, a stock button, then you can use <code>hildon_gtk_widget_set_theme_size()</code> to set the code afterwards. Like in this small example:
<pre>
GtkWidget *but = gtk_button_new_from_stock(GTK_STOCK_COPY);
hildon_gtk_widget_set_theme_size(but, HILDON_SIZE_THUMB_HEIGHT);
</pre>

Now to get a feeling for the different sizes here are some screenshots that show a HildonEntry together with a GtkButton using different sizes.

[[Image:Fle_tut_button_auto_finger.jpg|frame|A HildonEntry with HILDON_SIZE_AUTO_HEIGHT and a GtkButton with HILDON_SIZE_FINGER_HEIGHT. Looks inconsistent.]]

[[Image:Fle_tut_button_finger_finger.jpg|frame|Both widget with HILDON_SIZE_FINGER_HEIGHT. Looks more consistent now.]]

[[Image:Fle_tut_button_finger_thumb.jpg|frame|For comparison reasons the HildonEntry with HILDON_SIZE_FINGER_HEIGHT and the GtkButton with HILDON_SIZE_THUMB_HEIGHT.]]

= Window Menu =
In Fremantle it is not encouraged to use <code>GtkMenu</code> as window menu anymore. Instead you should use the <code>HildonAppMenu</code>. This new menu is really different from the old one so it´s worth taking a closer look. Here are the main features of the HildonAppMenu.
* It has big / finger friendly menu items.
* It holds a maximum of ten menu items.
* It does not support sub menues.
* The first row can be used for Filters. (Filters are explained in more details below.)
* In landscape mode the menu items are displayed in two rows.
* In portrait mode the menu items are automatically displayed in one row.
* There are no separators, so you cannot group your menu items.
* The menu items are GtkButtons and not GtkMenuItems.

The HildonAppMenu is meant to be displayed when the user clicks the title bar of the window, but it is possible to have several other HildonAppMenus in your application and activate them for example on button press.

As you can see the HildonAppMenu differs quite a lot from the old GtkMenu. The main difference is surely that you cannot have more then 10 menu items
inside the new menu. The Hildon HIG gives an overview on how to deal with that.

[[Image:Fle_tut_app_menu_with_filters.jpg‎|frame|A HildonAppMenu with two filters at the top and four buttons]]

== Using HildonAppMenu with GtkActions ==
As said earlier, the menu items are not GtkMenuItems anymore but instead they are normal GtkButtons. So you´re using GtkActions in your code, you´ll probably miss a replacement for <code>gtk_action_create_menu_item()</code>. There is no direct replacement, instead you just have to use standard gtk functions to connect the button as a proxy to the action. Here is an example:
<pre>
GtkButton *menu_item = gtk_button_new();
gtk_action_connect_proxy(action, menu_item);
</pre>
This is also possible with <code>GtkToggleAction</code> and <code>GtkRadioAction</code>. But remember that your GtkRadioButtons should look like GtkToggleButtons as mentioned above. So a complete example for a HildonAppMenu that should display three GtkRadioActions would look like this:

<pre>
GSList *group = NULL;
GtkAction *a1, *a2, *a3;
GtkWidget *b1, *b2, *b3;
GtkWidget *menu;

/* Create the actions */
a1 = gtk_radio_action_new("small", "Small", NULL, NULL, 0);
a2 = gtk_radio_action_new("normal", "Normal", NULL, NULL, 1);
a3 = gtk_radio_action_new("large", "Large", NULL, NULL, 2);

/* Build the radio action group */
gtk_radio_action_set_group(a1, group);
group = gtk_radio_action_get_group(a1);

gtk_radio_action_set_group(a2, group);
group = gtk_radio_action_get_group(a2);

gtk_radio_action_set_group(a3, group);
group = gtk_radio_action_get_group(a3);

/* Create the toggle buttons */
b1 = gtk_toggle_button_new();
b2 = gtk_toggle_button_new();
b3 = gtk_toggle_button_new();

/* Connect the buttons and the actions */
gtk_action_connect_proxy(a1, b1);
gtk_action_connect_proxy(a2, b2);
gtk_action_connect_proxy(a3, b3);

/* Create the menu */
menu = hildon_app_menu_new();

/* Add the buttons to the menu */
hildon_app_menu_append(menu, b1);
hildon_app_menu_append(menu, b2);
hildon_app_menu_append(menu, b3);
</pre>

= Finger Friendly GtkTreeView =
To get a finger friendly <code>GtkTreeView</code> it´s not enough to call <code>hildon_gtk_tree_view_new()</code> instead of <code>gtk_tree_view_new()</code> but you also have to put the tree view inside a <code>HildonPannableArea</code> to get finger friendly sizes. If you have your tree view inside a <code>GtkScrolledWindow</code> it will be displayed with stylus-style (like in Diablo).

Also if you´re displaying icons in your tree view you probably should use the 40x40 pixel version for Fremantle if you used the 26x26 pixel version in Diablo.

== Normal Vs. Edit Mode ==
There are now two different modes for the tree view. Those modes affect how the rows in a tree view react to finger taps.

You should use <code>HILDON_UI_MODE_NORMAL</code> if the user should only be able to activate one row of the text view. If the user taps a row in the tree view the <code>row-activated</code> is emitted. In standard Gtk+ this happens only if the user double clicks the row - a single click selects the row which is not possible with <code>HILDON_UI_MODE_NORMAL</code>.

If the user should be able to select or edit rows then you should use <code>HILDON_UI_MODE_EDIT</code>.

== Using Filters For Sorting ==
Most of you probably are using the tree view with a header row that displays column labels. Often this header row can also be used to sort the columns ascending or descending. If you're designing a finger friendly UI you will usually have a very limited number of visible columns - probably only one or two. In this case the column content is often self explanatory and the header row is only there for sorting. If that's the case for your UI, you might want to remove the header column completely and replace it with so called filters on the HildonAppMenu.

According to the HIG filters are meant to change how data is presented, but it should not affect the amount of data that is displayed. Sorting a tree view would be a possible use case. To do this, just have a look at the example:
<pre>
/* Remove the header row */
gtk_tree_view_set_headers_visible(view, FALSE);

/* Create two radio buttons for sorting */
GtkWidget *b1, *b2;
b1 = gtk_radio_button_new_with_label(NULL, "Sort By Title");
b2 = gtk_radio_button_new_with_label_from_widget(b1, "Sort By Date");

/* Draw them as toggle buttons not as radio buttons */
gtk_toggle_button_set_mode(b1, FALSE);
gtk_toggle_button_set_mode(b2, FALSE);

/* Add the buttons as filters to the menu */
hildon_app_menu_add_filter(menu, b1);
hildon_app_menu_add_filter(menu, b2);
</pre>

That is all for showing them on the window menu. Now only a callback is needed which gets activated whenever the user selects a filter. An example implementation might look like that:
<pre>
void on_sort_filter_clicked(GtkToggleButton *button, GtkTreeSortable *sortable)
{
if (gtk_toggle_button_get_active(button)) {
gtk_tree_sortable_set_sort_column_id(sortable, TITLE_COLUMN, GTK_SORT_ASCENDING);
}
}
</pre>

You can add as many filters as you like, but they will be displayed all in one row and there is no possibility to add another filter row. This means you have to select carefully what to put there and also have a look at the length of the strings.
If you, for example have two rows, one with a title and one with a date you could offer the user:
* Sort ascending by date
* Sort descending by date
* Sort ascending by title
* Sort descending by title
Those four strings will not fit into one row. Therefore you have to make a selection and include only the cases which will (hopefully) be most relevant to the user. In this case you should offer:
* Sort by title (which sorts by title ascending - A before B)
* Sort by date (which sorts by date descending - newest on top)
In the most recent version (not yet in Beta 2) the filter group has a fixed size which does not depend on the number of filters or the orientation of the device. So if your menu looks good in landscape mode it will look good in portrait mode.

[[Image:Fle_tut_tree_view.jpg‎|frame|A tree view without the title row. Sorting is now done with filters]]

[[Image:Fle_tut_tree_view_filter.jpg‎|frame|When clicking the title bar two filters are shown which let the user sort the tree view]]

[[Image:Fle_tut_filter_long_strings.jpg|frame|Long strings get truncated]]

= Context Menus =
To display finger friendly context menues there is a hildon helper function called <code>hildon_gtk_menu_new()</code>. Just call this instead of <code>gtk_menu_new()</code> and you´re done.
Example:
<pre>
GtkWidget *menu = hildon_gtk_menu_new();

GtkWidget *item1 = gtk_menu_item_new_with_label("Bla");
GtkWidget *item2 = gtk_menu_item_new_with_label("Blablabla");

gtk_menu_shell_append(GTK_MENU_SHELL(menu), item1);
gtk_menu_shell_append(GTK_MENU_SHELL(menu), item2);

gtk_widget_show_all(menu);
gtk_menu_popup(GTK_MENU(menu), NULL, NULL, NULL, NULL, 0,
gtk_get_current_event_time());
</pre>
''Note that in the Beta SDK there is a bug. If you´re using <code>GtkImageMenuItems</code> instead of <code>GtkMenuItems</code> the menu will have stylus-style. This bug is already fixed and a work around is available here: https://bugs.maemo.org/show_bug.cgi?id=4654 .''

[[Image:Fle_tut_context_menu.jpg‎|frame|Finger friendly context menu which is showing four stock items]]

= Panning =
Almost all of you will know the problems with scrollbars in Diablo. You can have small scrollbars which are not finger friendly or you can have large scrollbars which are using a lot of screen space and look ugly.

In Fremantle both kinds of scrollbars are still available, but there is also a third option. <code>HildonPannableArea</code> features kinetic panning using fingers. There is no scrollbar anymore, only a very small scroll indicator that indicates which part of the document you´re seeing right now.
<code>HildonPannableArea</code> can be used as a replacement for <code>GtkScrolledWindow</code> but there are things you have to keep in mind when doing so.

== GtkTextView Inside HildonPannableArea ==
Panning does not work with a <code>GtkTextView</code>. Instead you can use a <HildonTextView> which is a drop in replacement. The advantage is, that then panning is possible. The disadvantage is that selecting text is not possible anymore. The discussion about this is here: https://bugs.maemo.org/show_bug.cgi?id=4619

== GtkHtml Inside HildonPannableArea ==
When using <code>GtkHtml</code> inside a <code>HildonPannableArea</code> the panning is not smooth. The problem seems to be that GtkHtml provides some build in support for panning and that it conflicts with the panning offered by Hildon. See this bug report here: https://bugs.maemo.org/show_bug.cgi?id=4631

= Portrait Mode =
If your application should work in portrait mode you probably have to change the UI quite a bit. There are a couple of problems you'll might have:
* The toolbar is not wide enough to hold all items anymore.
* The columns of your tree view get too small.
* You cannot enter text because there´s no onscreen keyboard. (Actually the FKB works perfectly, but it will switch to landscape and then back to portrait when closed.)
* Dialogs are not shown correctly (see https://bugs.maemo.org/show_bug.cgi?id=4618 ).
* Probably more...

This means you have to listen to changes in the orientation and hide/show/change widgets to make the UI functional in portrait mode.

[[Image:Fle_tut_app_menu_portrait.jpg|frame|The HildonAppMenu with filters in portrait mode. The final version will cover the complete screen width, so there is a bit more space for the filters.]]

== Listening To Screen Orientation Changes ==
Basically here you´re not listening to changes in the devices orientation, but you check the height and width of the screen. So if width > height you are in landscape mode and if height > width you´re in portrait mode. This is supposed to work no matter why height and width changed. So it does not depend on hardware support like acceleratormeters it could also just be a software setting that rotates the screen.

<pre>
gboolean is_portrait()
{
GdkScreen *screen = gdk_screen_get_default();
int width = gdk_screen_get_width(screen);
int height = gdk_screen_get_height(screen);
if (width > height) {
return FALSE;
} else {
return TRUE;
}
}

void on_orientation_changed(GdkScreen *screen, GtkWidget *widget)
{
if (is_portrait()) {
gtk_widget_hide(widget);
/* Hide/Show other things */
} else {
gtk_widget_show(widget);
/* Hide/Show other things */
}
}
</pre>
Then inside your UI code you should listen to the <code>size-changed</code> signal of <code>GdkScreen</code>. For example:
<pre>
g_signal_connect(screen, "size-changed", on_orientation_changed, widget);
</pre>

== Testing Screen Orientation Changes In Scratchbox ==
For testing your code you can execute the following commands outside scratchbox:
<pre>
xrandr -display :2 -o left
xrandr -display :2 -o normal
</pre>

== Automatic Screen Rotation ==
Your application is not automatically rotated when the user rotates its device. Even if the hardware supports it. There are more things to do to make that happen. Basically you have to do two things:
* During startup of your application, or better shortly before showing the first window, you should check the orientation of the device and adjust your application.
* You have to listen to all changes in the devices orientation while your application is running and adapt accordingly.

Whether or not your application is rotated depends on a couple of things:
* There are two X window properties which you can set on your windows.
* Those tell the system what to do. The type of the value of the properties is <tt>XA_CARDINAL</tt> where 0 means "off", and 1 stands for "on". Other values may get other meaning in the future.
** <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> tells the system that your application can be rotated, so it won't prevent any other application from rotating.
** <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> tells the system that your application wants to be rotated.
* Rotation only happens when all visible windows are ok with being rotated.

That means that to get a rotated desktop all visible windows must have the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag set to 1 and at least one of them must have the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag set to true. The flags are inherited through the transiency chain, so you needn't set the SUPPORT flag on your transient dialogs for example, nor on all stackable windows.

It's important that you set the flags correctly on all windows that you open. If you or another application opens a window with the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag not set, the whole UI is rotated to landscape mode.

So here are the steps you have to do to make correct use of the portrait mode:
* On all windows that support portrait mode, set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag.
* During startup check the hardware orientation. If the hardware orientation is portrait mode, then set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag on at least one visible window.
* While running your application, listen to changes in the orientation of the device. If it is rotated to landscape mode set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag. If it's rotated to portrait mode set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag.
It is not necessary to set 'request' together with 'support' as 'request' implies 'support', provided that 'support' is unset (as opposed to set to 0).

=== Finding Out The Current Hardware Orientation ===
In order to find out whether or not the device currently is in portrait you need to ask the MCE (Mode Control Entity) via DBus. The parameters of the call are the following and can be found as constants in 'mce/dbus-names.h'.

<pre>
Service: "com.nokia.mce"
Path: "/com/nokia/mce/request"
Iterface: "com.nokia.mce.request"
Member: "get_device_orientation"
</pre>

This method returns several values:
* gchar * portrait/landscape orientation (see mce/mode-names.h for valid portrait/landscape states)
* gchar * on/off stand (see mce/mode-names.h for valid stand states)
* gchar * face up/face down (see mce/mode-names.h for valid facing states)
* dbus_int32_t x axis (unit mG)
* dbus_int32_t y axis (unit mG)
* dbus_int32_t z axis (unit mG)

In our case we are only interested in the first return value which will be 'portrait' or 'landscape'. Because we only need to know the first value here we can use the <tt>osso_rpc_run_system()</tt> function for making this call to DBus. It's a convenience function provided by libosso for making DBus calls. The advantage is that our code gets shorter, the disadvantage is that it only return the first return value - which in our case is ok. So here is the code using libosso.

<pre>
#include <mce/dbus-names.h>
#include <mce-dev/mode-names.h

gboolean
device_is_portrait_mode(osso_context_t* ctx)
{
osso_rpc_t ret;
gboolean result = FALSE;

if (osso_rpc_run_system(ctx, MCE_SERVICE, MCE_REQUEST_PATH,
MCE_REQUEST_IF, MCE_DEVICE_ORIENTATION_GET, &ret, DBUS_TYPE_INVALID) == OSSO_OK) {
g_printerr("INFO: DBus said orientation is: %s\n", ret.value.s);

if (strcmp(ret.value.s, MCE_ORIENTATION_PORTRAIT) == 0) {
result = TRUE;
}

osso_rpc_free_val(&ret);

} else {
g_printerr("ERROR: Call do DBus failed\n");
}

return result;
}
</pre>

=== Listening To Hardware Orientation Changes ===

So now you know how to ask the device for its orientation. Now let's see how to connect a signal handler to listen to changes in the orientation.

First here is again the signature:
<pre>
Service: "com.nokia.mce"
Path: "/com/nokia/mce/signal"
Iterface: "com.nokia.mce.signal"
Member: "sig_device_orientation_ind"
</pre>

The signal transports three values:
* gchar * portrait/landscape orientation (see mce/mode-names.h for valid portrait/landscape states)
* gchar * on/off stand (see mce/mode-names.h for valid stand states)
* gchar * face up/face down (see mce/mode-names.h for valid facing states)

Again we are only interested in the first value which is 'portrait' or 'landscape'. Unfortunately there is no libosso convenience function for listening to DBus signals, so we have to use the raw DBus API.

<pre>
static DBusHandlerResult
dbus_handle_mce_message(DBusConnection *con, DBusMessage *msg, gpointer data)
{
DBusMessageIter iter;
const gchar *mode = NULL;

if (dbus_message_is_signal(msg, MCE_SIGNAL_IF, MCE_DEVICE_ORIENTATION_SIG)) {
if (dbus_message_iter_init(msg, &iter)) {
dbus_message_iter_get_basic(&iter, &mode);
g_printerr("INFO: New orientation is now: %s\n", mode);
}
}
return DBUS_HANDLER_RESULT_NOT_YET_HANDLED;
}
</pre>

Now we need to register this signal handler.

<pre>
#define MCE_MATCH_RULE "type='signal',interface='" MCE_SIGNAL_IF "',member='" MCE_DEVICE_ORIENTATION_SIG "'"

/* Get the system DBus connection */
DBusConnection *con = osso_get_sys_dbus_connection(osso_context);

/* Add the callback, which should be called, once the device is rotated */
dbus_bus_add_match(con, MCE_MATCH_RULE, NULL);
dbus_connection_add_filter(con, dbus_handle_mce_message, NULL, NULL);
</pre>

=== Listening To Hardware Orientation Changes (Python example) ===

This short snippet should get you started (you only need the gobject.MainLoop if you are writing a console application). "handler" will be called every time the orientation changes, and the first parameter is the important one (compare it to "landscape" and "portrait").

<pre>import dbus
import dbus.glib

# Again, this is only needed for console apps
import gobject
mainloop = gobject.MainLoop()

# Define some constants
MCE_SIGNAL_NAME = 'sig_device_orientation_ind'
MCE_SIGNAL_IFACE = 'com.nokia.mce.signal'
MCE_SIGNAL_PATH = '/com/nokia/mce/signal'

# Get the system bus
system_bus = dbus.Bus.get_system()

# Define a callback that gets called for orientation changes
def handler(orientation, stand, face, x, y, z):
print orientation

# Connect the "handler" to the orientation changed signal of mce
system_bus.add_signal_receiver(handler, signal_name=MCE_SIGNAL_NAME, \
dbus_interface=MCE_SIGNAL_IFACE, path=MCE_SIGNAL_PATH)

# Start the main loop - only needed for console apps
mainloop.run()</pre>

Do you want it even more comfortable? See [http://talk.maemo.org/showthread.php?p=330992 this forum post] for a link to an easy-to-use drop-in module that will take care of auto-rotation all your application windows.

== Testing Hardware Orientation In Scratchbox ==
Testing whether or not your DBus signal handler for device orientation change works is easy. Just run the following commands inside scratchbox while your application is running.

Device was rotated into portrait mode:
<pre>
run-standalone.sh dbus-send --system --type=signal /com/nokia/mce/signal com.nokia.mce.signal.sig_device_orientation_ind string:'portrait'
</pre>

Device was rotated into landscape mode:
<pre>
run-standalone.sh dbus-send --system --type=signal /com/nokia/mce/signal com.nokia.mce.signal.sig_device_orientation_ind string:'landscape'
</pre>

For testing the call to the MCE you first have to install the MCE because it's not part of the default SDK installation. Simply do:
<pre>fakeroot apt-get install mce</pre>
Now start it using the debug mode. It won't start without the '--debug-mode' flag. You'll get lots of debug output on the terminal, just ignore it:
<pre>mce --debug-mode</pre>

Now the DBus call to the MCE should return 'landscape'. It probably will always return 'landscape' when run inside the SDK as it is not possible to really rotated the "device" there.

= References =
In no particular order

* http://maemo.org/api_refs/5.0/beta/tutorial/html
* http://maemo.org/api_refs/5.0/beta/hig/html

* http://lists.maemo.org/pipermail//maemo-developers/2009-May/019368.html
* http://lists.maemo.org/pipermail//maemo-developers/2009-May/019144.html
* http://lists.maemo.org/pipermail//maemo-developers/2009-June/019426.html
* http://lists.maemo.org/pipermail//maemo-developers/2009-June/019579.html
* http://lists.maemo.org/pipermail//maemo-developers/2009-August/020202.html

* https://bugs.maemo.org/show_bug.cgi?id=4617
* https://bugs.maemo.org/show_bug.cgi?id=4618
* https://bugs.maemo.org/show_bug.cgi?id=4619
* https://bugs.maemo.org/show_bug.cgi?id=4654
* https://bugs.maemo.org/show_bug.cgi?id=4637
* https://bugs.maemo.org/show_bug.cgi?id=4648

[[Category:Development]]
[[Category:Fremantle]]

Legacy Maemo 5 Documentation/Graphical UI Tutorial/Data selection

2009-11-11T12:47:00Z

192.100.124.219: /* Text Columns Example */

= Data selection =
Hildon provides a set of widgets for data selection specially designed for touchscreens that allows to build simple and easy-to-use interfaces.

The key widget is a selector widget that allows users to select items from one to many predefined lists. It is similar to a combo box but allows several individual pannable columns.

In addition, Hildon also provides a specialized dialog and a specialized button to be used in combination with a selector.

==Touch selector ==
HildonTouchSelector is the mentioned selector widget. This widget can display several pannable columns. Each column is represented by a GtkTreeModel and single or multiple selection is allowed.

===Text Columns Example===
Let us see the simplest possible example. A selector that shows a single text column.

'''Example 6.1. Example of a single-column selector'''

[[Image:example-single-text-column-selector.png|400px]]

#include <hildon/hildon.h>

void selection_changed (HildonTouchSelector * selector, gpointer user_data);
static GtkWidget *create_simple_selector ();

void
selection_changed (HildonTouchSelector * selector,
gpointer user_data)
{
gchar *current_selection = NULL;

current_selection = hildon_touch_selector_get_current_text (selector);
g_debug ("Current selection : %s", current_selection);
}

static GtkWidget *
create_simple_selector ()
{
GtkWidget *selector = NULL;
gint i;

/* Create a HildonTouchSelector with a single text column */
selector = hildon_touch_selector_new_text();

g_signal_connect (G_OBJECT (selector), "changed",
G_CALLBACK (selection_changed), NULL);

/* Populate selector */
for (i = 1; i <= 10 ; i++) {
gchar *label = g_strdup_printf ("Item %d", i);

/* Add item to the column */
hildon_touch_selector_append_text (HILDON_TOUCH_SELECTOR (selector),
label);

g_free (label);
}

/* Set selection mode */
hildon_touch_selector_set_column_selection_mode (HILDON_TOUCH_SELECTOR (selector),
HILDON_TOUCH_SELECTOR_SELECTION_MODE_MULTIPLE);

return selector;
}

int
main (int argc, char **argv)
{
HildonProgram *program = NULL;
GtkWidget *window = NULL;
GtkWidget *selector = NULL;
GtkWidget *picker_button = NULL;

hildon_gtk_init (&argc, &argv);

program = hildon_program_get_instance ();
g_set_application_name
("hildon-touch-selector example program");

window = hildon_stackable_window_new ();
hildon_program_add_window (program, HILDON_WINDOW (window));

/* Create touch selector */
selector = create_simple_selector ();

/* Create a picker button */
picker_button = hildon_picker_button_new (HILDON_SIZE_AUTO,
HILDON_BUTTON_ARRANGEMENT_VERTICAL);

/* Set a title to the button*/
hildon_button_set_title (HILDON_BUTTON (picker_button), "Select an item");

/* Attach touch selector to the picker button*/
hildon_picker_button_set_selector (HILDON_PICKER_BUTTON (picker_button),
HILDON_TOUCH_SELECTOR (selector));

/* Add button to main window */
gtk_container_add (GTK_CONTAINER (window), picker_button);

g_signal_connect (G_OBJECT (window), "destroy",
G_CALLBACK (gtk_main_quit), NULL);

gtk_widget_show_all (GTK_WIDGET (window));

gtk_main ();

return 0;
}

A HildonTouchSelector with a single text column is created in this program using the following convenience constructor.

<tt>GtkWidget<nowiki>*</nowiki> '''hildon_touch_selector_new_text''' (void);
</tt>

To add text to a selector created by calling the constructor above, use the function.

<tt>void '''hildon_touch_selector_append_text''' (HildonTouchSelector <nowiki>*</nowiki>selector,
'''const''' gchar <nowiki>*</nowiki>text);
</tt>

Alternatively, you can use <code>hildon_touch_selector_prepend_text()</code> or <code>hildon_touch_selector_insert_text()</code> to add text to the selector in different positions.

You can set the desired selection with the function. In the example, the mode was set to allow multiple selection.

<tt>void hildon_touch_selector_set_column_selection_mode
(HildonTouchSelector <nowiki>*</nowiki>selector,
HildonTouchSelectorSelectionMode mode);
</tt>

This example shows a very common use case of this widget. Next section shows how to build a more complex selector with several columns of different types.

Also a simple function was set as a handler for the "changed" signal which is emitted each time the selected items change.

The callback retrieves a text representation of the currently selected items in the selector by calling <code>hildon_touch_selector_get_current_text()</code>. By default this function returns a concatenation of the items selected, separated by a comma.

To change how the text representation is generated, set your own function by calling <code>hildon_touch_selector_set_print_func()</code> and using the following signature for the function:

<tt>gchar<nowiki>*</nowiki> '''user_function''' (HildonTouchSelector <nowiki>*</nowiki>selector);
</tt>

===Custom columns===

In the previous section, a selector with a text column was created. That is probably the most common use case of touch selectors. Convenience functions to deal with text columns was used. However, you can also set other type of columns.

Because each column is basically a treeview, you can use the same display to different data and in different ways as you would do with a GtkTreeview. Thus, you can use the GtkCellRenderers available in GTK+ to display the data on each cell.

This section explains how to build a selector within a column displaying stock icons. Firstly, let us take a look on the function which used for appending new columns to a touchable selector.

<tt>HildonTouchSelectorColumn<nowiki>*</nowiki> hildon_touch_selector_append_column
(HildonTouchSelector <nowiki>*</nowiki>selector,
GtkTreeModel <nowiki>*</nowiki>model,
GtkCellRenderer <nowiki>*</nowiki>cell_renderer,
...);
</tt>

This functions adds a new column to the widget whose data is obtained from the passed model. Pass also a GtkCellRenderer and a list of pairs property/value which is set as attributes of the renderer.

This function basically adds a GtkTreeView to the widget. For more information on how GtkTreeviews work, see [http://maemo.org/api_refs/5.0/beta/gtk/ GTK+ widgets] before.
The following example shows how to set a column to display images in a selector. For clarity, only the function which creates the selector is shown.

'''Example 6.2. Example of a selector with a custom column'''

[[Image:example-single-column-selector.png|400px]]

<tt> '''static''' GtkWidget <nowiki>*</nowiki>
'''create_customized_selector'''()
{
GtkWidget <nowiki>*</nowiki>selector<nowiki>;</nowiki>
GSList <nowiki>*</nowiki>icon_list <nowiki>=</nowiki> NULL<nowiki>;</nowiki>
GtkListStore <nowiki>*</nowiki>store_icons <nowiki>=</nowiki> NULL<nowiki>;</nowiki>
GSList <nowiki>*</nowiki>item <nowiki>=</nowiki> NULL<nowiki>;</nowiki>
GtkCellRenderer <nowiki>*</nowiki>renderer <nowiki>=</nowiki> NULL<nowiki>;</nowiki>
HildonTouchSelectorColumn <nowiki>*</nowiki>column <nowiki>=</nowiki> NULL<nowiki>;</nowiki>
''/* Create a touch selector */''
selector <nowiki>=</nowiki> '''hildon_touch_selector_new'''();
''/* Stock icons will be used for the example */''
icon_list <nowiki>=</nowiki> '''gtk_stock_list_ids'''();
''/* Create model to store selector's items */''
store_icons <nowiki>=</nowiki> '''gtk_list_store_new''' (1, G_TYPE_STRING);
''/* Populate model */''
'''for''' (item <nowiki>=</nowiki> icon_list<nowiki>;</nowiki> item<nowiki>;</nowiki> item <nowiki>=</nowiki> '''g_slist_next''' (item)) {
GtkTreeIter iter<nowiki>;</nowiki>
gchar <nowiki>*</nowiki>label <nowiki>=</nowiki> item->data<nowiki>;</nowiki>
'''gtk_list_store_append''' (store_icons, &iter);
'''gtk_list_store_set''' (store_icons, &iter, 0, label, -1);
'''g_free''' (label);
}
'''g_slist_free''' (icon_list);
''/* Create and set up a pixbuf renderer to use in the selector */''
renderer <nowiki>=</nowiki> '''gtk_cell_renderer_pixbuf_new'''();
'''gtk_cell_renderer_set_fixed_size''' (renderer, -1, 100);
''/* Add the column to the selector */''
column <nowiki>=</nowiki> '''hildon_touch_selector_append_column''' ('''HILDON_TOUCH_SELECTOR''' (selector),
'''GTK_TREE_MODEL''' (store_icons),
renderer,
"stock-id", 0,
NULL);
''/* Set the selection mode */''
'''hildon_touch_selector_set_column_selection_mode''' ('''HILDON_TOUCH_SELECTOR''' (selector),
HILDON_TOUCH_SELECTOR_SELECTION_MODE_MULTIPLE);
''/* Set the property "text-column" that indicates the column''
'' * of the model to get the string from */''
'''g_object_set''' ('''G_OBJECT''' (column), "text-column", 0, NULL);
'''return''' selector<nowiki>;</nowiki>
}
</tt>

The first step in the example is to create and populate a GtkTreeModel. A GtkListStore is used in the example. In most use cases of the touchable selectors a GtkListStore fits well as selectors were designed to allow users to select from a list of items.

In this case, the model stores a list of GTK+ stock icons identifiers. The following call creates a list store with one column to store strings.

<tt>store_icons <nowiki>=</nowiki> '''gtk_list_store_new''' (1, G_TYPE_STRING);
</tt>

The following loop appends all stock identifiers in the newly created model. The identifiers were previously retrieved using

<tt>'''gtk_stock_list_ids'''().
'''for''' (item <nowiki>=</nowiki> icon_list<nowiki>;</nowiki> item<nowiki>;</nowiki> item <nowiki>=</nowiki> '''g_slist_next''' (item)) {
GtkTreeIter iter<nowiki>;</nowiki>
gchar <nowiki>*</nowiki>label <nowiki>=</nowiki> item->data<nowiki>;</nowiki>
'''gtk_list_store_append''' (store_icons, &iter);
'''gtk_list_store_set''' (store_icons, &iter, 0, label, -1);
'''g_free''' (label);
}
'''g_slist_free''' (icon_list);
</tt>

The next step is to set up the renderer which renders each row of the new column. We need a GtkCellRendererPixbuf to display the stock icons.

<tt>renderer <nowiki>=</nowiki> '''gtk_cell_renderer_pixbuf_new'''();
</tt>

Finally, we create and append the new column, using the model and renderer previously created.

This call also sets the property "stock-id" of the GtkCellrendererPixbuf. The value is set to 0 which is the number of the column in the GtkTreeModel that stores the stock-id.

<tt> column <nowiki>=</nowiki> '''hildon_touch_selector_append_column''' ('''HILDON_TOUCH_SELECTOR''' (selector),
'''GTK_TREE_MODEL''' (store_icons),
renderer,
"stock-id", 0,
NULL);
</tt>

To summarize, setting a new custom column in a touchable selector is quite similar to setting a new column in a normal GtkTreeview. Create a model to store the data and a cell renderer to properly show this data in each row, and finally add the new column.

==Picker dialog and picker buttons ==
Normally, you use HildonTouchSelector together with a HildonPickerDialog activated from a button. For most common cases you use HildonPickerButton.

This is the usual way to present a selector to the user. The picker button opens a dialog which presents the selector and properly manages user interaction.

'''Example'''

Previous sections showed you how to create a touchable selector. In most cases the next step is to attach the selector to a HildonPickerButton.

A HildonPickerButton is a special GtkButton which displays two labels, title and value, and brings up a HildonPickerDialog. The user chooses one or several items. A string representation of the chosen items is displayed in the value label of the picker button.

Below, a modified version of the previous main function is shown, in which you can check how a HildonPickerButton is created and attached to a selector. Also a callback to catch the signal "value-changed" emitted is added.

[[Image:example-picker-button.png|400px]]

'''Example 6.3. Example of a Hildon picker button'''

<tt>'''static''' void
'''on_picker_value_changed''' (HildonPickerButton <nowiki>*</nowiki> button, gpointer data)
{
'''g_print''' ("Newly selected value: %s\n",
'''hildon_button_get_value''' ('''HILDON_BUTTON''' (button)));
}

int
'''main''' (int argc, char <nowiki>**</nowiki>argv)
{
HildonProgram <nowiki>*</nowiki>program<nowiki>;</nowiki>
GtkWidget <nowiki>*</nowiki>window<nowiki>;</nowiki>
GtkWidget <nowiki>*</nowiki>picker_button<nowiki>;</nowiki>

'''hildon_gtk_init''' (&argc, &argv);

program <nowiki>=</nowiki> '''hildon_program_get_instance''' ();
'''g_set_application_name''' ("hildon-touch-selector example program");

window <nowiki>=</nowiki> '''hildon_stackable_window_new''' ();
'''hildon_program_add_window''' (program, '''HILDON_WINDOW''' (window));

''/* Create touch selector */''
selector <nowiki>=</nowiki> '''create_customized_selector''' ();

''/* Create a picker button */''
picker_button <nowiki>=</nowiki> '''hildon_picker_button_new''' (HILDON_SIZE_AUTO,
HILDON_BUTTON_ARRANGEMENT_VERTICAL);

''/* Set a title to the button */''
'''hildon_button_set_title''' ('''HILDON_BUTTON''' (picker_button), "Select an item");

''/* Attach the touch selector to the picker button*/''
'''hildon_picker_button_set_selector''' ('''HILDON_PICKER_BUTTON''' (picker_button),
'''HILDON_TOUCH_SELECTOR''' (selector));

''/* Attach callback to the "value-changed" signal*/''
'''g_signal_connect''' ('''G_OBJECT''' (picker_button), "value-changed",
'''G_CALLBACK''' (on_picker_value_changed), NULL);

''/* Add button to main window */''
'''gtk_container_add''' ('''GTK_CONTAINER''' (window), picker_button);

'''g_signal_connect''' ('''G_OBJECT''' (window), "destroy",
'''G_CALLBACK''' (gtk_main_quit), NULL);

'''gtk_widget_show_all''' ('''GTK_WIDGET''' (window));

'''gtk_main''' ();

'''return''' 0<nowiki>;</nowiki>
}

</tt>

In the above example a picker button is created. The reference to the attached selector is stored in the property "touch-selector" of the picker button. To retrieve the attached selector , use function <code>hildon_picker_button_get_selector()</code>. To attach the selector, use the function <code>hildon_picker_button_set_selector()</code>.

Note that you do not need to take care of the HildonPickerDialog. The dialog is automatically brought up when users click the picker button and closed when the selection is done.

The dialog shows a button "Done" to allow users finish the selection when the touchable selector allows multiple selection. When the selector allows only single selection, the dialog does not show any button and closes when the user taps on one item.

The label of the button "Done" can be set by using <code>hildon_picker_button_set_done_button_text()</code> and retrieved by using <code>hildon_picker_button_get_done_button_text()</code>.

When users finish their selection, the value label on the button automatically changes to show a textual representation of the item or items selected.

In most cases you want to perform any action when selection is finished. To do that, add a handler to the signal "value-changed" of the picker button. In this example the handler attached to "value-changed" signal retrieves the value label of the button and prints a debug message.

==Touch selector entry ==
The HildonTouchSelectorEntry is a selector widget with a text entry that allows users to select an item from a predefined list or to enter a different one in a HildonEntry. Items can also be searched and selected by typing in the entry.

An additional feature is that the HildonEntry is auto-completed with the list's items as the user types their name.

Example below shows how to build a selector to pick a word in a list of words.

[[Image:Touch_selector_entry.png|400px]]

'''Example 6.4. Example of a Hildon picker button with a selector entry'''

<tt>'''<nowiki>#include</nowiki>''' <hildon/hildon.h>
'''static''' '''const''' gchar<nowiki>*</nowiki> artists [] <nowiki>=</nowiki> {
"AC/DC",
"Aerosmith",
"Alice in Chains",
"Black Sabbath",
"Carcass",
"Danzig",
"Deep Purple",
"Dream Theater",
"Eric Clapton",
NULL
}<nowiki>;</nowiki>
int
'''main''' (int argc, char <nowiki>**</nowiki>argv)
{
HildonProgram <nowiki>*</nowiki>program<nowiki>;</nowiki>
GtkWidget <nowiki>*</nowiki>window<nowiki>;</nowiki>
GtkWidget <nowiki>*</nowiki>button<nowiki>;</nowiki>
GtkWidget <nowiki>*</nowiki>selector<nowiki>;</nowiki>
gint i<nowiki>;</nowiki>
'''hildon_gtk_init''' (&argc, &argv);
program <nowiki>=</nowiki> '''hildon_program_get_instance''' ();
g_set_application_name
("HildonTouchSelectorEntry example program");
window <nowiki>=</nowiki> '''hildon_stackable_window_new''' ();
'''hildon_program_add_window''' (program, '''HILDON_WINDOW''' (window));
''/* Create a picker button */''
button <nowiki>=</nowiki> '''hildon_picker_button_new''' (HILDON_SIZE_AUTO,
HILDON_BUTTON_ARRANGEMENT_VERTICAL);
'''hildon_button_set_title''' ('''HILDON_BUTTON''' (button), "Pick a band!");
''/* Create a touch selector entry */''
selector <nowiki>=</nowiki> '''hildon_touch_selector_entry_new_text''' ();
''/* Populate the selector */''
'''for''' (i <nowiki>=</nowiki> 0<nowiki>;</nowiki> artists [i] <nowiki>!=</nowiki> NULL<nowiki>;</nowiki> i++) {
'''hildon_touch_selector_append_text''' ('''HILDON_TOUCH_SELECTOR''' (selector),
artists [i]);
}
''/* Attach selector to the picker button */''
'''hildon_picker_button_set_selector''' ('''HILDON_PICKER_BUTTON''' (button),
'''HILDON_TOUCH_SELECTOR''' (selector));
'''gtk_container_add''' ('''GTK_CONTAINER''' (window), button);
'''g_signal_connect''' ('''G_OBJECT''' (window), "destroy",
'''G_CALLBACK''' (gtk_main_quit), NULL);
'''gtk_widget_show_all''' ('''GTK_WIDGET''' (window));
'''gtk_main''' ();
'''return''' 0<nowiki>;</nowiki>
}
</tt>

As you can see in the example above, the use of this widget is similar to using a normal touchable selector.

You can also use custom columns in a HildonTouchableEntry but at least one column must be a text column. The text column is indicated by the property "text_column" which you set with <code>hildon_touch_selector_entry_set_text_column()</code>.

==Pre-built selectors ==
The widgets HildonDateButton and HildonTimeButton are buttons displaying and allowing the selection of date and time, respectively. Developers can use them directly instead of building their own date or time selectors.

Both widgets are specialized picker buttons with a convenient touchable selector attached that you can use directly in your application.

Here a simple application using a HildonDateButton.

'''Example 6.5. Example of a Hildon date button'''

#include <hildon/hildon.h>

int
main (int argc, char **argv)
{
HildonProgram *program = NULL;
GtkWidget *window = NULL;
GtkWidget *picker_button = NULL;

hildon_gtk_init (&argc, &argv);

program = hildon_program_get_instance ();
g_set_application_name
("hildon-date-button example program");

window = hildon_stackable_window_new ();
hildon_program_add_window (program, HILDON_WINDOW (window));

/* Create a picker button */
picker_button = hildon_date_button_new (HILDON_SIZE_AUTO,
HILDON_BUTTON_ARRANGEMENT_VERTICAL);

/* Set a title to the button*/
hildon_button_set_title (HILDON_BUTTON (picker_button), "Pick a date");

/* Add button to main window */
gtk_container_add (GTK_CONTAINER (window), picker_button);

g_signal_connect (G_OBJECT (window), "destroy",
G_CALLBACK (gtk_main_quit), NULL);

gtk_widget_show_all (GTK_WIDGET (window));

gtk_main ();

return 0;
}

Maemo-releases

2009-10-29T13:32:00Z

192.100.124.219: /* The rationale behind maemo-release */

== The rationale behind maemo-release ==

The maemo-release package seeks to address the situation wherein a source package is forked into gregale/bora/chinook/diablo/fremantle versions of itself because one set of Build-Depends does not work for all distributions.

Example: Fremantle provides libgstfarsight0.10-dev, whereas previous distributions do not. pidgin needs to Build-Depend on it for voice/video support to be compiled in during the build process. However, the libgstfarsight0.10-dev package does not exist in any previous distribution.

This results in having to provide a different debian/control file for the various distributions, which in turn forces one to make a different debian/changelog file for the various distributions. At this point, different distributions have different source packages.

To prevent this one reason for forking the source package, we need the maemo-release package. Then, knowing which distribution(s) contain a needed package foo, we can create an appropriate debian/control entry.

Example: Suppose Bora and Diablo contain package foo, but the other distributions do not. The corresponding debian/control Build-Depends entry will be:

<code>
Build-Depends: package1-dev,
package2-dev,
...,
foo | maemo-release (= 1.0.0) | maemo-release (= 3.0.0) | maemo-release (= 5.0.0),
...,
packagen-dev
</code>

This way you can describe intervals of distributions wherein a certain package has become available. Examples:

{|style="border:1px solid;"
|-
!align="center"|   (1.0.0) Gregale  
!align="center"|   (2.0.0) Bora  
!align="center"|   (3.0.0) Chinook  
!align="center"|   (4.0.0) Diablo  
!align="center"|   (5.0.0) Fremantle  
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (< 3.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="2" | foo is absent
| align="center" style="background:green; color:white" colspan="3" | foo is present
|-
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (< 3.0.0) | maemo-release (> 4.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="2" | foo is absent
| align="center" style="background:green; color:white" colspan="2" | foo is present
| align="center" style="background:red; color:white" colspan="1" | foo is absent
|-
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (= 1.0.0) | maemo-release (= 3.0.0) | maemo-release (= 5.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="1" | foo is absent
| align="center" style="background:green; color:white" colspan="1" | foo is present
| align="center" style="background:red; color:white" colspan="1" | foo is absent
| align="center" style="background:green; color:white" colspan="1" | foo is present
| align="center" style="background:red; color:white" colspan="1" | foo is absent
|-
|}

Of course, the rest of the build process has also to be made tolerant of the presence/absence of a given package.

Maemo-releases

2009-10-29T13:24:12Z

192.100.124.219: /* The rationale behind maemo-release */

== The rationale behind maemo-release ==

The maemo-release package seeks to address the situation wherein a source package is forked into gregale/bora/chinook/diablo/fremantle versions of itself because one set of Build-Depends does not work for all distributions.

Example: Fremantle provides libgstfarsight0.10-dev, whereas previous distributions do not. pidgin needs to Build-Depend on it for voice/video support to be compiled in during the build process. However, the libgstfarsight0.10-dev package does not exist in any previous distribution.

This results in having to provide a different debian/control file for the various distributions, which in turn forces one to make a different debian/changelog file for the various distributions. At this point, different distributions have different source packages.

To prevent this one reason for forking the source package, we need the maemo-release package. Then, knowing which distribution(s) contain a needed package foo, we can create an appropriate debian/control entry.

Example: Suppose Bora and Diablo contain package foo, but the other distributions do not. The corresponding debian/control Build-Depends entry will be:

<code>
Build-Depends: package1-dev,
package2-dev,
...,
foo | maemo-release (= 1.0.0) | maemo-release (= 3.0.0) | maemo-release (= 5.0.0),
...,
packagen-dev
</code>

This way you can describe intervals of distributions wherein a certain package has become available. Examples:

{|style="border:1px solid;"
|-
!align="center"|   (1.0.0) Gregale  
!align="center"|   (2.0.0) Bora  
!align="center"|   (3.0.0) Chinook  
!align="center"|   (4.0.0) Diablo  
!align="center"|   (5.0.0) Fremantle  
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (< 3.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="2" | foo is absent
| align="center" style="background:green; color:white" colspan="3" | foo is present
|-
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (< 2.0.0) | maemo-release (> 4.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="2" | foo is absent
| align="center" style="background:green; color:white" colspan="2" | foo is present
| align="center" style="background:red; color:white" colspan="1" | foo is absent
|-
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (= 1.0.0) | maemo-release (= 3.0.0) | maemo-release (= 5.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="1" | foo is absent
| align="center" style="background:green; color:white" colspan="1" | foo is present
| align="center" style="background:red; color:white" colspan="1" | foo is absent
| align="center" style="background:green; color:white" colspan="1" | foo is present
| align="center" style="background:red; color:white" colspan="1" | foo is absent
|-
|}

Of course, the rest of the build process has also to be made tolerant of the presence/absence of a given package.

Maemo-releases

2009-10-29T13:21:22Z

192.100.124.219: /* The rationale behind maemo-release */

== The rationale behind maemo-release ==

The maemo-release package seeks to address the situation wherein a source package is forked into gregale/bora/chinook/diablo/fremantle versions of itself because one set of Build-Depends does not work for all distributions.

Example: Fremantle provides libgstfarsight0.10-dev, whereas previous distributions do not. pidgin needs to Build-Depend on it for voice/video support to be compiled in during the build process. However, the libgstfarsight0.10-dev package does not exist in any previous distribution.

This results in having to provide a different debian/control file for the various distributions, which in turn forces one to make a different debian/changelog file for the various distributions. At this point, different distributions have different source packages.

To prevent this one reason for forking the source package, we need the maemo-release package. Then, knowing which distribution(s) contain a needed package foo, we can create an appropriate debian/control entry.

Example: Suppose Bora and Diablo contain package foo, but the other distributions do not. The corresponding debian/control Build-Depends entry will be:

<code>
Build-Depends: package1-dev,
package2-dev,
...,
foo | maemo-release (= 1.0.0) | maemo-release (= 3.0.0) | maemo-release (= 5.0.0),
...,
packagen-dev
</code>

This way you can describe intervals of distributions wherein a certain package has become available. Examples:

{|style="border:1px solid;"
|-
!align="center"|   (1.0.0) Gregale  
!align="center"|   (2.0.0) Bora  
!align="center"|   (3.0.0) Chinook  
!align="center"|   (4.0.0) Diablo  
!align="center"|   (5.0.0) Fremantle  
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (< 3.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="2" | foo is absent
| align="center" style="background:green; color:white" colspan="3" | foo is present
|-
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (< 2.0.0) | maemo-release (> 4.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="2" | foo is absent
| align="center" style="background:green; color:white" colspan="2" | foo is present
| align="center" style="background:red; color:white" colspan="1" | foo is absent
|-
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (= 1.0.0) | maemo-release (= 3.0.0) | maemo-release (= 5.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="1" | foo is absent
| align="center" style="background:green; color:white" colspan="1" | foo is present
| align="center" style="background:red; color:white" colspan="1" | foo is absent
| align="center" style="background:green; color:white" colspan="1" | foo is present
| align="center" style="background:red; color:white" colspan="1" | foo is absent
|-
|}

Maemo-releases

2009-10-29T13:17:27Z

192.100.124.219: New page

== The rationale behind maemo-release ==

The maemo-release package seeks to address the situation wherein a source package is forked into gregale/bora/chinook/diablo/fremantle versions of itself because one set of Build-Depends does not work for all distributions.

Example: Fremantle provides libgstfarsight0.10-dev, whereas previous distributions do not. pidgin needs to Build-Depend on it for voice/video support to be compiled in during the build process. However, the libgstfarsight0.10-dev package does not exist in any previous distribution.

This results in having to provide a different debian/control file for the various distributions, which in turn forces one to make a different debian/changelog file for the various distributions. At this point, different distributions have different source packages.

To prevent this one reason for forking the source package, we need the maemo-release package. Then, knowing which distribution(s) contain a needed package foo, we can create an appropriate debian/control entry.

Example: Suppose Bora and Diablo contain package foo, but the other distributions do not. The corresponding debian/control Build-Depends entry will be:

<code>
Build-Depends: package1-dev,
package2-dev,
...,
foo | maemo-version (= 1.0.0) | maemo-version (= 3.0.0) | maemo-version (= 5.0.0),
...,
packagen-dev
</code>

This way you can describe intervals of distributions wherein a certain package has become available. Examples:

{|style="border:1px solid;"
|-
!align="center"|   (1.0.0) Gregale  
!align="center"|   (2.0.0) Bora  
!align="center"|   (3.0.0) Chinook  
!align="center"|   (4.0.0) Diablo  
!align="center"|   (5.0.0) Fremantle  
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (< 3.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="2" | foo is absent
| align="center" style="background:green; color:white" colspan="3" | foo is present
|-
|-
|colspan="5" style="border:1px solid;" | Example: <code>foo | maemo-release (< 2.0.0) | maemo-release (> 4.0.0)</code>
|-
| align="center" style="background:red; color:white" colspan="2" | foo is absent
| align="center" style="background:green; color:white" colspan="2" | foo is present
| align="center" style="background:red; color:white" colspan="1" | foo is absent
|-
|}

Maemo Summit 2009

2009-10-19T14:25:58Z

192.100.124.219: Link to slides of my talk

<div style="font-weight:bold;">October 9-10-11, 2009- [http://www.westergasfabriek.nl/english/engels_welcome.php WesterGasFabriek] - Amsterdam</div>
[[Image:Westergas.png‎]]

== Conference archive ==
Videos, slides and other materials related to the sessions. Feel free to update your own.

=== Thursday, October 8 ===

17:00 - 19:00 Registration at the Community Room (Zuiveringshal Oost). '''Early registrations encouraged to avoid queues and stress on Friday morning!'''

19:00 - 00:00 The official get together on Thursday will be [http://www.indewildeman.nl/indexe.html In de Wildeman], a beer house ([http://maps.google.nl/maps?f=q&source=s_q&hl=en&geocode=&q=Kolksteeg+3+1012+PT+Amsterdam&sll=52.377171,4.897242&sspn=0.005803,0.016512&ie=UTF8&hq=&hnear=Kolksteeg+3,+1012+Amsterdam,+North+Holland&t=h&z=16 Map]).

=== [[/Schedule/Day 1 | Friday, October 9]] ===

9:00 Registration at the Community Room (Zuiveringshal Oost). '''Come early: you won't get to the conference without your badge.'''

10:00 '''Programme starts at N900 (Transformatorhuis)'''

10:00 '''Welcome - Opening of Summit ''' by [http://maemo.org/profile/view/peterschneider.html Peter Schneider], Head of Maemo Marketing @ Nokia

10:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Maemo_5_and_the_N900 Maemo 5 and the Nokia N900] by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi], VP - Maemo Devices @ Nokia [http://www.slideshare.net/peterschneider/maemo-and-the-nokia-n900 (slides)]

11:00 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Changing_PC_.26_Mobile_Landscape.3B_Why_Linux_will_play_a_Critical_Role Changing PC & Mobile Landscape; Why Linux will play a Critical Role]''' by Jim Zemlin, Executive Director @ Linux Foundation

11:30 '''Break'''

11:45 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Nokia_Nseries_Devices_on_Maemo Nokia Nseries Devices on Maemo]''' by Jose-Luis Martinez Merino, VP, Marketing @ Nokia [http://www.slideshare.net/peterschneider/nokia-nseries-and-maemo-6 (slides)]

12:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Harmattan_Highlights_-_Developer_Opportunities Harmattan Highlights - Developer Opportunities]''' by Janne Heikkinen, Director - Maemo Product Planning @ Nokia [http://www.slideshare.net/peterschneider/maemo-5-developer-offering (Maemo 5 slides)] - [http://www.slideshare.net/peterschneider/maemo-6-technology-highlights (Maemo 6 slides)]

13:00 '''Lunch - Maemo Expo opens'''

14:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Why_the_Maemo_Community_matters_to_Nokia Why the Maemo Community matters to Nokia]''' - Alan "[http://maemo.org/profile/view/qole/ qole]" Bruce of [[Community Council|Maemo Community Council]] interviewing Ari Jaaksi, VP - Maemo Devices @ Nokia

15:00 '''Expert streams'''

{| class="wikitable" border="2"
|-
! Time
! N900 - ''chair: John Loughney''
! N810 - ''chair: Anthony Fabbricino''
! N800 - ''chair: Quim Gil''
|-

|-
| 15:00 - 15:25
| rowspan="2" | '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#UX_panel UX Panel]'''
''Moderated by: [http://maemo.org/profile/view/timsamoff Tim Samoff], Maemo Council,''
''with Harri Kiljander, Director Maemo UX Design and Martin Schüle, Principal Designer Maemo 5''
| '''UI design of Maemo 5 apps'''
''Annu-Maaria Nivala, UX team, Digia'' [http://www.slideshare.net/annumaaria/ui-design-of-maemo-5-apps-digia (slides)]
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Cross-platform_with_Qt_-_live Cross-platform with Qt - live]'''
''Ariya Hidayat, Software Engineer, Nokia''
|-
| 15:30 - 15:55
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Developing_widgets_on_Maemo_5_-_showcase_Foreca_Weather Developing widgets on Maemo 5 - showcase Foreca Weather]'''
''Juha Järvi, Software Designer, Foreca''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Mer_-_how_the_community_innovates Mer - how the community innovates]'''
''Carsten Munk, Lead Developer, Mer project'' [http://www.slideshare.net/carstenmunk/mer-how-the-community-innovates (slides)]
|-
| 16.00 - 16.25
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Firefox_on_Maemo Firefox on Maemo]'''
''Stuart Parmenter, Director of Engineering, Mozilla''

| '''Developing apps with Qt for Maemo5'''
''Kate Alhola, Forum Nokia, Chief Guru on Maemo
| | '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Your_foundation_for_open-source_innovation:_TI.E2.80.99s_OMAP_processor-based_Zoom_platform Your foundation for open-source innovation: TI’s OMAP processor-based Zoom platform]'''
''Ameet Suri, Texas Instruments''
|-
| 16.30 - 16.55
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Present_and_future_of_Maemo_digital_marketing Present andd future of Maemo digital marketing]'''
''Isko Salminen, Production Manager, Activeark & Jussi Mäkinen, Maemo Marketing, Nokia'''
| '''Developing apps with Qt on Harmattan'''
''Ville Lavonius, Product Manager Developer Offering, Nokia''
| '''Feedservice and plug-ins development in Maemo 5'''
''Mikko Levonmaa, Ixonos''
|-
| 17.00 - 17.25
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Biz_apps_on_Maemo Biz apps on Maemo]'''
''Kari Pikkarainen, Product Manager Productivity, Nokia''
| '''Developing apps with Nokia Web Runtime'''
''Santtu Ahonen, Head of Developer Offering, Nokia''
| '''[http://www.slideshare.net/jtukkine/maemo-6-harmattan-architecture-overview Harmattan Architecture Overview]'''
''Juha Tukkinen, Principal Engineer, Maemo Devices, Nokia'' [http://www.slideshare.net/jtukkine/maemo-6-harmattan-architecture-overview (slides)]
|-
| 17.30 - 18.00
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Skype_on_Maemo Skype on Maemo]'''
''Mark Douglas, Mobile Product Manager, Skype''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Developer_Support_for_Maemo_by_Forum_Nokia Developer Support for Maemo by Forum Nokia]'''
''Matt Collins, Director, Forum Nokia Marketing''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Porting_an_OpenGL_game_to_GL_ES Porting an OpenGL game to GL ES]'''
''Oliver Mcfadden, Software Engineer, Nokia''
|-
|}

20:00 '''Maemo Party in FlexBar''' DJ's [http://valeriecherie.blogspot.com/2008/02/from-britain-with-love.html Russ Chimes] & [http://www.trashmenagerie.com/mixes/2008/04/01/grums-nllr-mixtape/ Grum] (check the mixtapes!) visuals by [http://www.xploitec.org/blog/?page_id=103 Xploitec VJ's]. coordinated by Jussi Mäkinen. It's a public bar and the doors are open to anybody. Our ''program'' will go until 23h or so, but the bar is open until really late with good music. Special cocktail hour sponsored by the lovely Skype people. Don't forget the Saturday schedule, though. :)

=== [[/Day 2 | Saturday, October 10]] ===

{| class="wikitable" border="2"
|-
! Time
! N900
! N810
! N800
! 770
|-
| align="right" | 9.00
| colspan="4" align="center" | Doors Open
|-
| 10.00 - 10.15
| colspan="4" align="center" | '''Welcome to Community days''' ''Maemo Community Council'' ([http://www.youtube.com/watch?v=6Mm-OS__8V0 Video])
|-
| 10.15 - 10:45
| colspan="4" align="center" | '''Keynote: Ton Roosendaal, the Blender Foundation'''
|-
| 10.45 - 11:00
| colspan="4" align="center" | Coffee-break
|-
| 11.00 - 11.25
| [[/Day 2#Designing_UI_for_Maemo_5 | '''Designing UI for Maemo 5''']] 
''Mox Soini'' ([http://www.slideshare.net/moximillian/soini-designing-ui-for-maemo-5 Slides])
| [[/Day 2#PyQt_application_development_on_Maemo | '''PyQt application development on Maemo''']] 
''Attila Csipa'' ([http://www.slideshare.net/guestb404461/pyqt-application-development-on-maemo Slides], [http://web.atombiztos.hu/pyqt_on_maemo.zip .odp with demo videos])
|rowspan="2" | [[/Day 2#Getting_started_session | '''Getting started session''']] ''Daniel Wilms and others''
| ------
|-
| 11.30 - 11.55
| [[/Day 2#Personalizing_your_Maemo_5_device | '''Personalizing your Maemo 5 device''']] ''Hartti Suomela''
| [[/Day 2#Canola_application_and_framework_for_rich_GUI | '''Canola application and framework for rich GUI''']] 
''Gustavo Sverzut Barbieri''
| ------
|-
| 12.00 - 12.25
| [[/Day 2#Modest.2C_email_client_for_Fremantle | '''Modest, email client for Fremantle''']] 
''Sergio Villar, Jose Dapena''
| [[/Day_2#Introducing_the_Harmattan_UI_framework | '''Introducing the Harmattan UI framework''']] 
''Tomas Junnonen''
| [[/Day 2#Maemomm:_Maemo_with_C.2B.2B_and_a_Gtkmm_flavour | '''Maemomm: Maemo with C++ and a Gtkmm flavour''']] 
''David King''
| rowspan="2" | [[/Day 2#Extras.2Fautobuilder.2Finterfaces_round-table | '''Extras/autobuilder/interfaces round-table''']]
|-
| 12.30 - 12.55
| [[/Day_2#Maemo_Co-creation | '''Maemo Co-Creation Showcase''']] 
''Jussi Mäkinen''
| [[/Day 2#Creating_packages_for_the_Maemo_platform | '''Creating packages for the Maemo platform''']] 
''Jeremiah Foster'' 
[http://www.slideshare.net/miahfost/packaging-for-the-maemo-platform (slides)]
| [[/Day 2#Developments_in_The_Qt_WebKit_Integration | '''Developments in The Qt WebKit Integration''']] 
''Kenneth Rohde Christiansen''
|-
| 13.00 - 14.30
| colspan="4" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="4" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Giving_Great_Presentations | '''Giving Great Presentations''']] - ''Dave Neary''
# [[/Lightning talks#Feedhandler_-_Integrating_RSS_newsreaders_with_the_browser | '''Feedhandler - Integrating RSS newsreaders with the browser''']] - ''Thomas Perl''
# [[/Lightning talks#python-mafw:_MAFW_framework_for_Python_developers | '''python-mafw: MAFW framework for Python developers''']] - ''Andrea Grandi'' - [http://www.slideshare.net/andy80/pythonmafw-intoduction-at-maemo-summit-2009 (Slides)]
# [[/Lightning talks#DVCS.3F_git.3F_-_How_does_that_work_then.3F | '''DVCS? git? - How does that work then?''']] - ''David Greaves'' - [http://www.slideshare.net/mrlbt/git-how-does-that-work-then (Slides)]
# [[/Lightning_talks#BlueMaemo_-_Bluetooth_HID_mouse_.26_keyboard_for_Maemo | '''BlueMaemo - Bluetooth HID mouse & keyboard for Maemo''']] - ''Valério Valério'' [http://www.slideshare.net/VDVsx/bluemaemo-bluetooth-hid-mouse-keyboard-for-maemo (Slides)]
# [[/Lightning_talks#Continous_Integration_with_CruiseControl_and_Scratchbox | '''Continous Integration with CruiseControl and Scratchbox''']] - ''Jani Mikkonen'' [http://www.slideshare.net/rasjani/continuous-integration-with-scratchbox-and-cruisecontrol (Slides)]
# [[/Lightning_talks#Conboy.2C_Tomboy_and_Snowy | '''Conboy, Tomboy and Snowy''']] - ''Cornelius Hald''
# [[/Lightning_talks#Ogg_support_status | '''Ogg support status''']] - ''Tuomas Kulve''
# [[/Lightning_talks#Maemo_Platform_Security | '''Maemo Platform Security''']] - ''Elena Reshetova''
|-
| 15:25 - 15:45
| colspan="4" align="center" | Break
|-
| 15.45 - 16.10
| [[/Day 2#GUPnP_and_Rygel:_The_UPnP.2FDLNA_solution_for_Maemo | '''GUPnP and Rygel: The UPnP/DLNA solution for Maemo''']] 
''Zeeshan Ali'' [http://github.com/zeenix/rygel-presentation-2009/raw/maemo-summit/slides.odp (slides)]
| [[/Day 2#Adapting_GNOME_applications_to_Maemo_Fremantle | '''Adapting GNOME applications to Maemo Fremantle''']] 
''Joaquim Rocha'' [http://www.slideshare.net/j_rocha/adapting-gnome-applications-to-maemo-fremantle (slides)]
| [[/Day 2#Contributing_with_Git_.26_Gitorious | '''Contributing with Git & Gitorious''']] Johan Sørensen
| [[/Day_2#High-resolution_image_processing_on_Maemo_devices | '''High-resolution image processing on Maemo devices''']] 
''Alexander Bokovoy''
|-
| 16.15 - 16.40
| [[/Day 2#Mer:_A_year_after| '''Mer: A year after''']] 
''Carsten Valdemar Munk'' [http://www.slideshare.net/carstenmunk/mer-a-year-after (slides)]
| [[/Day_2#Intelligent_Usage_of_Fremantle_Location_Framework_For_Location-aware_Applications | '''Intelligent Usage of Fremantle Location Framework For Location-aware Applications''']] 
''Quanyi Sun''
| [[/Day 2#Hildon_toolkit_for_Fremantle | '''Hildon toolkit for Fremantle''']] 
''Alberto Garcia, Claudio Saavedra''
| rowspan="2" | [[/Day_2#Git_hands-on_workshop | '''Git hands-on workshop''']] 
''David Greaves''
|-
| 16.45 - 17.10
| [[/Day 2#maemo.org_Bug_Management | '''maemo.org Bug Management''']] 
''Andre Klapper'' [http://home.arcor.de/ak-47/en/linux/maemosummit2009.pdf (slides)]
| [[/Day 2#Go-to_market_opportunities_for_mobile_application_developers | '''Go-to market opportunities for mobile application developers''']] 
''Boaz Zilberman''
| [[/Day_2#Tracker:_Dial_M_for_Metadata | '''Tracker: Dial M for Metadata''']] 
''Ivan Frade, Iridian Kiiskinen''
|-
| 17.10 - 17.30
| colspan="4" align="center" | Break
|-
| 17.30 - 17.55
| [[/Day 2#Canola:_Beyond_the_media_playback | '''Canola: Beyond the media playback''']] ''Eduardo Lima''
| [[/Day 2#Hands-on_development_with_Nokia_Web_Runtime | '''Hands-on development with Nokia Web Runtime''']] 
''Oren Levine'' [http://www.slideshare.net/olevine/handson-development-with-nokia-web-runtime (Slides)] [http://www.forum.nokia.com/Technology_Topics/Web_Technologies/Web_Runtime/ (More information)]
| [[/Day 2#The_Qt_Mobility_Project | '''The Qt Mobility Project''']] ''Alex Luddy''
| [[/Day_2#Hacking_officially_unsupported_Bluetooth_profiles_to_work_in_Fremantle | '''Hacking officially unsupported Bluetooth profiles to work in Fremantle''']] 
''Johan Hedberg''
|-
| 18.00 - 18.25
| [[/Day_2#The_Maemo_5_Address_Book | '''The Maemo 5 Address Book''']] 
''Mathias Hasselmann, Travis Reiter''
| [[/Day 2#Publishing_your_software_through_maemo.org | '''Publishing your software through maemo.org''']] ''Niels Breet''
| [[/Day_2#Maemo_and_oFono | '''Maemo and oFono''']] 
''Aki Niemi, Rémi Denis-Courmont''
| [[/Day_2#The_future_of_GTK.2B.2FHildon_in_Maemo_Harmattan | '''The future of GTK+/Hildon in Maemo Harmattan''']] 
''Alberto Garcia, Claudio Saavedra''
|-
| 18.45 - 20.30
| colspan="4" align="center" | Maemo Drinks in N900 room
|}

=== [[/Day 3 | Sunday, October 11]] ===

{| class="wikitable" border="2"
|-
! Time
! N900
! N810
! N800
! 770
|-
| align="right" | 9.00
| colspan="4" align="center" | Doors Open
|-
| 10.00 - 10.45
| colspan="4" align="center" | [[/Day 3#Fremantle_Stars_showcase | '''Fremantle Stars showcase''']] Including liqbase, OSM2Go, [http://mauku.innologies.com Mauku], OMWeather [http://www.slideshare.net/vasvlad/omweather-in-maemo-summit-2009 (Slides+notes)], eCoach and more.
|-
| 10.45 - 11.00
| colspan="4" align="center" | Coffee-break
|-
| 11.00 - 11.25
| [[/Day 3#Maemo_Browser_for_power_users | '''Maemo Browser for power users''']] ''Mikko Korpelainen'' - [http://www.slideshare.net/mtkorpel/maemo-browser (presentation content)]
 [[/Day 3#Maemo_Browser_evolution | ''Maemo Browser evolution'']] ''Oleg Romashin''
 
 [[/Day 3#Maemo_Browser_extension_development | ''Maemo Browser extension development'']] ''Sudarsana Nagineni''

| [[/Day 3#JamMo_-_Jamming_mobile_game_for_children | '''JamMo - Jamming mobile game for children''']] 
''Aapo Rantalainen''
| [[/Day_3#Building_for_Mer | '''Building for Mer''']] ''David Greaves'' - [http://www.slideshare.net/mrlbt/building-for-mer (Slides+notes)] [[Mer/Build | (see also Mer Build page)]]
| rowspan="2" | [[/Day 3#Hackathon:_Integrating_Canola_with_Fremantle | '''Canola Fremantle Hackathon''']]
|-
| 11.30 - 11.55
| [[/Day 3#Maemo_documentation_co-creation | '''Maemo documentation co-creation ''']] 
''Dave Neary''
| [[/Day_3#Designing_QT_application_for_Maemo_5_and_Maemo_6 | '''Designing Qt application for Maemo 5 and Maemo 6''']] ''Sergiy Dubovik, Ian Monroe''
| [[/Day 3#Writing_plugins_for_MAFW | '''Writing plugins for MAFW ''']] ''Iago Toral'' [http://blogs.igalia.com/itoral/2009/10/11/writing-mafw-plugins-talk-maemo-summit/ (blog post with slides and source code examples)]
|-
| 12.00 - 12.25
| [[/Day_3#Mobile_Office_based_on_KOffice_Open_Source_Project | '''Mobile Office based on KOffice Open Source Project''']] 
''Suresh Chande'' [http://sureshchande.blogspot.com/2009/10/mobile-office-based-on-koffice-for.html (blog post + video demo)]
| [[/Day 3#Handheld_Glom:_Easy_database_applications | '''Handheld Glom: Easy database applications''']] 
''Murray Cumming''
| [[/Day_3#Maemo_Platform_Security:_Principles_and_Concepts | '''Maemo Platform Security: Principles and Concepts''']] 
''Elena Reshetova''
|[[/Day_3#Extending_the_Hildon_desktop | '''Extending the Hildon desktop ''']] 
''Marc Ordinas i Llopis''
|-
| 12.30 - 12.55
| [[/Day 3#Towards_painless_and_quality_translations | '''Towards painless and quality translations''']] Dimitris Glezos ([http://media.indifex.com/other/maesum.pdf slides])
| [[/Day_3#10_Tips_for_Designing_Mobile_Widgets | '''10 Tips for Designing Mobile Widgets''']] 
''Rajesh Lal'' ([http://www.slideshare.net/rajeshlal/ten-tips-for-designing-mobile-widgets-2009-q3-maemo-summit-v1 slideshare], [http://irajesh.com/files/10TipsForDesigningMobileWidgets.pdf pdf], [http://irajesh.com/files/10TipsForDesigningMobileWidgets.ppt ppt], [http://irajesh.com/files/10TipsForDesigningMobileWidgets.pps pps])
| [[/Day_3#Telepathy_on_Maemo | '''Telepathy on Maemo''']] 
''Marco Barisione''
| [[/Day_3#What_to_do_about_.2Fopt_in_Fremantle | '''What to do about /opt in Fremantle''']] 
''Marius Vollmer''
|-
| 13.00 - 14.30
| colspan="4" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="4" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Issues_on_adapting_Maemo_4_application_to_Maemo_5 | '''Issues on adapting Maemo 4 application to Maemo 5''']] - ''Aniello del Sorbo'' - [http://www.slideshare.net/anidel/issues-on-adapting-maemo-4-applications-to-maemo-5-2229255 (Slides)]
# [[/Lightning talks#How_to_speed_up_your_Maemo_application_development | '''How to speed up your Maemo application development''']] - ''Raul Herbster''
# [[/Lightning talks#Development_Nirvana:_How_Maemo_Application_Development_Should_Be | '''Development Nirvana: How Maemo Application Development Should Be''']] - ''Andrew Flegg''
# [[/Lightning talks#GSoC_presentation:_BitTorrent_plugin_for_Canola | '''GSoC presentation: BitTorrent plugin for Canola''']] - ''Lauri Võsandi''
# [[/Lightning talks#GSoC_Project_presentation:_Picasa_plugin_for_Canola | '''GSoC Project presentation: Picasa plugin for Canola''']] - ''Andrei Mirestean''
# [[/Lightning talks#Behaviour-Driven_Development_on_Maemo | '''Behaviour-Driven Development on Maemo''']] - ''Jose Teixeira''
# [[/Lightning_talks#N900_HW_architecture_overview_.26_power_management | '''N900 HW architecture overview & power management''']] - ''Igor Stoppa''
# [[/Lightning talks#From_corporations_to_communities:_responsible_and_effective_engagement | '''From corporations to communities: responsible and effective engagement''']] - ''Randall "Texrat" Arnold''
# [[/Lightning talks#Mer_from_a_user.27s_perspective | '''Mer from a user's perspective''']] - ''Tomasz Dominikowski'' - [http://www.slideshare.net/guest8106d9c/mer-from-users-perspective (Slides)]
# [[/Lightning talks#Nokia_PUSH_N900_Project_Showcase | '''Nokia PUSH N900 Project Showcase''']] - ''Ben Mason and Gary Birkett''
|-
| 15.30 - 16.00
| colspan="4" align="center" | Grand Finale
|}

== News ==
Link here Summit related news that made it to the homepage of recognized media.
* Made it to homepage of slideshare.net as Spotlight: Maemo Summit 2009, Amsterdam in the right navigation

== User-created content ==

===Tagged===

Please use the tag "maesum" (or hashtag "#maesum" on Identi.ca/Twitter) to tag your content.

Here are some helpful links to search for Maemo Summit content:

* [http://www.flickr.com/photos/tags/maesum/interesting/ maesum on Flickr]
* [http://picasaweb.google.com/lh/view?q=maesum&psc=G maesum on Picasa]
* [http://search.twitter.com/search?q=maesum maesum on Twitter]
* [http://identi.ca/tag/maesum maesum on Identi.ca]
* [http://www.youtube.com/results?search_query=+%22maesum%22 maesum on YouTube]
* [http://technorati.com/search/maesum maesum on Technorati]
* [http://www.slideshare.net/event/maemo-summit-2009 maesum on Slideshare]
* [http://vimeo.com/tag:maesum maesum on Vimeo]

===Blogs===

See [http://planet.maemo.org Planet Maemo] for some additional posts.

* [http://freebirdbr.wordpress.com/2009/10/12/maemo-summit-2009-dia-1/ Day 1], [http://freebirdbr.wordpress.com/2009/10/12/maemo-summit-2009-dia-2/ Day 2], [http://freebirdbr.wordpress.com/2009/10/13/maemo-summit-2009-dia-3/ Day 3] and two special posts on [http://freebirdbr.wordpress.com/2009/10/09/mitos-do-n900-n900-roda-mesmo-quake-iii/ Quake III on Maemo] and [http://freebirdbr.wordpress.com/2009/10/13/maemo-co-creation-workshop/ Co-creation workshop] at [http://freebirdbr.wordpress.com/2009/10/12/maemo-summit-2009-dia-1/ Free Bird] ('''''in portuguese'''''); automatic translations (by Google Translate) [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F12%2Fmaemo-summit-2009-dia-1%2F&sl=&tl=en Day 1], [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F12%2Fmaemo-summit-2009-dia-2%2F&sl=&tl=en Day 2], [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F13%2Fmaemo-summit-2009-dia-3%2F&sl=&tl=en Day 3], [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F09%2Fmitos-do-n900-n900-roda-mesmo-quake-iii%2F&sl=&tl=en Quake III on Maemo] and [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F13%2Fmaemo-co-creation-workshop%2F&sl=&tl=en Co-creation workshop]
* Live blogging at [http://maemotalk.com/ Maemo Talk]: [http://maemotalk.com/2009/10/09/maemo-summit-2009-day-1/ Day 1], [http://maemotalk.com/2009/10/10/maemo-summit-2009-day-2/ Day 2], [http://maemotalk.com/2009/10/11/maemo-summit-2009-day-3/ Day 3]
* [http://blog.bdesmet.be/?p=228 biertie's blogpost]
* Add a link to your blog post here

===Videos===

Please add videos that have been taken directly at the Summit (Talks, Interviews, etc..).

* [http://www.youtube.com/watch?v=n7a2Vz9msq4 Quake 3 Presentation]
* [http://www.youtube.com/watch?v=-xzD7UrrP9w Intro Video (N900 room, Friday morning)]
* [http://vimeo.com/7109463 Mer: how the community innovates]
* [http://vimeo.com/7059150 Summit Finale]
* Add a link to your video here

===Photos===

Please add links to your photos, either as a Flickr photoset, Picasa album or personal website.

* [http://www.flickr.com/photos/63684846@N00/sets/72157622451059219/ thp's photos on Flickr]
* [http://www.flickr.com/photos/43614522@N08/ rajesh lal's photos on Flickr]
* Add a link to your photos here

== Old ==

<div style="font-size: 1em;">
<div class="sections">
<div class="column">
<div class="section">
<h2>Schedule</h2>
<ul class="document">{{Summit 2009 Schedule}}
</ul></div>
<div class="section">
<h2>Location</h2>
<ul class="help">{{Summit 2009 Location}}
</ul></div>
<div class="section">
<h2>Attendees</h2>
<ul class="help">{{Summit 2009 Attendees}}</ul>
* [[Maemo_Summit_2009/Speakers|Information for Speakers]]
</div>
<div class="column">
<div class="section">
<h2>Organization</h2>
<ul class="help">{{Summit 2009 Organization}}
</ul></div>
</div></div>
</div>

=== Latest News ===
<rss title="off" desc="off" number="10" time="3600">http://search.twitter.com/search.rss?q=%23maesum</rss>

[[Category:Community|Mer]]

Maemo Summit 2009

2009-10-19T09:44:58Z

192.100.124.219: /* Saturday, October 10 */ added link to my slides

<div style="font-weight:bold;">October 9-10-11, 2009- [http://www.westergasfabriek.nl/english/engels_welcome.php WesterGasFabriek] - Amsterdam</div>
[[Image:Westergas.png‎]]

== Conference archive ==
Videos, slides and other materials related to the sessions. Feel free to update your own.

=== Thursday, October 8 ===

17:00 - 19:00 Registration at the Community Room (Zuiveringshal Oost). '''Early registrations encouraged to avoid queues and stress on Friday morning!'''

19:00 - 00:00 The official get together on Thursday will be [http://www.indewildeman.nl/indexe.html In de Wildeman], a beer house ([http://maps.google.nl/maps?f=q&source=s_q&hl=en&geocode=&q=Kolksteeg+3+1012+PT+Amsterdam&sll=52.377171,4.897242&sspn=0.005803,0.016512&ie=UTF8&hq=&hnear=Kolksteeg+3,+1012+Amsterdam,+North+Holland&t=h&z=16 Map]).

=== [[/Schedule/Day 1 | Friday, October 9]] ===

9:00 Registration at the Community Room (Zuiveringshal Oost). '''Come early: you won't get to the conference without your badge.'''

10:00 '''Programme starts at N900 (Transformatorhuis)'''

10:00 '''Welcome - Opening of Summit ''' by [http://maemo.org/profile/view/peterschneider.html Peter Schneider], Head of Maemo Marketing @ Nokia

10:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Maemo_5_and_the_N900 Maemo 5 and the Nokia N900] by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi], VP - Maemo Devices @ Nokia [http://www.slideshare.net/peterschneider/maemo-and-the-nokia-n900 (slides)]

11:00 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Changing_PC_.26_Mobile_Landscape.3B_Why_Linux_will_play_a_Critical_Role Changing PC & Mobile Landscape; Why Linux will play a Critical Role]''' by Jim Zemlin, Executive Director @ Linux Foundation

11:30 '''Break'''

11:45 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Nokia_Nseries_Devices_on_Maemo Nokia Nseries Devices on Maemo]''' by Jose-Luis Martinez Merino, VP, Marketing @ Nokia [http://www.slideshare.net/peterschneider/nokia-nseries-and-maemo-6 (slides)]

12:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Harmattan_Highlights_-_Developer_Opportunities Harmattan Highlights - Developer Opportunities]''' by Janne Heikkinen, Director - Maemo Product Planning @ Nokia [http://www.slideshare.net/peterschneider/maemo-5-developer-offering (Maemo 5 slides)] - [http://www.slideshare.net/peterschneider/maemo-6-technology-highlights (Maemo 6 slides)]

13:00 '''Lunch - Maemo Expo opens'''

14:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Why_the_Maemo_Community_matters_to_Nokia Why the Maemo Community matters to Nokia]''' - Alan "[http://maemo.org/profile/view/qole/ qole]" Bruce of [[Community Council|Maemo Community Council]] interviewing Ari Jaaksi, VP - Maemo Devices @ Nokia

15:00 '''Expert streams'''

{| class="wikitable" border="2"
|-
! Time
! N900 - ''chair: John Loughney''
! N810 - ''chair: Anthony Fabbricino''
! N800 - ''chair: Quim Gil''
|-

|-
| 15:00 - 15:25
| rowspan="2" | '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#UX_panel UX Panel]'''
''Moderated by: [http://maemo.org/profile/view/timsamoff Tim Samoff], Maemo Council,''
''with Harri Kiljander, Director Maemo UX Design and Martin Schüle, Principal Designer Maemo 5''
| '''UI design of Maemo 5 apps'''
''Annu-Maaria Nivala, UX team, Digia'' [http://www.slideshare.net/annumaaria/ui-design-of-maemo-5-apps-digia (slides)]
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Cross-platform_with_Qt_-_live Cross-platform with Qt - live]'''
''Ariya Hidayat, Software Engineer, Nokia''
|-
| 15:30 - 15:55
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Developing_widgets_on_Maemo_5_-_showcase_Foreca_Weather Developing widgets on Maemo 5 - showcase Foreca Weather]'''
''Juha Järvi, Software Designer, Foreca''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Mer_-_how_the_community_innovates Mer - how the community innovates]'''
''Carsten Munk, Lead Developer, Mer project'' [http://www.slideshare.net/carstenmunk/mer-how-the-community-innovates (slides)]
|-
| 16.00 - 16.25
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Firefox_on_Maemo Firefox on Maemo]'''
''Stuart Parmenter, Director of Engineering, Mozilla''

| '''Developing apps with Qt for Maemo5'''
''Kate Alhola, Forum Nokia, Chief Guru on Maemo
| | '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Your_foundation_for_open-source_innovation:_TI.E2.80.99s_OMAP_processor-based_Zoom_platform Your foundation for open-source innovation: TI’s OMAP processor-based Zoom platform]'''
''Ameet Suri, Texas Instruments''
|-
| 16.30 - 16.55
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Present_and_future_of_Maemo_digital_marketing Present andd future of Maemo digital marketing]'''
''Isko Salminen, Production Manager, Activeark & Jussi Mäkinen, Maemo Marketing, Nokia'''
| '''Developing apps with Qt on Harmattan'''
''Ville Lavonius, Product Manager Developer Offering, Nokia''
| '''Feedservice and plug-ins development in Maemo 5'''
''Mikko Levonmaa, Ixonos''
|-
| 17.00 - 17.25
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Biz_apps_on_Maemo Biz apps on Maemo]'''
''Kari Pikkarainen, Product Manager Productivity, Nokia''
| '''Developing apps with Nokia Web Runtime'''
''Santtu Ahonen, Head of Developer Offering, Nokia''
| '''[http://www.slideshare.net/jtukkine/maemo-6-harmattan-architecture-overview Harmattan Architecture Overview]'''
''Juha Tukkinen, Principal Engineer, Maemo Devices, Nokia''
|-
| 17.30 - 18.00
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Skype_on_Maemo Skype on Maemo]'''
''Mark Douglas, Mobile Product Manager, Skype''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Developer_Support_for_Maemo_by_Forum_Nokia Developer Support for Maemo by Forum Nokia]'''
''Matt Collins, Director, Forum Nokia Marketing''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Porting_an_OpenGL_game_to_GL_ES Porting an OpenGL game to GL ES]'''
''Oliver Mcfadden, Software Engineer, Nokia''
|-
|}

20:00 '''Maemo Party in FlexBar''' DJ's [http://valeriecherie.blogspot.com/2008/02/from-britain-with-love.html Russ Chimes] & [http://www.trashmenagerie.com/mixes/2008/04/01/grums-nllr-mixtape/ Grum] (check the mixtapes!) visuals by [http://www.xploitec.org/blog/?page_id=103 Xploitec VJ's]. coordinated by Jussi Mäkinen. It's a public bar and the doors are open to anybody. Our ''program'' will go until 23h or so, but the bar is open until really late with good music. Special cocktail hour sponsored by the lovely Skype people. Don't forget the Saturday schedule, though. :)

=== [[/Day 2 | Saturday, October 10]] ===

{| class="wikitable" border="2"
|-
! Time
! N900
! N810
! N800
! 770
|-
| align="right" | 9.00
| colspan="4" align="center" | Doors Open
|-
| 10.00 - 10.15
| colspan="4" align="center" | '''Welcome to Community days''' ''Maemo Community Council'' ([http://www.youtube.com/watch?v=6Mm-OS__8V0 Video])
|-
| 10.15 - 10:45
| colspan="4" align="center" | '''Keynote: Ton Roosendaal, the Blender Foundation'''
|-
| 10.45 - 11:00
| colspan="4" align="center" | Coffee-break
|-
| 11.00 - 11.25
| [[/Day 2#Designing_UI_for_Maemo_5 | '''Designing UI for Maemo 5''']] 
''Mox Soini'' ([http://www.slideshare.net/moximillian/soini-designing-ui-for-maemo-5 Slides])
| [[/Day 2#PyQt_application_development_on_Maemo | '''PyQt application development on Maemo''']] 
''Attila Csipa'' ([http://www.slideshare.net/guestb404461/pyqt-application-development-on-maemo Slides], [http://web.atombiztos.hu/pyqt_on_maemo.zip .odp with demo videos])
|rowspan="2" | [[/Day 2#Getting_started_session | '''Getting started session''']] ''Daniel Wilms and others''
| ------
|-
| 11.30 - 11.55
| [[/Day 2#Personalizing_your_Maemo_5_device | '''Personalizing your Maemo 5 device''']] ''Hartti Suomela''
| [[/Day 2#Canola_application_and_framework_for_rich_GUI | '''Canola application and framework for rich GUI''']] 
''Gustavo Sverzut Barbieri''
| ------
|-
| 12.00 - 12.25
| [[/Day 2#Modest.2C_email_client_for_Fremantle | '''Modest, email client for Fremantle''']] 
''Sergio Villar, Jose Dapena''
| [[/Day_2#Introducing_the_Harmattan_UI_framework | '''Introducing the Harmattan UI framework''']] 
''Tomas Junnonen''
| [[/Day 2#Maemomm:_Maemo_with_C.2B.2B_and_a_Gtkmm_flavour | '''Maemomm: Maemo with C++ and a Gtkmm flavour''']] 
''David King''
| rowspan="2" | [[/Day 2#Extras.2Fautobuilder.2Finterfaces_round-table | '''Extras/autobuilder/interfaces round-table''']]
|-
| 12.30 - 12.55
| [[/Day_2#Maemo_Co-creation | '''Maemo Co-Creation Showcase''']] 
''Jussi Mäkinen''
| [[/Day 2#Creating_packages_for_the_Maemo_platform | '''Creating packages for the Maemo platform''']] 
''Jeremiah Foster'' 
[http://www.slideshare.net/miahfost/packaging-for-the-maemo-platform (slides)]
| [[/Day 2#Developments_in_The_Qt_WebKit_Integration | '''Developments in The Qt WebKit Integration''']] 
''Kenneth Rohde Christiansen''
|-
| 13.00 - 14.30
| colspan="4" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="4" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Giving_Great_Presentations | '''Giving Great Presentations''']] - ''Dave Neary''
# [[/Lightning talks#Feedhandler_-_Integrating_RSS_newsreaders_with_the_browser | '''Feedhandler - Integrating RSS newsreaders with the browser''']] - ''Thomas Perl''
# [[/Lightning talks#python-mafw:_MAFW_framework_for_Python_developers | '''python-mafw: MAFW framework for Python developers''']] - ''Andrea Grandi'' - [http://www.slideshare.net/andy80/pythonmafw-intoduction-at-maemo-summit-2009 (Slides)]
# [[/Lightning talks#DVCS.3F_git.3F_-_How_does_that_work_then.3F | '''DVCS? git? - How does that work then?''']] - ''David Greaves'' - [http://www.slideshare.net/mrlbt/git-how-does-that-work-then (Slides)]
# [[/Lightning_talks#BlueMaemo_-_Bluetooth_HID_mouse_.26_keyboard_for_Maemo | '''BlueMaemo - Bluetooth HID mouse & keyboard for Maemo''']] - ''Valério Valério'' [http://www.slideshare.net/VDVsx/bluemaemo-bluetooth-hid-mouse-keyboard-for-maemo (Slides)]
# [[/Lightning_talks#Continous_Integration_with_CruiseControl_and_Scratchbox | '''Continous Integration with CruiseControl and Scratchbox''']] - ''Jani Mikkonen'' [http://www.slideshare.net/rasjani/continuous-integration-with-scratchbox-and-cruisecontrol (Slides)]
# [[/Lightning_talks#Conboy.2C_Tomboy_and_Snowy | '''Conboy, Tomboy and Snowy''']] - ''Cornelius Hald''
# [[/Lightning_talks#Ogg_support_status | '''Ogg support status''']] - ''Tuomas Kulve''
# [[/Lightning_talks#Maemo_Platform_Security | '''Maemo Platform Security''']] - ''Elena Reshetova''
|-
| 15:25 - 15:45
| colspan="4" align="center" | Break
|-
| 15.45 - 16.10
| [[/Day 2#GUPnP_and_Rygel:_The_UPnP.2FDLNA_solution_for_Maemo | '''GUPnP and Rygel: The UPnP/DLNA solution for Maemo''']] 
''Zeeshan Ali''
| [[/Day 2#Adapting_GNOME_applications_to_Maemo_Fremantle | '''Adapting GNOME applications to Maemo Fremantle''']] 
''Joaquim Rocha'' [http://www.slideshare.net/j_rocha/adapting-gnome-applications-to-maemo-fremantle (slides)]
| [[/Day 2#Contributing_with_Git_.26_Gitorious | '''Contributing with Git & Gitorious''']] Johan Sørensen
| [[/Day_2#High-resolution_image_processing_on_Maemo_devices | '''High-resolution image processing on Maemo devices''']] 
''Alexander Bokovoy''
|-
| 16.15 - 16.40
| [[/Day 2#Mer:_A_year_after| '''Mer: A year after''']] 
''Carsten Valdemar Munk'' [http://www.slideshare.net/carstenmunk/mer-a-year-after (slides)]
| [[/Day_2#Intelligent_Usage_of_Fremantle_Location_Framework_For_Location-aware_Applications | '''Intelligent Usage of Fremantle Location Framework For Location-aware Applications''']] 
''Quanyi Sun''
| [[/Day 2#Hildon_toolkit_for_Fremantle | '''Hildon toolkit for Fremantle''']] 
''Alberto Garcia, Claudio Saavedra''
| rowspan="2" | [[/Day_2#Git_hands-on_workshop | '''Git hands-on workshop''']] 
''David Greaves''
|-
| 16.45 - 17.10
| [[/Day 2#maemo.org_Bug_Management | '''maemo.org Bug Management''']] 
''Andre Klapper'' [http://home.arcor.de/ak-47/en/linux/maemosummit2009.pdf (slides)]
| [[/Day 2#Go-to_market_opportunities_for_mobile_application_developers | '''Go-to market opportunities for mobile application developers''']] 
''Boaz Zilberman''
| [[/Day_2#Tracker:_Dial_M_for_Metadata | '''Tracker: Dial M for Metadata''']] 
''Ivan Frade, Iridian Kiiskinen''
|-
| 17.10 - 17.30
| colspan="4" align="center" | Break
|-
| 17.30 - 17.55
| [[/Day 2#Canola:_Beyond_the_media_playback | '''Canola: Beyond the media playback''']] ''Eduardo Lima''
| [[/Day 2#Hands-on_development_with_Nokia_Web_Runtime | '''Hands-on development with Nokia Web Runtime''']] 
''Oren Levine'' [http://www.slideshare.net/olevine/handson-development-with-nokia-web-runtime (Slides)] [http://www.forum.nokia.com/Technology_Topics/Web_Technologies/Web_Runtime/ (More information)]
| [[/Day 2#The_Qt_Mobility_Project | '''The Qt Mobility Project''']] ''Alex Luddy''
| [[/Day_2#Hacking_officially_unsupported_Bluetooth_profiles_to_work_in_Fremantle | '''Hacking officially unsupported Bluetooth profiles to work in Fremantle''']] 
''Johan Hedberg''
|-
| 18.00 - 18.25
| [[/Day_2#The_Maemo_5_Address_Book | '''The Maemo 5 Address Book''']] 
''Mathias Hasselmann, Travis Reiter''
| [[/Day 2#Publishing_your_software_through_maemo.org | '''Publishing your software through maemo.org''']] ''Niels Breet''
| [[/Day_2#Maemo_and_oFono | '''Maemo and oFono''']] 
''Aki Niemi, Rémi Denis-Courmont''
| [[/Day_2#The_future_of_GTK.2B.2FHildon_in_Maemo_Harmattan | '''The future of GTK+/Hildon in Maemo Harmattan''']] 
''Alberto Garcia, Claudio Saavedra''
|-
| 18.45 - 20.30
| colspan="4" align="center" | Maemo Drinks in N900 room
|}

=== [[/Day 3 | Sunday, October 11]] ===

{| class="wikitable" border="2"
|-
! Time
! N900
! N810
! N800
! 770
|-
| align="right" | 9.00
| colspan="4" align="center" | Doors Open
|-
| 10.00 - 10.45
| colspan="4" align="center" | [[/Day 3#Fremantle_Stars_showcase | '''Fremantle Stars showcase''']] Including liqbase, OSM2Go, [http://mauku.innologies.com Mauku], OMWeather [http://www.slideshare.net/vasvlad/omweather-in-maemo-summit-2009 (Slides+notes)], eCoach and more.
|-
| 10.45 - 11.00
| colspan="4" align="center" | Coffee-break
|-
| 11.00 - 11.25
| [[/Day 3#Maemo_Browser_for_power_users | '''Maemo Browser for power users''']] ''Mikko Korpelainen'' - [http://www.slideshare.net/mtkorpel/maemo-browser (presentation content)]
 [[/Day 3#Maemo_Browser_evolution | ''Maemo Browser evolution'']] ''Oleg Romashin''
 
 [[/Day 3#Maemo_Browser_extension_development | ''Maemo Browser extension development'']] ''Sudarsana Nagineni''

| [[/Day 3#JamMo_-_Jamming_mobile_game_for_children | '''JamMo - Jamming mobile game for children''']] 
''Aapo Rantalainen''
| [[/Day_3#Building_for_Mer | '''Building for Mer''']] ''David Greaves'' - [http://www.slideshare.net/mrlbt/building-for-mer (Slides+notes)] [[Mer/Build | (see also Mer Build page)]]
| rowspan="2" | [[/Day 3#Hackathon:_Integrating_Canola_with_Fremantle | '''Canola Fremantle Hackathon''']]
|-
| 11.30 - 11.55
| [[/Day 3#Maemo_documentation_co-creation | '''Maemo documentation co-creation ''']] 
''Dave Neary''
| [[/Day_3#Designing_QT_application_for_Maemo_5_and_Maemo_6 | '''Designing Qt application for Maemo 5 and Maemo 6''']] ''Sergiy Dubovik, Ian Monroe''
| [[/Day 3#Writing_plugins_for_MAFW | '''Writing plugins for MAFW ''']] ''Iago Toral'' [http://blogs.igalia.com/itoral/2009/10/11/writing-mafw-plugins-talk-maemo-summit/ (blog post with slides and source code examples)]
|-
| 12.00 - 12.25
| [[/Day_3#Mobile_Office_based_on_KOffice_Open_Source_Project | '''Mobile Office based on KOffice Open Source Project''']] 
''Suresh Chande'' [http://sureshchande.blogspot.com/2009/10/mobile-office-based-on-koffice-for.html (blog post + video demo)]
| [[/Day 3#Handheld_Glom:_Easy_database_applications | '''Handheld Glom: Easy database applications''']] 
''Murray Cumming''
| [[/Day_3#Maemo_Platform_Security:_Principles_and_Concepts | '''Maemo Platform Security: Principles and Concepts''']] 
''Elena Reshetova''
|[[/Day_3#Extending_the_Hildon_desktop | '''Extending the Hildon desktop ''']] 
''Marc Ordinas i Llopis''
|-
| 12.30 - 12.55
| [[/Day 3#Towards_painless_and_quality_translations | '''Towards painless and quality translations''']] Dimitris Glezos ([http://media.indifex.com/other/maesum.pdf slides])
| [[/Day_3#10_Tips_for_Designing_Mobile_Widgets | '''10 Tips for Designing Mobile Widgets''']] 
''Rajesh Lal'' ([http://www.slideshare.net/rajeshlal/ten-tips-for-designing-mobile-widgets-2009-q3-maemo-summit-v1 slideshare], [http://irajesh.com/files/10TipsForDesigningMobileWidgets.pdf pdf], [http://irajesh.com/files/10TipsForDesigningMobileWidgets.ppt ppt], [http://irajesh.com/files/10TipsForDesigningMobileWidgets.pps pps])
| [[/Day_3#Telepathy_on_Maemo | '''Telepathy on Maemo''']] 
''Marco Barisione''
| [[/Day_3#What_to_do_about_.2Fopt_in_Fremantle | '''What to do about /opt in Fremantle''']] 
''Marius Vollmer''
|-
| 13.00 - 14.30
| colspan="4" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="4" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Issues_on_adapting_Maemo_4_application_to_Maemo_5 | '''Issues on adapting Maemo 4 application to Maemo 5''']] - ''Aniello del Sorbo'' - [http://www.slideshare.net/anidel/issues-on-adapting-maemo-4-applications-to-maemo-5-2229255 (Slides)]
# [[/Lightning talks#How_to_speed_up_your_Maemo_application_development | '''How to speed up your Maemo application development''']] - ''Raul Herbster''
# [[/Lightning talks#Development_Nirvana:_How_Maemo_Application_Development_Should_Be | '''Development Nirvana: How Maemo Application Development Should Be''']] - ''Andrew Flegg''
# [[/Lightning talks#GSoC_presentation:_BitTorrent_plugin_for_Canola | '''GSoC presentation: BitTorrent plugin for Canola''']] - ''Lauri Võsandi''
# [[/Lightning talks#GSoC_Project_presentation:_Picasa_plugin_for_Canola | '''GSoC Project presentation: Picasa plugin for Canola''']] - ''Andrei Mirestean''
# [[/Lightning talks#Behaviour-Driven_Development_on_Maemo | '''Behaviour-Driven Development on Maemo''']] - ''Jose Teixeira''
# [[/Lightning_talks#N900_HW_architecture_overview_.26_power_management | '''N900 HW architecture overview & power management''']] - ''Igor Stoppa''
# [[/Lightning talks#From_corporations_to_communities:_responsible_and_effective_engagement | '''From corporations to communities: responsible and effective engagement''']] - ''Randall "Texrat" Arnold''
# [[/Lightning talks#Mer_from_a_user.27s_perspective | '''Mer from a user's perspective''']] - ''Tomasz Dominikowski'' - [http://www.slideshare.net/guest8106d9c/mer-from-users-perspective (Slides)]
# [[/Lightning talks#Nokia_PUSH_N900_Project_Showcase | '''Nokia PUSH N900 Project Showcase''']] - ''Ben Mason and Gary Birkett''
|-
| 15.30 - 16.00
| colspan="4" align="center" | Grand Finale
|}

== News ==
Link here Summit related news that made it to the homepage of recognized media.
* Made it to homepage of slideshare.net as Spotlight: Maemo Summit 2009, Amsterdam in the right navigation

== User-created content ==

===Tagged===

Please use the tag "maesum" (or hashtag "#maesum" on Identi.ca/Twitter) to tag your content.

Here are some helpful links to search for Maemo Summit content:

* [http://www.flickr.com/photos/tags/maesum/interesting/ maesum on Flickr]
* [http://picasaweb.google.com/lh/view?q=maesum&psc=G maesum on Picasa]
* [http://search.twitter.com/search?q=maesum maesum on Twitter]
* [http://identi.ca/tag/maesum maesum on Identi.ca]
* [http://www.youtube.com/results?search_query=+%22maesum%22 maesum on YouTube]
* [http://technorati.com/search/maesum maesum on Technorati]
* [http://www.slideshare.net/event/maemo-summit-2009 maesum on Slideshare]
* [http://vimeo.com/tag:maesum maesum on Vimeo]

===Blogs===

See [http://planet.maemo.org Planet Maemo] for some additional posts.

* [http://freebirdbr.wordpress.com/2009/10/12/maemo-summit-2009-dia-1/ Day 1], [http://freebirdbr.wordpress.com/2009/10/12/maemo-summit-2009-dia-2/ Day 2], [http://freebirdbr.wordpress.com/2009/10/13/maemo-summit-2009-dia-3/ Day 3] and two special posts on [http://freebirdbr.wordpress.com/2009/10/09/mitos-do-n900-n900-roda-mesmo-quake-iii/ Quake III on Maemo] and [http://freebirdbr.wordpress.com/2009/10/13/maemo-co-creation-workshop/ Co-creation workshop] at [http://freebirdbr.wordpress.com/2009/10/12/maemo-summit-2009-dia-1/ Free Bird] ('''''in portuguese'''''); automatic translations (by Google Translate) [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F12%2Fmaemo-summit-2009-dia-1%2F&sl=&tl=en Day 1], [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F12%2Fmaemo-summit-2009-dia-2%2F&sl=&tl=en Day 2], [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F13%2Fmaemo-summit-2009-dia-3%2F&sl=&tl=en Day 3], [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F09%2Fmitos-do-n900-n900-roda-mesmo-quake-iii%2F&sl=&tl=en Quake III on Maemo] and [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F13%2Fmaemo-co-creation-workshop%2F&sl=&tl=en Co-creation workshop]
* Live blogging at [http://maemotalk.com/ Maemo Talk]: [http://maemotalk.com/2009/10/09/maemo-summit-2009-day-1/ Day 1], [http://maemotalk.com/2009/10/10/maemo-summit-2009-day-2/ Day 2], [http://maemotalk.com/2009/10/11/maemo-summit-2009-day-3/ Day 3]
* [http://blog.bdesmet.be/?p=228 biertie's blogpost]
* Add a link to your blog post here

===Videos===

Please add videos that have been taken directly at the Summit (Talks, Interviews, etc..).

* [http://www.youtube.com/watch?v=n7a2Vz9msq4 Quake 3 Presentation]
* [http://www.youtube.com/watch?v=-xzD7UrrP9w Intro Video (N900 room, Friday morning)]
* [http://vimeo.com/7109463 Mer: how the community innovates]
* [http://vimeo.com/7059150 Summit Finale]
* Add a link to your video here

===Photos===

Please add links to your photos, either as a Flickr photoset, Picasa album or personal website.

* [http://www.flickr.com/photos/63684846@N00/sets/72157622451059219/ thp's photos on Flickr]
* [http://www.flickr.com/photos/43614522@N08/ rajesh lal's photos on Flickr]
* Add a link to your photos here

== Old ==

<div style="font-size: 1em;">
<div class="sections">
<div class="column">
<div class="section">
<h2>Schedule</h2>
<ul class="document">{{Summit 2009 Schedule}}
</ul></div>
<div class="section">
<h2>Location</h2>
<ul class="help">{{Summit 2009 Location}}
</ul></div>
<div class="section">
<h2>Attendees</h2>
<ul class="help">{{Summit 2009 Attendees}}</ul>
* [[Maemo_Summit_2009/Speakers|Information for Speakers]]
</div>
<div class="column">
<div class="section">
<h2>Organization</h2>
<ul class="help">{{Summit 2009 Organization}}
</ul></div>
</div></div>
</div>

=== Latest News ===
<rss title="off" desc="off" number="10" time="3600">http://search.twitter.com/search.rss?q=%23maesum</rss>

[[Category:Community|Mer]]

Maemo.org Sprints/October 09

2009-10-19T04:29:17Z

192.100.124.219: /* Tasks */

== October 2009 Sprint planning ==

* Planning meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?month=10&day=6&year=2009&hour=13&min=30&sec=0 Tuesday, 6th October 13:30 UTC] in [[IRC|#maemo-meeting]].
* Follows [[maemo.org Sprints/September 09|September 09]]. Precedes [[maemo.org Sprints/November 09|November 09]].
* Main themes: New council; summit

== Tasks ==
[[:Category:Ongoing|Ongoing]] tasks carried here from the previous sprint + New tasks committed by their owners in the sprint meeting. They come from the tasks in the [[Maemo.org_backlog|Backlog]] and the [[Maemo.org_proposals|Proposals]].

{| class="wikitable"
| style="background:LightGreen" | Completed
| style="background:LightBlue" | Good progress
| Just standing
| style="background:Orange" | Some help needed!
| style="background:Tomato" | Really stuck/delayed
|}

{| class="wikitable sortable"
|-
! Task ID
! Task
! Sprint priority
! Owner
! Percentage complete
! Notes
|- style="background:Orange"
| 9.04-05
| [[Task:Implement new maemo.org layout and style|Implement new maemo.org layout and style - Bugzilla]]
| Must
| [http://maemo.org/profile/view/andre/ Andre]
| 80%
|
|- style=""
| 9.04-08
| [[ITP]] process/workflow around [http://test.maemo.org/cgi-bin/itp.cgi prototype]
| Must
| [http://maemo.org/profile/view/jeremiah/ Jeremiah]
| 90%
|
|- style=""
| 9.08-04
| Integrate [http://wiki.maemo.org/Extras-testing#Maemian.2FMinimae_checks_after_builds minimae] into package promotion to get infrastructure & UI in place
| Must
| [http://maemo.org/profile/view/jeremiah/ Jeremiah]
| 90%
|
|- style=""
| 9.08-11
| Document & communicate packages interface to testers
| Must
| [http://maemo.org/profile/view/jaffa/ Jaffa]
| 0%
| Not done.
|- style=""
| 9.09-01
| Push packaging policy updates
| Must
| [http://maemo.org/profile/view/xfade/ X-Fade], [http://maemo.org/profile/view/danielwilms/ danielwilms]
| 40%
| Make some changes, waiting for Daniel to pass it to Nokia internal team.
|- style=""
| 9.10-01
| Discuss [[Token_based_access_restriction | Token based access restriction]] at Summit
| Must
| [http://maemo.org/profile/view/stskeeps/ Stskeeps], [http://maemo.org/profile/view/xfade/ X-Fade]
| 0%
|
|- style="background:LightGreen"
| 9.10-02
| Define docmaster priorities
| Must
| [http://maemo.org/profile/view/dneary/ dneary]
| DONE
| Done as part of preparation for summit, and discussions before, during & after summit. First big job: Getting the [[Maemowiki Action Group]] working effectively.
|- style=""
| 9.10-03
| Implement SSO backend
| Must
| [http://maemo.org/profile/view/indeyets/ indeyets]
| 0%
|
|- style=""
| 9.10-04
| Brainstorm: bug fixes and new features
| Must
| [http://maemo.org/profile/view/netblade/ NetBlade]
| 0%
| [https://bugs.maemo.org/show_bug.cgi?id=5282 Related bug]
|- style=""
| 9.10-05
| Brainstorm: better categories view
| Must
| [http://maemo.org/profile/view/netblade/ NetBlade]
| 0%
|
|- style=""
| 9.10-06
| Brainstorm: automoderation from sandbox to under consideration
| Must
| [http://maemo.org/profile/view/netblade/ NetBlade]
| 0%
|
|- style=""
| 9.10-07
| Server migration
| Must
| [http://maemo.org/profile/view/feri/ Ferenc]
| 0%
|
|- style=""
| 9.10-08
| Maemo Summit council meeting agenda
| Must
| new & old council & maemo.org staff
| 0%
|
|- style=""
| 9.08-10
| Draft [http://wiki.maemo.org/Extras_repository_process_definition#Quality_Assurance quality guidelines] for extras-testing to extras promotion
| Should
| [http://maemo.org/profile/view/qgil/ qgil]
| 10%
| Drafting at [[Extras-testing#Quality_criteria|Extras-testing Quality_criteria]] + [http://talk.maemo.org/showthread.php?t=30541 tmo discussion].
|- style=""
| 9.10-09
| Prototype [[Task:Publishing_API_docs | library.maemo.org]]
| Should
| [http://maemo.org/profile/view/dneary/ dneary]
| 0%
|
|- style="background:LightGreen"
| 9.06-14
| Plan for the OMAP2 acceleration [[Drivers justification|drivers]]
| Could
| [http://maemo.org/profile/view/qgil/ qgil]
| DONE
| My part has been done after TI's commitment to release the drivers announced in the maemo Summit.
|- style=""
| 9.08-12
| Improve reporting feed appearance on sprint page
| Could
| [http://maemo.org/profile/view/feri/ Ferenc]
| 0%
| To liaise with [http://maemo.org/profile/view/jaffa/ Jaffa]
|- style=""
| 9.09-10
| Implement SSO sync-API endpoint for garage
| Could
| [http://maemo.org/profile/view/danielwilms/ danielwilms]
| 0%
|
|- style=""
| 9.10-10
| Add extra info fields from control files to interface - Changelog
| Could
| [http://maemo.org/profile/view/xfade/ X-Fade]
| 0%
|
|}

== Actions ==
''None yet''

== Activity log ==
Latest activity report goes on top. Activity will be reported here, [http://www.qaiku.com/channels/show/maemork/ Qaiku #maemork channel] ([http://www.qaiku.com/feeds/channels/maemork Atom feed]) or talk.maemo.org.

<rss title="off" desc="off" number="40" time="3600">http://pipes.yahoo.com/pipes/pipe.run?_id=mvdCJrB_3hGfIDijIDfpSg&_render=rss</rss>

[[Category:Community]]
[[Category:maemo.org]]

Talk:Maemo security

2009-10-15T08:43:22Z

192.100.124.219: /* Can network operators restrict you switching to Open mode? */

Suggested questions:

===Is there a diagram showing the security framework and components?===
There were some diagrams in the presentation - can we see them.

Elena Reshetova: The presentation was uploaded, and currently it is the only information, which I can share.

===What is "Open Mode" and can it be revoked remotely?===
Is that the right terminology?
Essentially can Nokia reach out the the 2nd stage bootloader and tell it to stop running unsigned kernels.
Maybe this should be 2 questions.

===What does closed mode restrict you from doing?===

* Terminal?
* Root?
** If the [http://aegis.sf.net Aegis AC] is used for the protected storage then root is probably disabled.

** I don't think this Aegis has anything to do with Maemo

Elena Reshetova: We don't have any connection to the Aegis Project, mentioned above. This is a collision of names, I am sorry about it.
In general "close" mode has its own security policy, which user won't be able to change.

* Cellular is marked as a protected ressource in the slide. Can one still use it (phone, data, sms etc.) while running in open mode? While runnin a rebuilt kernel?

Elena Reshetova: If you use your own kernel, you are the one to set the security policy for the device, meaning that your SW in this case can make calls, send sms and so on (for example). Please note that the list of protected resources on the slide is given just as example (to show the possible granularity level), so it doesn't mean that we would have exactly these resources.

===How easy is it to switch between Open and Closed modes?===

Is it so trivial that you would want to and be able to do it several times a day and on the go (without restart)?

Elena Reshetova: I should be able to tell the exact procedure in the future, but for now I can say that it won't be so trivial (like press the GUI button :-)), and the restart is needed. The checks for the SW image are done by the Loader, and during the boot time, so you do need to restart.

===Can network operators restrict you switching to Open mode?===
Like if a device is sim-locked to a particular network, does the device get locked down in closed DRM mode only too? Can you always switch to open mode?

Elena Reshetova: If the device is SIM-locked, operator can restrict you to the usage of one particular kernel (slide 5), for example the one, which was shipped with a device. However, it is up to you to decide to buy the device from the operator or form the Nokia store.

===How granular is the encryption?===
If my app creates content in the closed mode can I see it in open mode?

Elena Reshetova: If your application uses the Protected Storage for encryption (slide 8) in the initial mode, and after you switch to another mode, the application won't be able to get decrypted data. If your application just stores the data in the filesystem, after switching to your own kernel, you will be able to access the data (because they are just plain files in the filesystem).

===Can open applications use the privilege mechanisms in the Open and Closed modes?===

Elena Reshetova: I guess the question is "Can the applications access protected resources in both modes?" I hope I got the question correctly. The answer is that the Device Security Policy (slide 7) defines the resources can be potentially granted to the SW coming from a particular SW source. When one uses the Nokia signed kernel, the device security policy is defined, and user can't change it. If one uses its own kernel (or community kernel for example), he (or community) is the one to define/change the device policy. This means that one can, for example, change the policy in the way that the SW coming from the maemo.org gets access to all protected resources (of course some content becomes unavailable when one switch to its own kernel, for example DRM). However, again, it is possible only while using your own kernel.

===Can open applications use the DRM encryption mechanisms in the Open and Closed modes?===
I can see that this could be useful. Maybe.

===Will community extensions to the kernel (modules) be permitted in Open/Closed modes?===
I can't see how - which leads to the question: How do community 'enhancements' to the kernel get adopted?

Elena Reshetova: In the "Open" mode any changes of the kernel are allowed. Regarding the "closed" mode, unfortunately I am not the right person to answer this question.

===Is there any GPLv3 software impacted?===
Please have a license discussion somewhere and let us know when you have consensus.
What is Nokias position? Peter made a statement at the talk - can someone transcribe it and/or get Nokia to clarify.

===What exactly is available to the end user?===

* storage encryption ?
* PIM data encryption ?
* encrypted/signed communications (phone, sms/mms, mails, IM) ?

=== How does closed mode affect on-device debugging? ===

For example, will ptrace(2) still work (eg gdb, strace & ltrace)? Will we be able to produce code dumps?

===Will DRM-free data and DRM-free applications be accessible from both modes once they're installed/created in either of the two modes?===

E.g.: I start in DRM-mode, install DRM-free applications from Extras, take 3 pictures, add some contacts. Then I switch to DRM-free mode: Will I be able to run the applications installed in DRM-free mode, view and edit my contacts and view and edit my own pictures? (And the other way round, of course, starting from DRM-free mode and switching to DRM afterwards.)

===What is open mode good for at all?===

Provided you don't consume digitally restricted media and don't purchase applications that in any way rely on DRM: You don't need DRM-mode then, but on the other hand why would you want DRM-free mode? What is it you cannot do in DRM-mode in such a scenario? Use case?

===What is ARM's TrustZone?===
The official ARM TrustZone page:
http://www.arm.com/products/security/trustzone/index.html

===Can the Trusted Execution Environment (TrEE) be used as a kill switch for the device even if it runs in open mode?===

== Maintaining the discussion ==

On the [http://talk.maemo.org/showthread.php?p=344427#post344427 talk.maemo.org thread], I suggest that end-users are kept at arms' length from this page and we use it as a proper communication mechanism between the community and Elena et al. --[[User:jaffa|Jaffa]] 10:43, 13 October 2009 (UTC)

More discussion in the [http://mg.pov.lt/maemo-irclog/%23maemo.2009-10-11.log.html#t2009-10-11T12:50:36 #maemo chat] which was going on concurrently with the talk and a [http://www.flickr.com/photos/30863507@N02/4007518495/ few] [http://www.flickr.com/photos/30863507@N02/4008286892/ flickr] [http://www.flickr.com/photos/30863507@N02/4007522767/ photos]. --[[User:jaffa|Jaffa]] 11:20, 13 October 2009 (UTC)

Talk:Maemo security

2009-10-15T08:06:35Z

192.100.124.219: /* Will community extensions to the kernel (modules) be permitted in Open/Closed modes? */

Suggested questions:

===Is there a diagram showing the security framework and components?===
There were some diagrams in the presentation - can we see them.

Elena Reshetova: The presentation was uploaded, and currently it is the only information, which I can share.

===What is "Open Mode" and can it be revoked remotely?===
Is that the right terminology?
Essentially can Nokia reach out the the 2nd stage bootloader and tell it to stop running unsigned kernels.
Maybe this should be 2 questions.

===What does closed mode restrict you from doing?===

* Terminal?
* Root?
** If the [http://aegis.sf.net Aegis AC] is used for the protected storage then root is probably disabled.

** I don't think this Aegis has anything to do with Maemo

Elena Reshetova: We don't have any connection to the Aegis Project, mentioned above. This is a collision of names, I am sorry about it.
In general "close" mode has its own security policy, which user won't be able to change.

* Cellular is marked as a protected ressource in the slide. Can one still use it (phone, data, sms etc.) while running in open mode? While runnin a rebuilt kernel?

Elena Reshetova: If you use your own kernel, you are the one to set the security policy for the device, meaning that your SW in this case can make calls, send sms and so on (for example). Please note that the list of protected resources on the slide is given just as example (to show the possible granularity level), so it doesn't mean that we would have exactly these resources.

===How easy is it to switch between Open and Closed modes?===

Is it so trivial that you would want to and be able to do it several times a day and on the go (without restart)?

Elena Reshetova: I should be able to tell the exact procedure in the future, but for now I can say that it won't be so trivial (like press the GUI button :-)), and the restart is needed. The checks for the SW image are done by the Loader, and during the boot time, so you do need to restart.

===Can network operators restrict you switching to Open mode?===
Like if a device is sim-locked to a particular network, does the device get locked down in closed DRM mode only too? Can you always switch to open mode?

Elena Reshetova: If device is SIM-locked (slide 5 of the presentation), you aren't allowed to use your own kernel. The only kernel, which will be allowed, is the kernel, which is shipped with the device, when you buy it from the operator. The reasons for this are simple, and I hope understandable: if we allowed to change the kernel, we can't be sure about security of the SIM-lock. Moreover, it is your choice to buy the device from the operator or from Nokia stores.

===How granular is the encryption?===
If my app creates content in the closed mode can I see it in open mode?

Elena Reshetova: If your application uses the Protected Storage for encryption (slide 8) in the initial mode, and after you switch to another mode, the application won't be able to get decrypted data. If your application just stores the data in the filesystem, after switching to your own kernel, you will be able to access the data (because they are just plain files in the filesystem).

===Can open applications use the privilege mechanisms in the Open and Closed modes?===

Elena Reshetova: I guess the question is "Can the applications access protected resources in both modes?" I hope I got the question correctly. The answer is that the Device Security Policy (slide 7) defines the resources can be potentially granted to the SW coming from a particular SW source. When one uses the Nokia signed kernel, the device security policy is defined, and user can't change it. If one uses its own kernel (or community kernel for example), he (or community) is the one to define/change the device policy. This means that one can, for example, change the policy in the way that the SW coming from the maemo.org gets access to all protected resources (of course some content becomes unavailable when one switch to its own kernel, for example DRM). However, again, it is possible only while using your own kernel.

===Can open applications use the DRM encryption mechanisms in the Open and Closed modes?===
I can see that this could be useful. Maybe.

===Will community extensions to the kernel (modules) be permitted in Open/Closed modes?===
I can't see how - which leads to the question: How do community 'enhancements' to the kernel get adopted?

Elena Reshetova: In the "Open" mode any changes of the kernel are allowed. Regarding the "closed" mode, unfortunately I am not the right person to answer this question.

===Is there any GPLv3 software impacted?===
Please have a license discussion somewhere and let us know when you have consensus.
What is Nokias position? Peter made a statement at the talk - can someone transcribe it and/or get Nokia to clarify.

===What exactly is available to the end user?===

* storage encryption ?
* PIM data encryption ?
* encrypted/signed communications (phone, sms/mms, mails, IM) ?

=== How does closed mode affect on-device debugging? ===

For example, will ptrace(2) still work (eg gdb, strace & ltrace)? Will we be able to produce code dumps?

===Will DRM-free data and DRM-free applications be accessible from both modes once they're installed/created in either of the two modes?===

E.g.: I start in DRM-mode, install DRM-free applications from Extras, take 3 pictures, add some contacts. Then I switch to DRM-free mode: Will I be able to run the applications installed in DRM-free mode, view and edit my contacts and view and edit my own pictures? (And the other way round, of course, starting from DRM-free mode and switching to DRM afterwards.)

===What is open mode good for at all?===

Provided you don't consume digitally restricted media and don't purchase applications that in any way rely on DRM: You don't need DRM-mode then, but on the other hand why would you want DRM-free mode? What is it you cannot do in DRM-mode in such a scenario? Use case?

===What is ARM's TrustZone?===
The official ARM TrustZone page:
http://www.arm.com/products/security/trustzone/index.html

===Can the Trusted Execution Environment (TrEE) be used as a kill switch for the device even if it runs in open mode?===

== Maintaining the discussion ==

On the [http://talk.maemo.org/showthread.php?p=344427#post344427 talk.maemo.org thread], I suggest that end-users are kept at arms' length from this page and we use it as a proper communication mechanism between the community and Elena et al. --[[User:jaffa|Jaffa]] 10:43, 13 October 2009 (UTC)

More discussion in the [http://mg.pov.lt/maemo-irclog/%23maemo.2009-10-11.log.html#t2009-10-11T12:50:36 #maemo chat] which was going on concurrently with the talk and a [http://www.flickr.com/photos/30863507@N02/4007518495/ few] [http://www.flickr.com/photos/30863507@N02/4008286892/ flickr] [http://www.flickr.com/photos/30863507@N02/4007522767/ photos]. --[[User:jaffa|Jaffa]] 11:20, 13 October 2009 (UTC)

Talk:Maemo security

2009-10-15T07:53:06Z

192.100.124.219: /* Can open applications use the privilege mechanisms in the Open and Closed modes? */

Suggested questions:

===Is there a diagram showing the security framework and components?===
There were some diagrams in the presentation - can we see them.

Elena Reshetova: The presentation was uploaded, and currently it is the only information, which I can share.

===What is "Open Mode" and can it be revoked remotely?===
Is that the right terminology?
Essentially can Nokia reach out the the 2nd stage bootloader and tell it to stop running unsigned kernels.
Maybe this should be 2 questions.

===What does closed mode restrict you from doing?===

* Terminal?
* Root?
** If the [http://aegis.sf.net Aegis AC] is used for the protected storage then root is probably disabled.

** I don't think this Aegis has anything to do with Maemo

Elena Reshetova: We don't have any connection to the Aegis Project, mentioned above. This is a collision of names, I am sorry about it.
In general "close" mode has its own security policy, which user won't be able to change.

* Cellular is marked as a protected ressource in the slide. Can one still use it (phone, data, sms etc.) while running in open mode? While runnin a rebuilt kernel?

Elena Reshetova: If you use your own kernel, you are the one to set the security policy for the device, meaning that your SW in this case can make calls, send sms and so on (for example). Please note that the list of protected resources on the slide is given just as example (to show the possible granularity level), so it doesn't mean that we would have exactly these resources.

===How easy is it to switch between Open and Closed modes?===

Is it so trivial that you would want to and be able to do it several times a day and on the go (without restart)?

Elena Reshetova: I should be able to tell the exact procedure in the future, but for now I can say that it won't be so trivial (like press the GUI button :-)), and the restart is needed. The checks for the SW image are done by the Loader, and during the boot time, so you do need to restart.

===Can network operators restrict you switching to Open mode?===
Like if a device is sim-locked to a particular network, does the device get locked down in closed DRM mode only too? Can you always switch to open mode?

Elena Reshetova: If device is SIM-locked (slide 5 of the presentation), you aren't allowed to use your own kernel. The only kernel, which will be allowed, is the kernel, which is shipped with the device, when you buy it from the operator. The reasons for this are simple, and I hope understandable: if we allowed to change the kernel, we can't be sure about security of the SIM-lock. Moreover, it is your choice to buy the device from the operator or from Nokia stores.

===How granular is the encryption?===
If my app creates content in the closed mode can I see it in open mode?

Elena Reshetova: If your application uses the Protected Storage for encryption (slide 8) in the initial mode, and after you switch to another mode, the application won't be able to get decrypted data. If your application just stores the data in the filesystem, after switching to your own kernel, you will be able to access the data (because they are just plain files in the filesystem).

===Can open applications use the privilege mechanisms in the Open and Closed modes?===

Elena Reshetova: I guess the question is "Can the applications access protected resources in both modes?" I hope I got the question correctly. The answer is that the Device Security Policy (slide 7) defines the resources can be potentially granted to the SW coming from a particular SW source. When one uses the Nokia signed kernel, the device security policy is defined, and user can't change it. If one uses its own kernel (or community kernel for example), he (or community) is the one to define/change the device policy. This means that one can, for example, change the policy in the way that the SW coming from the maemo.org gets access to all protected resources (of course some content becomes unavailable when one switch to its own kernel, for example DRM). However, again, it is possible only while using your own kernel.

===Can open applications use the DRM encryption mechanisms in the Open and Closed modes?===
I can see that this could be useful. Maybe.

===Will community extensions to the kernel (modules) be permitted in Open/Closed modes?===
I can't see how - which leads to the question: How do community 'enhancements' to the kernel get adopted?

===Is there any GPLv3 software impacted?===
Please have a license discussion somewhere and let us know when you have consensus.
What is Nokias position? Peter made a statement at the talk - can someone transcribe it and/or get Nokia to clarify.

===What exactly is available to the end user?===

* storage encryption ?
* PIM data encryption ?
* encrypted/signed communications (phone, sms/mms, mails, IM) ?

=== How does closed mode affect on-device debugging? ===

For example, will ptrace(2) still work (eg gdb, strace & ltrace)? Will we be able to produce code dumps?

===Will DRM-free data and DRM-free applications be accessible from both modes once they're installed/created in either of the two modes?===

E.g.: I start in DRM-mode, install DRM-free applications from Extras, take 3 pictures, add some contacts. Then I switch to DRM-free mode: Will I be able to run the applications installed in DRM-free mode, view and edit my contacts and view and edit my own pictures? (And the other way round, of course, starting from DRM-free mode and switching to DRM afterwards.)

===What is open mode good for at all?===

Provided you don't consume digitally restricted media and don't purchase applications that in any way rely on DRM: You don't need DRM-mode then, but on the other hand why would you want DRM-free mode? What is it you cannot do in DRM-mode in such a scenario? Use case?

===What is ARM's TrustZone?===
The official ARM TrustZone page:
http://www.arm.com/products/security/trustzone/index.html

===Can the Trusted Execution Environment (TrEE) be used as a kill switch for the device even if it runs in open mode?===

== Maintaining the discussion ==

On the [http://talk.maemo.org/showthread.php?p=344427#post344427 talk.maemo.org thread], I suggest that end-users are kept at arms' length from this page and we use it as a proper communication mechanism between the community and Elena et al. --[[User:jaffa|Jaffa]] 10:43, 13 October 2009 (UTC)

More discussion in the [http://mg.pov.lt/maemo-irclog/%23maemo.2009-10-11.log.html#t2009-10-11T12:50:36 #maemo chat] which was going on concurrently with the talk and a [http://www.flickr.com/photos/30863507@N02/4007518495/ few] [http://www.flickr.com/photos/30863507@N02/4008286892/ flickr] [http://www.flickr.com/photos/30863507@N02/4007522767/ photos]. --[[User:jaffa|Jaffa]] 11:20, 13 October 2009 (UTC)

Talk:Maemo security

2009-10-15T07:43:54Z

192.100.124.219: /* How granular is the encryption? */

Suggested questions:

===Is there a diagram showing the security framework and components?===
There were some diagrams in the presentation - can we see them.

Elena Reshetova: The presentation was uploaded, and currently it is the only information, which I can share.

===What is "Open Mode" and can it be revoked remotely?===
Is that the right terminology?
Essentially can Nokia reach out the the 2nd stage bootloader and tell it to stop running unsigned kernels.
Maybe this should be 2 questions.

===What does closed mode restrict you from doing?===

* Terminal?
* Root?
** If the [http://aegis.sf.net Aegis AC] is used for the protected storage then root is probably disabled.

** I don't think this Aegis has anything to do with Maemo

Elena Reshetova: We don't have any connection to the Aegis Project, mentioned above. This is a collision of names, I am sorry about it.
In general "close" mode has its own security policy, which user won't be able to change.

* Cellular is marked as a protected ressource in the slide. Can one still use it (phone, data, sms etc.) while running in open mode? While runnin a rebuilt kernel?

Elena Reshetova: If you use your own kernel, you are the one to set the security policy for the device, meaning that your SW in this case can make calls, send sms and so on (for example). Please note that the list of protected resources on the slide is given just as example (to show the possible granularity level), so it doesn't mean that we would have exactly these resources.

===How easy is it to switch between Open and Closed modes?===

Is it so trivial that you would want to and be able to do it several times a day and on the go (without restart)?

Elena Reshetova: I should be able to tell the exact procedure in the future, but for now I can say that it won't be so trivial (like press the GUI button :-)), and the restart is needed. The checks for the SW image are done by the Loader, and during the boot time, so you do need to restart.

===Can network operators restrict you switching to Open mode?===
Like if a device is sim-locked to a particular network, does the device get locked down in closed DRM mode only too? Can you always switch to open mode?

Elena Reshetova: If device is SIM-locked (slide 5 of the presentation), you aren't allowed to use your own kernel. The only kernel, which will be allowed, is the kernel, which is shipped with the device, when you buy it from the operator. The reasons for this are simple, and I hope understandable: if we allowed to change the kernel, we can't be sure about security of the SIM-lock. Moreover, it is your choice to buy the device from the operator or from Nokia stores.

===How granular is the encryption?===
If my app creates content in the closed mode can I see it in open mode?

Elena Reshetova: If your application uses the Protected Storage for encryption (slide 8) in the initial mode, and after you switch to another mode, the application won't be able to get decrypted data. If your application just stores the data in the filesystem, after switching to your own kernel, you will be able to access the data (because they are just plain files in the filesystem).

===Can open applications use the privilege mechanisms in the Open and Closed modes?===

===Can open applications use the DRM encryption mechanisms in the Open and Closed modes?===
I can see that this could be useful. Maybe.

===Will community extensions to the kernel (modules) be permitted in Open/Closed modes?===
I can't see how - which leads to the question: How do community 'enhancements' to the kernel get adopted?

===Is there any GPLv3 software impacted?===
Please have a license discussion somewhere and let us know when you have consensus.
What is Nokias position? Peter made a statement at the talk - can someone transcribe it and/or get Nokia to clarify.

===What exactly is available to the end user?===

* storage encryption ?
* PIM data encryption ?
* encrypted/signed communications (phone, sms/mms, mails, IM) ?

=== How does closed mode affect on-device debugging? ===

For example, will ptrace(2) still work (eg gdb, strace & ltrace)? Will we be able to produce code dumps?

===Will DRM-free data and DRM-free applications be accessible from both modes once they're installed/created in either of the two modes?===

E.g.: I start in DRM-mode, install DRM-free applications from Extras, take 3 pictures, add some contacts. Then I switch to DRM-free mode: Will I be able to run the applications installed in DRM-free mode, view and edit my contacts and view and edit my own pictures? (And the other way round, of course, starting from DRM-free mode and switching to DRM afterwards.)

===What is open mode good for at all?===

Provided you don't consume digitally restricted media and don't purchase applications that in any way rely on DRM: You don't need DRM-mode then, but on the other hand why would you want DRM-free mode? What is it you cannot do in DRM-mode in such a scenario? Use case?

===What is ARM's TrustZone?===
The official ARM TrustZone page:
http://www.arm.com/products/security/trustzone/index.html

===Can the Trusted Execution Environment (TrEE) be used as a kill switch for the device even if it runs in open mode?===

== Maintaining the discussion ==

On the [http://talk.maemo.org/showthread.php?p=344427#post344427 talk.maemo.org thread], I suggest that end-users are kept at arms' length from this page and we use it as a proper communication mechanism between the community and Elena et al. --[[User:jaffa|Jaffa]] 10:43, 13 October 2009 (UTC)

More discussion in the [http://mg.pov.lt/maemo-irclog/%23maemo.2009-10-11.log.html#t2009-10-11T12:50:36 #maemo chat] which was going on concurrently with the talk and a [http://www.flickr.com/photos/30863507@N02/4007518495/ few] [http://www.flickr.com/photos/30863507@N02/4008286892/ flickr] [http://www.flickr.com/photos/30863507@N02/4007522767/ photos]. --[[User:jaffa|Jaffa]] 11:20, 13 October 2009 (UTC)

Talk:Maemo security

2009-10-15T07:36:48Z

192.100.124.219: /* Can network operators restrict you switching to Open mode? */

Suggested questions:

===Is there a diagram showing the security framework and components?===
There were some diagrams in the presentation - can we see them.

Elena Reshetova: The presentation was uploaded, and currently it is the only information, which I can share.

===What is "Open Mode" and can it be revoked remotely?===
Is that the right terminology?
Essentially can Nokia reach out the the 2nd stage bootloader and tell it to stop running unsigned kernels.
Maybe this should be 2 questions.

===What does closed mode restrict you from doing?===

* Terminal?
* Root?
** If the [http://aegis.sf.net Aegis AC] is used for the protected storage then root is probably disabled.

** I don't think this Aegis has anything to do with Maemo

Elena Reshetova: We don't have any connection to the Aegis Project, mentioned above. This is a collision of names, I am sorry about it.
In general "close" mode has its own security policy, which user won't be able to change.

* Cellular is marked as a protected ressource in the slide. Can one still use it (phone, data, sms etc.) while running in open mode? While runnin a rebuilt kernel?

Elena Reshetova: If you use your own kernel, you are the one to set the security policy for the device, meaning that your SW in this case can make calls, send sms and so on (for example). Please note that the list of protected resources on the slide is given just as example (to show the possible granularity level), so it doesn't mean that we would have exactly these resources.

===How easy is it to switch between Open and Closed modes?===

Is it so trivial that you would want to and be able to do it several times a day and on the go (without restart)?

Elena Reshetova: I should be able to tell the exact procedure in the future, but for now I can say that it won't be so trivial (like press the GUI button :-)), and the restart is needed. The checks for the SW image are done by the Loader, and during the boot time, so you do need to restart.

===Can network operators restrict you switching to Open mode?===
Like if a device is sim-locked to a particular network, does the device get locked down in closed DRM mode only too? Can you always switch to open mode?

Elena Reshetova: If device is SIM-locked (slide 5 of the presentation), you aren't allowed to use your own kernel. The only kernel, which will be allowed, is the kernel, which is shipped with the device, when you buy it from the operator. The reasons for this are simple, and I hope understandable: if we allowed to change the kernel, we can't be sure about security of the SIM-lock. Moreover, it is your choice to buy the device from the operator or from Nokia stores.

===How granular is the encryption?===
If my app creates content in the closed mode can I see it in open mode?

===Can open applications use the privilege mechanisms in the Open and Closed modes?===

===Can open applications use the DRM encryption mechanisms in the Open and Closed modes?===
I can see that this could be useful. Maybe.

===Will community extensions to the kernel (modules) be permitted in Open/Closed modes?===
I can't see how - which leads to the question: How do community 'enhancements' to the kernel get adopted?

===Is there any GPLv3 software impacted?===
Please have a license discussion somewhere and let us know when you have consensus.
What is Nokias position? Peter made a statement at the talk - can someone transcribe it and/or get Nokia to clarify.

===What exactly is available to the end user?===

* storage encryption ?
* PIM data encryption ?
* encrypted/signed communications (phone, sms/mms, mails, IM) ?

=== How does closed mode affect on-device debugging? ===

For example, will ptrace(2) still work (eg gdb, strace & ltrace)? Will we be able to produce code dumps?

===Will DRM-free data and DRM-free applications be accessible from both modes once they're installed/created in either of the two modes?===

E.g.: I start in DRM-mode, install DRM-free applications from Extras, take 3 pictures, add some contacts. Then I switch to DRM-free mode: Will I be able to run the applications installed in DRM-free mode, view and edit my contacts and view and edit my own pictures? (And the other way round, of course, starting from DRM-free mode and switching to DRM afterwards.)

===What is open mode good for at all?===

Provided you don't consume digitally restricted media and don't purchase applications that in any way rely on DRM: You don't need DRM-mode then, but on the other hand why would you want DRM-free mode? What is it you cannot do in DRM-mode in such a scenario? Use case?

===What is ARM's TrustZone?===
The official ARM TrustZone page:
http://www.arm.com/products/security/trustzone/index.html

===Can the Trusted Execution Environment (TrEE) be used as a kill switch for the device even if it runs in open mode?===

== Maintaining the discussion ==

On the [http://talk.maemo.org/showthread.php?p=344427#post344427 talk.maemo.org thread], I suggest that end-users are kept at arms' length from this page and we use it as a proper communication mechanism between the community and Elena et al. --[[User:jaffa|Jaffa]] 10:43, 13 October 2009 (UTC)

More discussion in the [http://mg.pov.lt/maemo-irclog/%23maemo.2009-10-11.log.html#t2009-10-11T12:50:36 #maemo chat] which was going on concurrently with the talk and a [http://www.flickr.com/photos/30863507@N02/4007518495/ few] [http://www.flickr.com/photos/30863507@N02/4008286892/ flickr] [http://www.flickr.com/photos/30863507@N02/4007522767/ photos]. --[[User:jaffa|Jaffa]] 11:20, 13 October 2009 (UTC)

Talk:Maemo security

2009-10-15T07:31:35Z

192.100.124.219: /* How easy is it to switch between Open and Closed modes? */

Suggested questions:

===Is there a diagram showing the security framework and components?===
There were some diagrams in the presentation - can we see them.

Elena Reshetova: The presentation was uploaded, and currently it is the only information, which I can share.

===What is "Open Mode" and can it be revoked remotely?===
Is that the right terminology?
Essentially can Nokia reach out the the 2nd stage bootloader and tell it to stop running unsigned kernels.
Maybe this should be 2 questions.

===What does closed mode restrict you from doing?===

* Terminal?
* Root?
** If the [http://aegis.sf.net Aegis AC] is used for the protected storage then root is probably disabled.

** I don't think this Aegis has anything to do with Maemo

Elena Reshetova: We don't have any connection to the Aegis Project, mentioned above. This is a collision of names, I am sorry about it.
In general "close" mode has its own security policy, which user won't be able to change.

* Cellular is marked as a protected ressource in the slide. Can one still use it (phone, data, sms etc.) while running in open mode? While runnin a rebuilt kernel?

Elena Reshetova: If you use your own kernel, you are the one to set the security policy for the device, meaning that your SW in this case can make calls, send sms and so on (for example). Please note that the list of protected resources on the slide is given just as example (to show the possible granularity level), so it doesn't mean that we would have exactly these resources.

===How easy is it to switch between Open and Closed modes?===

Is it so trivial that you would want to and be able to do it several times a day and on the go (without restart)?

Elena Reshetova: I should be able to tell the exact procedure in the future, but for now I can say that it won't be so trivial (like press the GUI button :-)), and the restart is needed. The checks for the SW image are done by the Loader, and during the boot time, so you do need to restart.

===Can network operators restrict you switching to Open mode?===
Like if a device is sim-locked to a particular network, does the device get locked down in closed DRM mode only too? Can you always switch to open mode?

===How granular is the encryption?===
If my app creates content in the closed mode can I see it in open mode?

===Can open applications use the privilege mechanisms in the Open and Closed modes?===

===Can open applications use the DRM encryption mechanisms in the Open and Closed modes?===
I can see that this could be useful. Maybe.

===Will community extensions to the kernel (modules) be permitted in Open/Closed modes?===
I can't see how - which leads to the question: How do community 'enhancements' to the kernel get adopted?

===Is there any GPLv3 software impacted?===
Please have a license discussion somewhere and let us know when you have consensus.
What is Nokias position? Peter made a statement at the talk - can someone transcribe it and/or get Nokia to clarify.

===What exactly is available to the end user?===

* storage encryption ?
* PIM data encryption ?
* encrypted/signed communications (phone, sms/mms, mails, IM) ?

=== How does closed mode affect on-device debugging? ===

For example, will ptrace(2) still work (eg gdb, strace & ltrace)? Will we be able to produce code dumps?

===Will DRM-free data and DRM-free applications be accessible from both modes once they're installed/created in either of the two modes?===

E.g.: I start in DRM-mode, install DRM-free applications from Extras, take 3 pictures, add some contacts. Then I switch to DRM-free mode: Will I be able to run the applications installed in DRM-free mode, view and edit my contacts and view and edit my own pictures? (And the other way round, of course, starting from DRM-free mode and switching to DRM afterwards.)

===What is open mode good for at all?===

Provided you don't consume digitally restricted media and don't purchase applications that in any way rely on DRM: You don't need DRM-mode then, but on the other hand why would you want DRM-free mode? What is it you cannot do in DRM-mode in such a scenario? Use case?

===What is ARM's TrustZone?===
The official ARM TrustZone page:
http://www.arm.com/products/security/trustzone/index.html

===Can the Trusted Execution Environment (TrEE) be used as a kill switch for the device even if it runs in open mode?===

== Maintaining the discussion ==

On the [http://talk.maemo.org/showthread.php?p=344427#post344427 talk.maemo.org thread], I suggest that end-users are kept at arms' length from this page and we use it as a proper communication mechanism between the community and Elena et al. --[[User:jaffa|Jaffa]] 10:43, 13 October 2009 (UTC)

More discussion in the [http://mg.pov.lt/maemo-irclog/%23maemo.2009-10-11.log.html#t2009-10-11T12:50:36 #maemo chat] which was going on concurrently with the talk and a [http://www.flickr.com/photos/30863507@N02/4007518495/ few] [http://www.flickr.com/photos/30863507@N02/4008286892/ flickr] [http://www.flickr.com/photos/30863507@N02/4007522767/ photos]. --[[User:jaffa|Jaffa]] 11:20, 13 October 2009 (UTC)

Talk:Maemo security

2009-10-14T14:39:24Z

192.100.124.219: /* Is there a diagram showing the security framework and components? */