sound volume adjustment.
Use these:
HILDON_HARDKEY_INCREASE
HILDON_HARDKEY_DECREASE
As defined in:
https://git.maemo.org/projects/hildon/gitweb?p=hildon;a=blob;f=hildon/hildon-defines.h;h=f6e251d7cb667f80e4cbf9abbc5f3e0e23c2a829;hb=HEAD
I think these were already available in the previous
HILDON_ICON_SIZE_FINGER
Or in pixels:
HILDON_ICON_PIXEL_SIZE_FINGER
BR,
Mox
-Original Message-
From: maemo-developers-boun...@maemo.org
[mailto:maemo-developers-boun...@maemo.org] On Behalf Of ext
Cornelius Hald
Sent: 31 August, 2009 16:14
To: maemo-developers@maemo.org
Subject:
ext Andrea Grandi wrote:
Hi,
2009/9/4 Kate Alhola kate.alh...@nokia.commailto:kate.alh...@nokia.com:
Current version is 4.5.2, soon 4.5.3 . Qt is already in Fremantle
repository,
so installing Qt applications to N900 is already totally transparent to end
user
because application installer
From: Alhola Kate (Nokia-FNDC/Tampere)
So while _technically_ QT apps work on Fremantle, I'd like
to hear and
see whether it is really possible to provide a true Maemo 5 user
experience when using QT as the toolkit.
Toolkit, either GTK or Qt can't fix the UI design. If you
don't make
- Original message -
On Fri, Sep 04, 2009 at 07:16:43PM +0200,
kate.alh...@nokia.commailto:kate.alh...@nokia.com wrote:
What people are asking here (among other things) is whether there
are Qt widgets similar to HildonAppMenu or HildonPickerButton
-which are absolutely
On Sat, Sep 5, 2009 at 08:01
However, if you want to have the exact same user experience as the
preinstalled Maemo 5 applications have (as seen in all youtube videos and
the SDK), then you have much easier time and faster development with the
gtk-based hildon widgets in Maemo 5.
This
Hi all,
There is already good documentation available on wiki.maemo.org regarding UI
Design of Maemo 5.
In particular there's the Maemo 5 Human Interface Guidelines at:
http://wiki.maemo.org/index.php?title=Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines
The above document
Hi,
The purpose of the two labels in HildonButton, is to have different semantics
for the labels.
The first one is title, the second one is value (HildonPickerButton) or
description (Hildonbutton)
The checkbutton doesn't really fit so well with this kind of semantics. So
you're not really
The purpose of the two labels in HildonButton, is to have different
semantics for the labels.
The first one is title, the second one is value (HildonPickerButton) or
description (Hildonbutton)
that's fine with me. The first row is Name of Plugin the second is
Description of plugin. Now it
-Original Message-
From: ext Cornelius Hald [mailto:h...@icandy.de]
But of course I could recreate the same layout as I have now,
but instead of buttons using a TreeView. [...] I
might give it a try, though. How is the cell renderer called
that is used for the two-row text?
Talk to
The color wheel might be more understandable to users, yes,
but it's very hard to do a complete color dialog for Maemo 5 and
fit a large finger-usable color-wheel into that space.
It is doable, if you compromise and use stylus instead, but I think
then the whole point of a new widget is lost.
Hi, couple of comments to the color pickers...
http://zwong.de/wp-content/uploads/2009/10/screenshot12.png
Having a pre-defined palette (and possibly a picker to choose different
palettes) seems like the best way to tackle this.
Maybe just start with Tango palette (as proposed) and
12 matches
Mail list logo
