Adapting GNOME Applications to Maemo Fremantle

static void_f_do_barnacle_install_properties(GObjectClass

*gobject_class){

GParamSpec *pspec;

/* Party code attribute */ pspec = g_param_spec_uint64 (F_DO_BARNACLE_CODE,

"Barnacle code.", "Barnacle code",

0, G_MAXUINT64,

G_MAXUINT64 /* default value */,

G_PARAM_READABLE | G_PARAM_WRITABLE |

G_PARAM_PRIVATE);

g_object_class_install_property (gobject_class,

F_DO_BARNACLE_PROP_CODE,

Joaquim Rocha (jrocha on IRC)[email protected]

Adapting GNOMEApplications toMaemo Fremantle

Adapting GNOME Applications to Maemo Fremantle · Joaquim Rocha <[email protected]>

whoami

● GTK+ && Hildon && Python developer

● Igalian since 2008

● Part of Hildon Input Methods project

What porting means?


What porting means

● Before Fremantle:● Make an application RUN in Maemo

● After Fremantle:● ADAPT an application to Maemo


Why bothering?

● Your application gets better● Your users get happier● Your fingers too!


GNOME Applications

● Coding will be easier – it is GTK+!● Lots of interesting applications waiting to be ported!● If you're a GNOME user, you may have your common

applications available to you.

Root view / Sub view


Root view / sub view philosophy

● Applications are stacks of windows

● The root window is the base● E.g.: List of emails

● Actions that break the usage flow, will be sub views:● E.g.: Reading an email


Root View Sub View

This means: no GTKPaned!

Black Chapter

FAIL!FAIL!

What to do with this!?

Divide and Conquer


When a box is tapped,a dialog appears...

Use a GtkToggle button or a HildonPickerButton

Replaced the GtkSpinButtons by HildonEntries and not by HildonPickerButtons because the changes are shown immediately in the image.

Assign the numeric GtkInputMode

Text is the focus here, so, instead of a GtkNotebook, the style properties are in a GtkDialog launched from the text properties HildonAppMenu

GtkSpinButtons are replaced by HildonPickerButtons with a TouchSelectorEntry assigned

HildonAppMenu


HildonAppMenu

● Really different from a GtkMenu!!

● Do not stuff it: Keep a low number of items

● Use filters to display HOW contents are shown, not WHICH contents are shown


DRY: Don't Repeat Yourself

How to keep a low number of menu items?

Choose the most used/important menus and sub-menus from the menu bar.

Pages can be chosen using gestures, so, no need for Next/Previous menus.

The status bar and toolbar are not used in EOG for Maemo, so, no menus are needed.

The Zoom In / Zoom Out functionalities are accomplished by using the Increase / Decrease hard-keys.


Following the Hildon Interface Guidelines

● HIG says: don't show menu items that are insensitive● Here's a helpful tip:

● Connect a callback to the “show” signal of each HildonAppMenu item

● The callback shows/hides the item according to its “sensitive” property

EOG with no images loaded

EOG with an image loaded

Migrating Preferences Dialogs


Preferences Dialogs

● Dialogs with a GtkNotebook to group different kinds of preferences

● Tabs' labels define groups' names


How to migrate it to Fremantle?

● Use a HildonPannableArea

● Add a GtkVBox with ALL the preferences groups and use a GtkLabel above each one, identifying it


Where to go from here?

● Maemo 5 Developer Guide:

http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide

● Maemo 5 API Reference:

http://maemo.org/api_refs/5.0/5.0-final/hildon/

http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide

http://maemo.org/api_refs/5.0/5.0-final/hildon/

Questions?

Thank you!

Technology

Adapting GNOME Applications to Maemo Fremantle