MeeGo wiki - User contributions [en]

Maliit

2011-11-09T21:42:43Z

Jonnor: /* Communication channels */ update with Maliit upstream comm channels

{{MaliitNavigationBar}}

[[File:Maliit2.png|448px|link=]]

Maliit is the input methods solution used in MeeGo. See the [http://www.maliit.org official project website] for more information.

This wiki contains information about Maliit in MeeGo. Information that is not MeeGo specific is found upstream.

== Communication channels ==
All Maliit communication – also MeeGo specific – now happens in Maliit upstream channels. [http://lists.maliit.org/pipermail/maliit-discuss-maliit.org/2011-November/000001.html Announcement]

'''Mailing list:''' maliit-discuss@lists.maliit.org ([http://lists.maliit.org/listinfo.cgi/maliit-discuss-maliit.org listinfo] | [http://lists.maliit.org/pipermail/maliit-discuss-maliit.org/ archives])

'''Bugtracker:''' bugs.meego.com, Product: OS, Component: Virtual Keyboard ([https://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_based_on=virtual%20keyboard&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&component=Virtual%20keyboard&product=OS%20Base&known_name=virtual%20keyboard open bugs] |
[https://bugs.meego.com/enter_bug.cgi?product=OS%20Base&component=Virtual%20keyboard file new bug])

'''IRC:''' Visit us in #maliit at freenode.net ([http://webchat.freenode.net/?randomnick=1&channels=maliit&uio=d4 webchat])

{{MaliitNavigationBar}}

Maliit/Installing

2011-09-05T10:04:01Z

Jonnor:

{{MaliitNavigationBar}}

Meego Input Methods comes preinstalled and works out-of-the-box on:
* Meego Handset UX 1.1 and later
* Meego Tablet UX 1.2 and later

=== Meego Netbook UX ===

These steps have been tested on Meego 1.1.

* Enable the 'handset' repository. For example:

$ sudo zypper addrepo <nowiki>http://repo.meego.com/MeeGo/releases/1.1/handset/repos/ia32/packages/</nowiki> handset
$ sudo zypper refresh

* Install these packages:
** meegotouch-inputmethodbridges
** meegotouch-inputmethodkeyboard

sudo zypper install meegotouch-inputmethodkeyboard meegotouch-inputmethodbridges

* Modify <code>/etc/xdg/autostart/meego-im-uiserver.desktop</code> to look like this:

[Desktop Entry]
Exec=/usr/bin/meego-im-uiserver -target slate -bypass-wm-hint
X-Moblin-Priority=High
OnlyShowIn=X-MEEGO-HS;X-MEEGO-NB

This will work with 1024x600 resolution. Replace 'slate' with other code if you have different resolution. See /etc/meegotouch/devices.conf for different codes.

* Add this line to ~/.bashrc (any better place in X configs? /etc/X11/xinitrc-common failed for me) to activate the inputmethod plugin for Qt-based programs:
export QT_IM_MODULE=MInputContext

* Relogin (or reboot) to desktop

{{MaliitNavigationBar}}

Maliit/Development

2011-09-05T10:02:38Z

Jonnor: add bug search links

{{MaliitNavigationBar}}

Most development of Maliit happens [http://maliit.org upstream]. This page contains development information specific Maliit to MeeGo.

== Repositories ==
For MeeGo 1.2, the following branches are used:
* https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/commits/meego-1.2
* https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/commits/meego-1.2

== Meego packaging ==
* [http://build.meego.com/project/show?project=devel%3Ainput-methods devel:input-methods on MeeGo OBS]
* [http://build.meego.com/project/monitor?commit=Filter%3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&pkgname=maliit&repo_standard=1&repo_weekly=1&arch_armv8el=1&arch_i586=1&project=Trunk&defaults=0 Status in Trunk]
* [http://build.meego.com/project/monitor?commit=Filter%3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&pkgname=inputmethod&repo_standard=1&arch_armv8el=1&arch_i586=1&project=MeeGo%3A1.2%3Aoss&defaults=0 Status in 1.2]
* [http://build.meego.com/project/monitor?commit=Filter%3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&pkgname=inputmethod&repo_standard=1&arch_armv7el=1&arch_i586=1&lastbuild=1&project=MeeGo%3A1.1%3ACore&defaults=0 Status in 1.1]

== QA Reports ==
Latest inputmethod packages QA reports using recent Meego images can be found at the [http://qa-reports.meego.com/1.2/Handset/Basic%20Feature%20Testing/N900 QA Basic Feature Testing] section of [http://qa-reports.meego.com http://qa-reports.meego.com].

== Open bug reports ==
Open bugs under [https://bugs.meego.com/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=maliit-framework&component=maliit-plugins&product=MeeGo%20Distribution%20Packages MeeGo Distribution Packages -> Maliit] (for Meego 1.3+)

Open bugs under [https://bugs.meego.com/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=meegotouch-inputmethodbridges&component=meegotouch-inputmethodengine&component=meegotouch-inputmethodframework&component=meegotouch-inputmethodkeyboard&product=MeeGo%20Distribution%20Packages&classification=MeeGo%20Platform MeeGo Distribution Packages -> meegotouch-inputmethod] (not in use)

Open bugs under [https://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_based_on=virtual%20keyboard&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=Virtual%20keyboard&product=OS%20Base&known_name=virtual%20keyboard OS Base -> Virtual keyboard] (for Meego 1.0, 1.1 and 1.2)

{{#bugzilla:
|columns=id,status,to,severity,version,summary
|group=priority
|grouporder=asc
|component=Virtual keyboard
|product=OS Base
|status=UNCONFIRMED,NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED
|lastcomment=1
}}

{{MaliitNavigationBar}}

Template:MaliitNavigationBar

2011-07-12T17:03:23Z

Jonnor:

{| class="wikitable" style="width:100%;text-align:center"
! [[Maliit|Maliit - Input Methods for MeeGo]]
|-
| [[Maliit|Overview]] · [[Maliit/Development|Development]] · [[Maliit/Installing|Installing]] · [[Maliit/Roadmap|Roadmap]]
|}

[[Category:Maliit]][[Category:MeeGo Input Methods]]

Maliit/Team

2011-07-12T16:53:23Z

Jonnor: Replaced content with "Moved to Maliit"

Moved to [[Maliit]]

Maliit

2011-07-12T16:42:26Z

Jonnor: remove non-MeeGo specific content (moved upstream)

{{MaliitNavigationBar}}

[[File:Maliit2.png|448px|link=]]

Maliit is the input methods solution used in MeeGo. See the [http://www.maliit.org official project website] for more information.

This wiki contains information about Maliit in MeeGo. Information that is not MeeGo specific is found upstream.

== Communication channels ==

'''Mailing list:''' meego-inputmethods@lists.meego.com ([http://lists.meego.com/listinfo/meego-inputmethods listinfo] | [http://lists.meego.com/pipermail/meego-inputmethods/ archives])

'''Bugtracker:''' bugs.meego.com, Product: OS, Component: Virtual Keyboard ([https://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_based_on=virtual%20keyboard&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&component=Virtual%20keyboard&product=OS%20Base&known_name=virtual%20keyboard open bugs] |
[https://bugs.meego.com/enter_bug.cgi?product=OS%20Base&component=Virtual%20keyboard file new bug])

'''IRC:''' Visit us in #meego-inputmethods at freenode.net ([http://webchat.freenode.net/?randomnick=1&channels=meego-inputmethods&uio=d4 webchat])

{{MaliitNavigationBar}}

Maliit/Meetings

2011-07-12T16:18:50Z

Jonnor: add meego input methods category

== MeeGo Input Methods IRC meeting, March 29th 2011 ==

=== How can we simplify development and maintenance of input contexts? ===

Participants: Michael Hasselmann (Openismus), Jon Nordby (Openismus), Andy Ross (Windriver), Pekka Vuorela (Nokia), Gary Birkett (Collabora), Robin Burchell (Collabora)

Log: http://lists.meego.com/pipermail/meego-inputmethods/2011-March/000037.html

The outcome of this meeting were the following tasks:

{| border="0" cellpadding="4" class="wikitable"
! Task !! Assignee !! Status !! Details
|-
| Alternative for MInputMethodState || [https://bugs.meego.com/show_bug.cgi?id=20076 BMC#20076] || done || We need to provide a fully working alternative for MInputMethodState. And this would also fit with our plans to offer better support for plain Qt, QML, Qt Components (and GTK+ on MeeGo). We can decide to add the less important features (toolbar and keyboard customization) at a later point, for example.
|-
| Decide on where to put extended API || [https://bugs.meego.com/show_bug.cgi?id=20076 BMC#20076] || done || No agreement yet on whether it's better to provide needed API through signals/slots in inputcontext or whether it's better to provide a separate library (in MeeGo Input Methods itself). Andy Ross is supposed to kick off the discussion on the public ML (check next week).
|-
| Clean up D-Bus API || Maksim Kirillov || done || We clean up the D-Bus API, instead of further abstraction. We will use native D-Bus types instead of (serialized) Qt datatypes.
|-
| Check QtDBus status in Qt 4.8 || [https://qt.gitorious.org/qt/qt/merge_requests/2343 MRQ#2343] || done || Check QtDBus situation in 4.8 and switch to Qt's D-Bus interface, if possible. We need working P2P D-Bus.
|-
| Provide documentation for D-Bus API || [[Maliit/Documentation#Documentation_working_area|moved here]] || punted || Obvious. Currently no overview of its intent or how it actually works, only documentation on the methods itself.
|}

[[Category:Maliit]][[Category:MeeGo Input Methods]]

Template:MaliitNavigationBar

2011-07-12T16:14:01Z

Jonnor: update to only have pages with content on them

{| class="wikitable" style="width:100%;text-align:center"
! [[Maliit|Maliit - Input Methods for MeeGo]]
|-
| [[Maliit|Overview]] · [[Maliit/Development|Development]] · [[Maliit/Installing|Installing]] · [[Maliit/Roadmap|Roadmap]] · [[Maliit/Team|Team]]
|}

[[Category:Maliit]][[Category:MeeGo Input Methods]]

Maliit/Meetings

2011-07-12T16:06:30Z

Jonnor: update

Maliit/Ideas/Supporting Non X11 Platforms

2011-07-12T15:55:52Z

Jonnor: Moved (upstream) to http://wiki.maliit.org/Ideas/Supporting_Non_X11_Platforms

Moved (upstream) to http://wiki.maliit.org/Ideas/Supporting_Non_X11_Platforms

Maliit/Installing

2011-07-12T15:51:27Z

Jonnor:

{{MaliitNavigationBar}}

Meego Input Methods comes preinstalled on:
* Meego Handset UX 1.1 and later
* Meego Tablet UX 1.2 and later

=== Meego Netbook UX ===

These steps have been tested on Meego 1.1.

* Enable the 'handset' repository. For example:

$ sudo zypper addrepo <nowiki>http://repo.meego.com/MeeGo/releases/1.1/handset/repos/ia32/packages/</nowiki> handset
$ sudo zypper refresh

* Install these packages:
** meegotouch-inputmethodbridges
** meegotouch-inputmethodkeyboard

sudo zypper install meegotouch-inputmethodkeyboard meegotouch-inputmethodbridges

* Modify <code>/etc/xdg/autostart/meego-im-uiserver.desktop</code> to look like this:

[Desktop Entry]
Exec=/usr/bin/meego-im-uiserver -target slate -bypass-wm-hint
X-Moblin-Priority=High
OnlyShowIn=X-MEEGO-HS;X-MEEGO-NB

This will work with 1024x600 resolution. Replace 'slate' with other code if you have different resolution. See /etc/meegotouch/devices.conf for different codes.

* Add this line to ~/.bashrc (any better place in X configs? /etc/X11/xinitrc-common failed for me) to activate the inputmethod plugin for Qt-based programs:
export QT_IM_MODULE=MInputContext

* Relogin (or reboot) to desktop

{{MaliitNavigationBar}}

Maliit/Ideas

2011-07-12T15:47:45Z

Jonnor: Moved (upstream) to http://wiki.maliit.org/Ideas

Moved (upstream) to http://wiki.maliit.org/Ideas

Maliit/Roadmap

2011-07-12T15:44:28Z

Jonnor: remove non-Meego specific content (moved upstream)

{{MaliitNavigationBar}}

== MeeGo 1.3 ==
Development in in progress.

MeeGo 1.3 will have Maliit 1.0 (see [http://wiki.maliit.org/Roadmap upstream roadmap]).

* New maliit-* package-names (DONE)
* Settings applet for meego-ux-settings
* Better integration with standard applications

== MeeGo 1.2 ==
All items in this section are DONE.

=== Framework ===
* private D-Bus connection
* new information exposures:
** anchor position
** cursor position
* libmeegotouch removal
* self-compositing
* self-rotation animation

=== Engine framework ===
* New interface: Handwriting recognition
* New functionality: Dynamic virtual keyboard layout

{{MaliitNavigationBar}}

Maliit/Team

2011-07-12T15:42:06Z

Jonnor: removed non-Meego specific content (moved upstream)

{{MaliitNavigationBar}}

Most of the team works on Maliit upstream. See http://wiki.maliit.org/Team

== MeeGo Integration Team ==
* Luis Araujo (lead)
* Rakesh Cherian (Test Developer, Bug Triager)
* [http://meego.com/users/jonnor Jon Nordby] (Developer)

{{MaliitNavigationBar}}

Maliit/Features

2011-07-12T15:40:40Z

Jonnor: Moved upstream to http://wiki.maliit.org/Features

Moved upstream to http://wiki.maliit.org/Features

Maliit/Documentation

2011-07-12T15:34:25Z

Jonnor: Moved (upstream) to http://wiki.maliit.org/Documentation

Moved (upstream) to http://wiki.maliit.org/Documentation

Maliit/Development

2011-07-12T15:31:06Z

Jonnor: remove all non-meego specific content (moved upstream)

Maliit/Making a Release

2011-07-12T15:22:55Z

Jonnor: moved upstream

Moved to http://wiki.maliit.org/Development/Making_Releases

Maliit/Writing Release Notes

2011-07-12T15:22:41Z

Jonnor: moved upstream

Moved to http://wiki.maliit.org/Development/Making_Releases

Maliit

2011-07-06T10:07:17Z

Jonnor: /* Maliit in action */ SEO

{{MaliitNavigationBar}}

[[File:Maliit2.png|448px|link=]]

Maliit provides a flexible and cross-platform input method framework, including a virtual keyboard. It works on all MeeGo user experiences, and in other GNU/Linux distributions.

== Goals ==

Maliit aims to be ''the'' input method project for MeeGo and other GNU/Linux-based embedded/mobile platforms. To achieve this we should provide:

'''A solid input method framework'''

This includes support for traditional input methods such as hardware and virtual keyboards. More exotic input methods should also be possible, such as handwriting recognition and voice input, and special purpose input methods such as date/time pickers, tag clouds, etc.

'''A core set of input methods'''

The default set of input methods should demonstrate the core capabilities of the framework and provide a good user experience that device manufacturers and integrators can use easily.

We also aim to:

'''Empower third-party developers'''

Customizing existing input methods or developing powerful new input methods should be simple, regardless of whether it is for profit, research or fun.

'''Build a diverse community of contributors'''

Employees from different companies, freelancers, members of academia, hackers and volunteers should all be welcomed and encouraged to contribute to the project.

== Communication channels ==

'''Mailing list:''' meego-inputmethods@lists.meego.com ([http://lists.meego.com/listinfo/meego-inputmethods listinfo] | [http://lists.meego.com/pipermail/meego-inputmethods/ archives])

'''Bugtracker:''' bugs.meego.com, Product: OS, Component: Virtual Keyboard ([https://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_based_on=virtual%20keyboard&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&component=Virtual%20keyboard&product=OS%20Base&known_name=virtual%20keyboard open bugs] |
[https://bugs.meego.com/enter_bug.cgi?product=OS%20Base&component=Virtual%20keyboard file new bug])

'''IRC:''' Visit us in #meego-inputmethods at freenode.net ([http://webchat.freenode.net/?randomnick=1&channels=meego-inputmethods&uio=d4 webchat])

== Social Media ==

'''Facebook: ''' [http://www.facebook.com/home.php?sk=group_127020324047804 Maliit group]

'''Twitter/Identica: ''' Use the #maliit hashtag

== Upcoming events ==
* August 6th-12th - Desktop Summit Berlin. Workshops & BoFs planned

== News ==
* 24.06.2011 - MeeGo Freeday presentation/workshop in Berlin. [http://meetmeego.org/2011/06/15/meego-freeday-24-06-2011/ Announcement] (in german), [[Media:Maliit-input-methods-for-meego.pdf|Slides]], [http://www.youtube.com/watch?v=kmR0J699oGA Video]
* 21.06.2011 - Nokia's N9 announced, with input methods powered by Maliit [http://www.youtube.com/watch?v=JOI5g129rtM Video]
* 20.06.2011 - First release (Maliit 0.80) as an independent project. [http://lists.meego.com/pipermail/meego-dev/2011-June/483526.html Announcement]
* 17.06.2011 - Session at Qt Collaborator Summit 2011. [http://developer.qt.nokia.com/groups/qt_contributors_summit/wiki/Input_methods_and_Wayland_in_Qt_5 Session summary]
* 24.05.2011 - Session at MeeGo Spring Conference 2011. [http://sf2011.meego.com/program/sessions/developing-custom-input-methods-meego Info, Recording]
* 08.04.2011 - MeeGo Keyboard is relicensed with BSD license: [http://lists.meego.com/pipermail/meego-dev/2011-April/482578.html Announcement]
* 29.03.2011 - Held first offical IRC meeting: [[Maliit/Meetings|How can we simplify development and maintenance of input contexts?]]
* 04.03.2011 - API/ABI break in 0.20.0: [http://lists.meego.com/pipermail/meego-dev/2011-March/481869.html meego-im-framework is removing dependency to libmeegotouch from its API]
* 23.02.2011 - Packages available for Ubuntu Lucid/Maverick to ease development. [http://taschenorakel.de/michael/2011/02/24/meego-input-methods-your-desktop/ Blogpost], [[#Packages for Ubuntu .2810.04 Lucid Lynx .2F 10.10 Maveric Meerkat.29|documentation]]
* 17.02.2011 - Claudio Saavedra started on MeeGo+Gtk integration work, focusing on input methods. [http://people.gnome.org/~csaavedra/news-2011-02.html#D10 Blogpost]
* 13.02.2011 - MeeGo Tablet UX demoed at Mobile World Conference, with Swype keyboard. [http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 Pictures]
* 01.02.2011 - API/ABI break in 0.19.41: [http://lists.meego.com/pipermail/meego-dev/2011-February/481353.html meegoimframework interfaces related to orientation change will be changed]
* 15.11.2010 - Architect and Lead Developer of Maliit give talk at MeeGo Conference. [http://conference2010.meego.com/session/meego-touch-input-method-frameworks Info, Recording]
* 15.11.2010 - Linpus shows off MeeGo based slate at MeeGo Conference, with keyboard based on Maliit.
* 30.06.2010 - MeeGo Handset UX Day 1 release, first public release of MeeGo Input Methods. [http://meego.com/community/blogs/valhalla/2010/meego-handset-project-day-1-here Announcement]

== Maliit in action ==

Maliit is used on a number of devices and form factors, and can easily be adapted to run on new ones. Here are some screenshots, pictures and videos.

* [http://www.linpus.com/products_meego_slate.html Linpus Slate] ([http://www.linpus.com/images/slate/kb.png screenshot showing Linpus virtual keyboard])
* [http://appdeveloper.intel.com/en-us/meego-iso-esla Intel MeeGo Tablet] ([http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 pictures showing Swype keyboard])
* [http://www.youtube.com/watch?v=l_7f3Lxd4_I GNOME3 on a WeTab (video)]
* [http://www.youtube.com/watch?v=JOI5g129rtM N9 and Swype integration (video)]
<gallery widths="250px" heights="250px" perrow="3">
Image:Lenovo_meego_vkb.jpg| [[Maliit/MeeGo 1.1#Netbook|MeeGo 1.1 Netbook]] with MeeGo Keyboard on Lenovo S10-3T Ideapad
Image:Meego1.1_handset_on_aava.jpg| [http://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo 1.1 Handset] with MeeGo Keyboard on Aava Mobile
Image:tegra-vkb2.jpg| MeeGo 1.2 prerelease on [[ARM/TEGRA2|Advent Vega, Tegra2]]
Image:Maliit-on-lucid.png | Ubuntu Lucid (10.04)
Image:Maliit-in-GNOME3.jpg | GNOME3 on a WeTab
Image:Maliit-on-KDE-Plasma.jpg | KDE, using Plasma
Image:Maliit-meego-ce-n900-landscape.jpg | MeeGo N900CE (landscape)
Image:Maliit-meego-ce-n900-portrait.jpg | MeeGo N900CE (portrait)
Image:Maliit_Nokia_N9.jpg | Nokia N9
</gallery>

{{MaliitNavigationBar}}

Maliit/Documentation/Examples

2011-07-05T12:28:52Z

Jonnor: Created page with "Currently these items are all TODO. = Guidelines for examples = All examples should show a single aspect of Maliit, and be self contained. The best way is to make the examples ..."

Currently these items are all TODO.

= Guidelines for examples =

All examples should show a single aspect of Maliit, and be self contained.
The best way is to make the examples standalone.
An additional overview/demo application can be used to launch these standalone examples.
(similar to what GTK+ does)

Examples must be built as part of the standard build. Whenever possible
they should also have a sanity test that is a part of the ordinary test suite.
The existing examples in maliit-framework examples/ do this, and can be used as a base.

Examples should be installed as part of a normal install, both the binaries
and the source code. We do currently not have a ready solution for this, but it
could be done by adding similar logic as the maliit-plugin-sdk-dist.sh script
to the build system.

Check if we can use stuff from LMT widgetsgallery.

= Examples and testing =
Our UI tests currently have a number of test applications. For the simplest one
the tests should be able to use the examples we provide here instead of custom
ones. This reduces duplication and means our examples are tested.

Idea: Have applications with different toolkits and test all of them with our UI tests.

= Wanted examples =

== Plugin development examples ==
* Integrating a correction engine
* Attribute extensions - shown a couple of keys and allows to customize them
* Cycle-keys - Can be used to explain difference between preedit and commit
* How to handle rotation

== Application / Application Framework examples ==
Should be plain Qt and/or QML. Would use the new libmaliit library

* Attribute extensions - goes together with the plugin example
* Rotation - how to notify the IM framework about rotation changes
* Input Widget relocation
* Input Method hints

== Engine plugin development ==
* Handwriting
* Words

== Reference plugins ==
* Layouts
* Theming
* Adding an engine

== Feedback ==
* How to use reactionmaps
* How to use feedback FW api
* How to write a feedback backend

== Other ==

* Settings
* Hardware keyboard presence notification

Maliit

2011-06-30T07:06:43Z

Jonnor: /* Communication channels */ add social media

{{MaliitNavigationBar}}

[[File:Maliit2.png|448px|link=]]

Maliit provides a flexible and cross-platform input method framework, including a virtual keyboard. It works on all MeeGo user experiences, and in other GNU/Linux distributions.

== Goals ==

Maliit aims to be ''the'' input method project for MeeGo and other GNU/Linux-based embedded/mobile platforms. To achieve this we should provide:

'''A solid input method framework'''

This includes support for traditional input methods such as hardware and virtual keyboards. More exotic input methods should also be possible, such as handwriting recognition and voice input, and special purpose input methods such as date/time pickers, tag clouds, etc.

'''A core set of input methods'''

The default set of input methods should demonstrate the core capabilities of the framework and provide a good user experience that device manufacturers and integrators can use easily.

We also aim to:

'''Empower third-party developers'''

Customizing existing input methods or developing powerful new input methods should be simple, regardless of whether it is for profit, research or fun.

'''Build a diverse community of contributors'''

Employees from different companies, freelancers, members of academia, hackers and volunteers should all be welcomed and encouraged to contribute to the project.

== Communication channels ==

'''Mailing list:''' meego-inputmethods@lists.meego.com ([http://lists.meego.com/listinfo/meego-inputmethods listinfo] | [http://lists.meego.com/pipermail/meego-inputmethods/ archives])

'''Bugtracker:''' bugs.meego.com, Product: OS, Component: Virtual Keyboard ([https://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_based_on=virtual%20keyboard&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&component=Virtual%20keyboard&product=OS%20Base&known_name=virtual%20keyboard open bugs] |
[https://bugs.meego.com/enter_bug.cgi?product=OS%20Base&component=Virtual%20keyboard file new bug])

'''IRC:''' Visit us in #meego-inputmethods at freenode.net ([http://webchat.freenode.net/?randomnick=1&channels=meego-inputmethods&uio=d4 webchat])

== Social Media ==

'''Facebook: ''' [http://www.facebook.com/home.php?sk=group_127020324047804 Maliit group]

'''Twitter/Identica: ''' Use the #maliit hashtag

== Upcoming events ==
* August 6th-12th - Desktop Summit Berlin. Workshops & BoFs planned

== News ==
* 24.06.2011 - MeeGo Freeday presentation/workshop in Berlin. [http://meetmeego.org/2011/06/15/meego-freeday-24-06-2011/ Announcement] (in german), [[Media:Maliit-input-methods-for-meego.pdf|Slides]], [http://www.youtube.com/watch?v=kmR0J699oGA Video]
* 21.06.2011 - Nokia's N9 announced, with input methods powered by Maliit [http://www.youtube.com/watch?v=JOI5g129rtM Video]
* 20.06.2011 - First release (Maliit 0.80) as an independent project. [http://lists.meego.com/pipermail/meego-dev/2011-June/483526.html Announcement]
* 17.06.2011 - Session at Qt Collaborator Summit 2011. [http://developer.qt.nokia.com/groups/qt_contributors_summit/wiki/Input_methods_and_Wayland_in_Qt_5 Session summary]
* 24.05.2011 - Session at MeeGo Spring Conference 2011. [http://sf2011.meego.com/program/sessions/developing-custom-input-methods-meego Info, Recording]
* 08.04.2011 - MeeGo Keyboard is relicensed with BSD license: [http://lists.meego.com/pipermail/meego-dev/2011-April/482578.html Announcement]
* 29.03.2011 - Held first offical IRC meeting: [[Maliit/Meetings|How can we simplify development and maintenance of input contexts?]]
* 04.03.2011 - API/ABI break in 0.20.0: [http://lists.meego.com/pipermail/meego-dev/2011-March/481869.html meego-im-framework is removing dependency to libmeegotouch from its API]
* 23.02.2011 - Packages available for Ubuntu Lucid/Maverick to ease development. [http://taschenorakel.de/michael/2011/02/24/meego-input-methods-your-desktop/ Blogpost], [[#Packages for Ubuntu .2810.04 Lucid Lynx .2F 10.10 Maveric Meerkat.29|documentation]]
* 17.02.2011 - Claudio Saavedra started on MeeGo+Gtk integration work, focusing on input methods. [http://people.gnome.org/~csaavedra/news-2011-02.html#D10 Blogpost]
* 13.02.2011 - MeeGo Tablet UX demoed at Mobile World Conference, with Swype keyboard. [http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 Pictures]
* 01.02.2011 - API/ABI break in 0.19.41: [http://lists.meego.com/pipermail/meego-dev/2011-February/481353.html meegoimframework interfaces related to orientation change will be changed]
* 15.11.2010 - Architect and Lead Developer of Maliit give talk at MeeGo Conference. [http://conference2010.meego.com/session/meego-touch-input-method-frameworks Info, Recording]
* 15.11.2010 - Linpus shows off MeeGo based slate at MeeGo Conference, with keyboard based on Maliit.
* 30.06.2010 - MeeGo Handset UX Day 1 release, first public release of MeeGo Input Methods. [http://meego.com/community/blogs/valhalla/2010/meego-handset-project-day-1-here Announcement]

== Maliit in action ==

Maliit is used on a number of devices and form factors, and can easily be adapted to run on new ones.

* [http://www.linpus.com/products_meego_slate.html Linpus Slate] ([http://www.linpus.com/images/slate/kb.png screenshot showing Linpus virtual keyboard])
* [http://appdeveloper.intel.com/en-us/meego-iso-esla Intel MeeGo Tablet] ([http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 pictures showing Swype keyboard])
* [http://www.youtube.com/watch?v=l_7f3Lxd4_I GNOME3 on a WeTab (video)]
* [http://www.youtube.com/watch?v=JOI5g129rtM N9 and Swype integration (video)]
<gallery widths="250px" heights="250px" perrow="3">
Image:Lenovo_meego_vkb.jpg| [[Maliit/MeeGo 1.1#Netbook|MeeGo 1.1 Netbook]] with MeeGo Keyboard on Lenovo S10-3T Ideapad
Image:Meego1.1_handset_on_aava.jpg| [http://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo 1.1 Handset] with MeeGo Keyboard on Aava Mobile
Image:tegra-vkb2.jpg| MeeGo 1.2 prerelease on [[ARM/TEGRA2|Advent Vega, Tegra2]]
Image:Maliit-on-lucid.png | Ubuntu Lucid (10.04)
Image:Maliit-in-GNOME3.jpg | GNOME3 on a WeTab
Image:Maliit-on-KDE-Plasma.jpg | KDE, using Plasma
Image:Maliit-meego-ce-n900-landscape.jpg | MeeGo N900CE (landscape)
Image:Maliit-meego-ce-n900-portrait.jpg | MeeGo N900CE (portrait)
Image:Maliit_Nokia_N9.jpg | Nokia N9
</gallery>

{{MaliitNavigationBar}}

Maliit/Documentation

2011-06-29T13:16:46Z

Jonnor: /* Important cases */

[[Category:Maliit]][[Category:MeeGo Input Methods]]
{{MaliitNavigationBar}}

== FAQ ==
Frequently asked questions.

'''1. How to write my own input method?''' 
The recommended way to get started is to use the Maliit Plugin SDK and follow the [[Maliit/Documentation#Plugin_development_Quickstart|quickstart documentation]].

For developing an input method plugin, the primary interface is Qt and C++. The most relevant classes are: [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/minputmethodplugin.h MInputMethodPlugin],
[https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/mabstractinputmethod.h MAbstractInputMethod] and [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/mabstractinputmethodhost.h MAbstractInputMethodHost].

Since version 0.20.9-1 of the framework (May 2011), the MInputMethodQuick API allows one to also easily write input
methods using QML. See the [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/meego-keyboard-quick MeegoKeyboardQuick code] for an example.
As of May 2011 this interface is not yet feature complete with the C++ one. Contributions welcomed.

=== Unanswered questions ===
Please add any questions you may have here.

* Does Maliit work with non-compositing Window Managers?
* Which window managers are currently supported?

== Plugin Development Quickstart ==
How to get started developing plugins. This documentation is mainly for framework version 0.20.11-1 and newer. The C++ plugin API is compatible with all 0.20.x versions, and the QML interface is available from 0.20.9-1. Meego 1.2 has version 0.20.6. To develop there, one can install packages from Trunk/1.3.

Note that this is not intended to be 100% copy'n'paste step-by-step instructions. You may need to use common sense.

* [[Maliit/Installing|Install Maliit]] for your development environment
* [http://www.jonnor.com/files/maliit/maliit-plugin-sdk-0.1.0.tar.gz Download] the Maliit Plugin SDK
* Extract the examples
# In your favorite terminal:
tar -xf maliit-plugin-sdk-*.tar.gz
cd maliit-plugin-sdk/examples/
* Compile them
qmake
make
make install
* Have a look around. In the examples directory you will find a QML based plugin and a C++ based plugin.
# QML plugin code
ls plugins/quick/
# C++ plugin code
ls plugins/standard
* Try out one of the examples
# First enable both of the example input methods, along with the meego keyboard
gconftool-2 -s /meegotouch/inputmethods/onscreen/enabled -t list --list-type strings \
[libmeego-keyboard.so,en_gb.xml,libmeego-keyboard-quick.so,,libhelloworldplugin.so,,libexampleplugin.so,ExamplePluginSubview1]
# To activate the QML example
gconftool-2 -s /meegotouch/inputmethods/onscreen/active -t list --list-type string [libhelloworldplugin.so,]
# To instead activate the C++ example
gconftool-2 -s /meegotouch/inputmethods/onscreen/active -t list --list-type string [libexampleplugin.so,ExamplePluginSubview1]

# To test, start the Maliit server and a application with a Maliit inputcontext loaded
# Note: More documentation on this can be found on the Installing page
meego-im-uiserver > server.log &
QT_IM_MODULE=MInputContext apps/plainqt/plainqt

# Tap/double tap on a text field to activate the input method
# You should now be able to see an input method which allows you to click to input "Hello World"

* Try changing the plugin code a bit, and reinstall and restart the Maliit server to try again.
# Do changes (start simple, maybe by changing the "Hello World" string to something else)

# Rebuild and reinstall plugins
make && make install
# Remember to restart the Maliit server for it to pick up the changed plugin

If you have any issues, first try to solve the problem by reading the instructions again, and maybe other documentation. If you cannot solve it, ask for help through one of our communication channels.

There are also several open source input plugins that one look at. See for instance
* [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/m-keyboard Meego Keyboard]
* [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/meego-keyboard-quick Meego Keyboard Quick]
* [https://github.com/foolegg/cute-input-method/tree/n9 cute-input-method]

== Feature documentation ==
See [[Maliit#Features]]

== API documentation ==
* [http://apidocs.meego.com/1.1/platform/html/meego-im-framework/main.html Old MeeGo 1.1 Input method engine and framework] - note that there has been changes in API since then
* Documentation webpage for the latest git version and Meego version has been requested. See [https://bugs.meego.com/show_bug.cgi?id=14382 bug 14382] and [https://bugs.meego.com/show_bug.cgi?id=14994 bug 14994]
* Generate from source code with doxygen.

Some of the documentation is slighly outdated, and we are working to improve this. Use our [[Maliit#Communication_Channels|communication channels]] if there are any issues.

== Technical documentation ==
* [[Media:Technical-overview-widget-reloc.pdf|Widget relocation in MTF]]
* More to come!

== Blogposts et.c. ==
(most recent first)
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/06/20/brave-new-world/ Brave New World]
* Michael Hasselmannn: [http://taschenorakel.de/michael/2011/06/10/decent-examples-last/ Decent examples, at last!]
* Jon Nordby: [http://www.jonnor.com/2011/06/example-plugins-for-maliit-available/ Example plugins for Maliit]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/06/07/maliit-session-meego-spring-conference-2011/ Maliit Session at MeeGo Spring Conference 2011]
* Jan Arne Petersen: [http://blog.jpetersen.org/2011/05/29/maliit-packages-for-fedora/ Maliit packages for Fedora]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit/ Writing QML-based input methods for Maliit]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/05/10/painting-strategy-meegos-virtual-keyboard/ Painting Strategy in MeeGo's Virtual Keyboard]
* Jon Nordby: [http://www.jonnor.com/2011/04/introducing-maliit-on-screen-keyboard-in-gnome-3/ Introducing; Maliit on-screen keyboard in Gnome 3]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/04/10/customizing-meego-keyboard/ Customizing the Meego Keyboard]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/02/24/meego-input-methods-your-desktop/ MeeGo Input Methods for your desktop]

== Documentation working area ==
Here is the working area to keep track of the status of and work on the documentation.

* Goal: Every aspect of Maliit is well-documented, and the documentation easily accessible.
* Primary focus is on consumers of Maliit: Third-party developers and integrators

=== Important cases ===
* Creating and adding a new layout file to the keyboard
* Developing a new input method plugin
* Using Maliit in an application
* Integrating Maliit in a product
* Developing a new engine plugin
* Adding support for additional application toolkits

=== Documentation status ===

{|border="1" cellpadding="4" class="wikitable"
|-
! Item
! Status
! Description
|-
| wiki.meego.com/Maliit || 90% || Our public webpage/wiki page, starting point for all information about our project. In pretty good shape.
|-
| apidocs.meego.com/git-tip || 10% || Our docs should be shown here. [https://bugs.meego.com/show_bug.cgi?id=14382 Bug 14382]
|-
| apidocs.meego.com/1.2 || 10% || Our docs should be shown here. [https://bugs.meego.com/show_bug.cgi?id=14994 Bug 14994]
|-
| colspan=3 | '''Framework'''
|-
| Overall architecture || 30% || Some docs exists in framework source tree, but is very outdated
|-
| Input Method/framework settings system || 0% ||
|-
| Input Method Plugin<->Framework interaction || 0% || What the interaction concepts are (both user and technical), and what is done on each side to support this
|-
| Input Method Framework Window handling || 0% || Passthrough window, Self-compositing, plugin pixmap drawing, rotation animation. Maybe covered by above item?
|-
| Input Method Plugin API || 60% || Example plugins exists, initial plugin SDK published. Need to remove the outdated tutorial from framework docs
|-
| Input Context DBus API || 0% ||
|-
| Toolkit integration concepts || 20% || Key concepts like pre-edit injection, and widget relocation should be documented. Purpose: make it easy for others to improve toolkit integration, and to bring new people up to date. Widget relocation is documented.
|-
| Toolkit integration/support status || 10% || Implicitly all keyboard features/IM are available for MTF. No documentation about plain Qt, QML, Clutter or Gtk+
|-
| Engine interfaces || ? || Correction/prediction/suggestion/handwriting, both plugin side and IM side
|-
| Feedback framework || ? ||
|-
| colspan=3 | '''Plugins'''
|-
| Meego Keyboard theming (CSS) || 100% || Docs in keyboard source tree. ||
|-
| Meego Keyboard layouts || 100% || Docs in keyboard source tree. ||
|-
| Meego Keyboard features || 100% || Documented on wiki page. ||
|-
|}

{{MaliitNavigationBar}}

Maliit/Development

2011-06-27T11:16:45Z

Jonnor: /* Repositories */ remove engines, right now there is nothing there

{{MaliitNavigationBar}}

== Repositories ==
* [https://gitorious.org/maliit/maliit-framework Maliit framework]:<pre>git clone git@gitorious.org:maliit/maliit-framework.git</pre>
* [https://gitorious.org/maliit/maliit-plugins Maliit plugins (virtual keyboards etc.)]:<pre>git clone git@gitorious.org:maliit/maliit-plugins.git</pre>

For MeeGo 1.2, use the following branches instead of master:
* https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/commits/meego-1.2
* https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/commits/meego-1.2

== Releases ==
* Howtos: [[Maliit/Making_a_Release|Making a release]], [[Maliit/Writing_Release_Notes|Writing release notes]]
* 0.80.0 - Brave New World: [http://lists.meego.com/pipermail/meego-dev/2011-June/483526.html Release notes], [http://gitorious.org/maliit/maliit-framework/archive-tarball/0.80.0 framework tarball], [http://gitorious.org/maliit/maliit-plugins/archive-tarball/0.80.0 plugins tarball].

== Contributing ==
We use gitorious to handle patches and reviews. Clone our repository, and create a merge request with the commits you want merged. As a general rule, do not send patches to the mailinglist.

If you are implementing a new feature, it is smart to discuss it on the mailing list first.
If you have a fix for a bug that affects Meego, file a bugreport at bugs.meego.com and link your merge request there.

We currently do not have a concrete policy for giving out commit rights to the mainline repositories. However, it is our intention that contributors
that builds up a track record with the project are able to get commit rights.
Do note that also those who have commit rights have to submit and get their merge requests reviewed prior to changes going in.

== Open bug reports ==

{{#bugzilla:
|columns=id,status,to,severity,version,summary
|group=priority
|grouporder=asc
|component=Virtual keyboard
|product=OS Base
|status=UNCONFIRMED,NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED
|lastcomment=1
}}

== Bugreports, patches and merge requests in other projects ==
This area is for keeping track of things that concern Maliit or is done by the Maliit team in related projects.

* [https://bugzilla.novell.com/show_bug.cgi?id=701523 Maliit openSUSE OBS project request]
* [https://bugs.freedesktop.org/show_bug.cgi?id=38563 Maliit project request on freedesktop.org]

== Meego packaging ==
* [http://build.meego.com/project/monitor?commit=Filter%3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&pkgname=inputmethod&repo_standard=1&repo_weekly=1&arch_armv7el=1&arch_armv8el=1&arch_i586=1&project=Trunk&defaults=0 Status in Trunk]
* [http://build.meego.com/project/monitor?commit=Filter%3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&pkgname=inputmethod&repo_standard=1&arch_armv8el=1&arch_i586=1&project=MeeGo%3A1.2%3Aoss&defaults=0 Status in 1.2]
* [http://build.meego.com/project/monitor?commit=Filter%3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&pkgname=inputmethod&repo_standard=1&arch_armv7el=1&arch_i586=1&lastbuild=1&project=MeeGo%3A1.1%3ACore&defaults=0 Status in 1.1]

== QA Reports ==

Latest inputmethod packages QA reports using recent Meego images can be found at the [http://qa-reports.meego.com/1.2/Handset/Basic%20Feature%20Testing/N900 QA Basic Feature Testing] section of [http://qa-reports.meego.com http://qa-reports.meego.com].

== Maliit google searches ==
References to Maliit from other places on the web. Search used: maliit keyboard OR "input method" OR meego -ang

* [http://www.google.de/search?q=maliit+keyboard+OR+%22input+method%22+OR+meego+-ang&hl=en&client=firefox-a&hs=HdI&tbo=1&rls=org.mozilla%3Aen-US%3Aunofficial&num=10&lr=&ft=i&cr=&safe=images&tbs=#q=maliit+keyboard+OR+%22input+method%22+OR+meego+-ang&hl=en&lr=&client=firefox-a&hs=kfI&tbo=1&rls=org.mozilla:en-US:unofficial&prmd=ivns&ei=1XDeTf-CEtHIswb5sbXLBQ&start=0&sa=N&bav=on.2,or.r_gc.r_pw.&fp=bf4289d263b569cc&biw=1302&bih=937 Webpages]
* [http://www.google.de/search?q=maliit+keyboard+OR+%22input+method%22+OR+meego+-ang&hl=en&lr=&client=firefox-a&hs=f0x&tbo=1&rls=org.mozilla:en-US:unofficial&biw=1302&bih=937&prmdo=1&tbm=dsc&prmd=ivns&source=lnms&ei=6HDeTeOzMYXs-gaQuYXvCQ&sa=X&oi=mode_link&ct=mode&ved=0CBcQ_AU Discussions]
* [http://www.google.de/search?q=maliit+keyboard+OR+%22input+method%22+OR+meego+-ang&hl=en&lr=&client=firefox-a&hs=S0x&tbo=1&rls=org.mozilla:en-US:unofficial&biw=1302&bih=937&prmd=ivns&source=lnms&tbm=mbl&ei=23DeTZGDCcrHswbUwbzLBQ&sa=X&oi=mode_link&ct=mode&cd=9&ved=0CCAQ_AUoCA&prmdo=1 Realtime]
* [http://www.google.de/search?q=maliit+keyboard+OR+%22input+method%22+OR+meego+-ang&hl=en&lr=&client=firefox-a&hs=S0x&tbo=1&rls=org.mozilla:en-US:unofficial&biw=1302&bih=937&prmd=ivns&source=lnms&tbm=blg&ei=23DeTZGDCcrHswbUwbzLBQ&sa=X&oi=mode_link&ct=mode&cd=8&ved=0CB8Q_AUoBw&prmdo=1 Blogs]

{{MaliitNavigationBar}}

Maliit/Development

2011-06-27T11:15:03Z

Jonnor:

{{MaliitNavigationBar}}

== Repositories ==
* [https://gitorious.org/maliit/maliit-framework Maliit framework]:<pre>git clone git@gitorious.org:maliit/maliit-framework.git</pre>
* [https://gitorious.org/maliit/maliit-engines Maliit engines]:<pre>git clone git@gitorious.org:maliit/maliit-engines.git</pre>
* [https://gitorious.org/maliit/maliit-plugins Maliit plugins (virtual keyboards etc.)]:<pre>git clone git@gitorious.org:maliit/maliit-plugins.git</pre>

For MeeGo 1.2, use the following branches instead of master:
* https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/commits/meego-1.2
* https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/commits/meego-1.2

== Releases ==
* Howtos: [[Maliit/Making_a_Release|Making a release]], [[Maliit/Writing_Release_Notes|Writing release notes]]
* 0.80.0 - Brave New World: [http://lists.meego.com/pipermail/meego-dev/2011-June/483526.html Release notes], [http://gitorious.org/maliit/maliit-framework/archive-tarball/0.80.0 framework tarball], [http://gitorious.org/maliit/maliit-plugins/archive-tarball/0.80.0 plugins tarball].

== Contributing ==
We use gitorious to handle patches and reviews. Clone our repository, and create a merge request with the commits you want merged. As a general rule, do not send patches to the mailinglist.

If you are implementing a new feature, it is smart to discuss it on the mailing list first.
If you have a fix for a bug that affects Meego, file a bugreport at bugs.meego.com and link your merge request there.

We currently do not have a concrete policy for giving out commit rights to the mainline repositories. However, it is our intention that contributors
that builds up a track record with the project are able to get commit rights.
Do note that also those who have commit rights have to submit and get their merge requests reviewed prior to changes going in.

== Open bug reports ==

{{#bugzilla:
|columns=id,status,to,severity,version,summary
|group=priority
|grouporder=asc
|component=Virtual keyboard
|product=OS Base
|status=UNCONFIRMED,NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED
|lastcomment=1
}}

== Bugreports, patches and merge requests in other projects ==
This area is for keeping track of things that concern Maliit or is done by the Maliit team in related projects.

* [https://bugzilla.novell.com/show_bug.cgi?id=701523 Maliit openSUSE OBS project request]
* [https://bugs.freedesktop.org/show_bug.cgi?id=38563 Maliit project request on freedesktop.org]

== Meego packaging ==
* [http://build.meego.com/project/monitor?commit=Filter%3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&pkgname=inputmethod&repo_standard=1&repo_weekly=1&arch_armv7el=1&arch_armv8el=1&arch_i586=1&project=Trunk&defaults=0 Status in Trunk]
* [http://build.meego.com/project/monitor?commit=Filter%3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&pkgname=inputmethod&repo_standard=1&arch_armv8el=1&arch_i586=1&project=MeeGo%3A1.2%3Aoss&defaults=0 Status in 1.2]
* [http://build.meego.com/project/monitor?commit=Filter%3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&pkgname=inputmethod&repo_standard=1&arch_armv7el=1&arch_i586=1&lastbuild=1&project=MeeGo%3A1.1%3ACore&defaults=0 Status in 1.1]

== QA Reports ==

Latest inputmethod packages QA reports using recent Meego images can be found at the [http://qa-reports.meego.com/1.2/Handset/Basic%20Feature%20Testing/N900 QA Basic Feature Testing] section of [http://qa-reports.meego.com http://qa-reports.meego.com].

== Maliit google searches ==
References to Maliit from other places on the web. Search used: maliit keyboard OR "input method" OR meego -ang

* [http://www.google.de/search?q=maliit+keyboard+OR+%22input+method%22+OR+meego+-ang&hl=en&client=firefox-a&hs=HdI&tbo=1&rls=org.mozilla%3Aen-US%3Aunofficial&num=10&lr=&ft=i&cr=&safe=images&tbs=#q=maliit+keyboard+OR+%22input+method%22+OR+meego+-ang&hl=en&lr=&client=firefox-a&hs=kfI&tbo=1&rls=org.mozilla:en-US:unofficial&prmd=ivns&ei=1XDeTf-CEtHIswb5sbXLBQ&start=0&sa=N&bav=on.2,or.r_gc.r_pw.&fp=bf4289d263b569cc&biw=1302&bih=937 Webpages]
* [http://www.google.de/search?q=maliit+keyboard+OR+%22input+method%22+OR+meego+-ang&hl=en&lr=&client=firefox-a&hs=f0x&tbo=1&rls=org.mozilla:en-US:unofficial&biw=1302&bih=937&prmdo=1&tbm=dsc&prmd=ivns&source=lnms&ei=6HDeTeOzMYXs-gaQuYXvCQ&sa=X&oi=mode_link&ct=mode&ved=0CBcQ_AU Discussions]
* [http://www.google.de/search?q=maliit+keyboard+OR+%22input+method%22+OR+meego+-ang&hl=en&lr=&client=firefox-a&hs=S0x&tbo=1&rls=org.mozilla:en-US:unofficial&biw=1302&bih=937&prmd=ivns&source=lnms&tbm=mbl&ei=23DeTZGDCcrHswbUwbzLBQ&sa=X&oi=mode_link&ct=mode&cd=9&ved=0CCAQ_AUoCA&prmdo=1 Realtime]
* [http://www.google.de/search?q=maliit+keyboard+OR+%22input+method%22+OR+meego+-ang&hl=en&lr=&client=firefox-a&hs=S0x&tbo=1&rls=org.mozilla:en-US:unofficial&biw=1302&bih=937&prmd=ivns&source=lnms&tbm=blg&ei=23DeTZGDCcrHswbUwbzLBQ&sa=X&oi=mode_link&ct=mode&cd=8&ved=0CB8Q_AUoBw&prmdo=1 Blogs]

{{MaliitNavigationBar}}

Maliit/Roadmap

2011-06-27T11:04:41Z

Jonnor: /* Maliit 1.0 */ link roadmap item to bugreport

{{MaliitNavigationBar}}

Submit your ideas in [[Maliit/Ideas|Ideas page]] to get considered to be put into the roadmap.

== Maliit 1.0 ==
Development in progress.

With Maliit 1.0 the goal is long-term API stability for application and input method plugin API.

* '''0.2x''': Still uses MeeGo Touch. (DONE)
* '''0.8x''': Compiles MeeGo Touch free version by default, has legacy build option. (DONE)
** Maliit now an [http://lists.meego.com/pipermail/meego-dev/2011-June/483406.html independent project].
** Installation paths, library names and GConf keys now follow new Maliit naming conventions.
** Legacy LMT build can be done using qmake CONFIG+=nomeegotouch (works in -framework and -plugins repo).
** No API changes in plugin or application API! New library structure will require recompilation though.
* '''0.9x''': Alpha release that will lead up to Maliit 1.0
** Will contain API cleanups (not LMT related, but rather about removing cruft and cleanup).
** API cleanup should be done for all Maliit libraries (including engines and feedback API).
** In first release for the 0.9x series, the C++ based reference VKB (Maliit Keyboard) will be LMT-free.
* '''1.0''': Stable release

=== Framework ===
* Use D-Bus datatype instead of serialized Qt types in D-Bus API (DONE)
* [[Maliit/Ideas/Supporting_Non_X11_Platforms|Support for non X11 platform]]
* [https://bugs.meego.com/show_bug.cgi?id=20076 Meego Touch independent application API]
* Unified, UI independent, settings API
** Probably even hide the framework's GConf usage behind some API that can be used by apps and plugins.

=== MeeGo Keyboard ===
* Key magnification and accent pop-ups (DONE)
* New word prediction widgets: Word Ribbon (DONE)
* Extended support for CJK languages
* Remove libmeegotouch dependency

= Platforms =
== MeeGo 1.3 ==
Development in in progress.

MeeGo 1.3 will have Maliit 1.0.

* New maliit-* package-names (DONE)
* Settings applet for meego-ux-settings
* Better integration with standard applications

== MeeGo 1.2 ==
All items in this section are DONE.

=== Framework ===
* private D-Bus connection
* new information exposures:
** anchor position
** cursor position
* libmeegotouch removal
* self-compositing
* self-rotation animation

=== Engine framework ===
* New interface: Handwriting recognition
* New functionality: Dynamic virtual keyboard layout

[[Category:Maliit]]
[[Category:MeeGo Input Methods]]

{{MaliitNavigationBar}}

Maliit/Meetings

2011-06-27T10:57:05Z

Jonnor:

== MeeGo Input Methods IRC meeting, March 29th 2011 ==

=== How can we simplify development and maintenance of input contexts? ===

Participants: Michael Hasselmann (Openismus), Jon Nordby (Openismus), Andy Ross (Windriver), Pekka Vuorela (Nokia), Gary Birkett (Collabora), Robin Burchell (Collabora)

Log: http://lists.meego.com/pipermail/meego-inputmethods/2011-March/000037.html

The outcome of this meeting were the following tasks:

{| border="0" cellpadding="4" class="wikitable"
! Task !! Assignee !! Status !! Details
|-
| Alternative for MInputMethodState || [https://bugs.meego.com/show_bug.cgi?id=20076 BMC#20076] || in progress || We need to provide a fully working alternative for MInputMethodState. And this would also fit with our plans to offer better support for plain Qt, QML, Qt Components (and GTK+ on MeeGo). We can decide to add the less important features (toolbar and keyboard customization) at a later point, for example.
|-
| Decide on where to put extended API || [https://bugs.meego.com/show_bug.cgi?id=20076 BMC#20076] || done || No agreement yet on whether it's better to provide needed API through signals/slots in inputcontext or whether it's better to provide a separate library (in MeeGo Input Methods itself). Andy Ross is supposed to kick off the discussion on the public ML (check next week).
|-
| Clean up D-Bus API || Maksim Kirillov || done || We clean up the D-Bus API, instead of further abstraction. We will use native D-Bus types instead of (serialized) Qt datatypes.
|-
| Check QtDBus status in Qt 4.8 || [https://qt.gitorious.org/qt/qt/merge_requests/2343 MRQ#2343] || done || Check QtDBus situation in 4.8 and switch to Qt's D-Bus interface, if possible. We need working P2P D-Bus.
|-
| Provide documentation for D-Bus API || [[Maliit/Documentation#Documentation_working_area|moved here]] || punted || Obvious. Currently no overview of its intent or how it actually works, only documentation on the methods itself.
|}

[[Category:Maliit]]

Maliit

2011-06-27T10:44:52Z

Jonnor: /* News */ add Meego Freeday video

{{MaliitNavigationBar}}

[[File:Maliit2.png|448px|link=]]

Maliit provides a flexible and cross-platform input method framework, including a virtual keyboard. It works on all MeeGo user experiences, and in other GNU/Linux distributions.

== Goals ==

Maliit aims to be ''the'' input method project for MeeGo and other GNU/Linux-based embedded/mobile platforms. To achieve this we should provide:

'''A solid input method framework'''

This includes support for traditional input methods such as hardware and virtual keyboards. More exotic input methods should also be possible, such as handwriting recognition and voice input, and special purpose input methods such as date/time pickers, tag clouds, etc.

'''A core set of input methods'''

The default set of input methods should demonstrate the core capabilities of the framework and provide a good user experience that device manufacturers and integrators can use easily.

We also aim to:

'''Empower third-party developers'''

Customizing existing input methods or developing powerful new input methods should be simple, regardless of whether it is for profit, research or fun.

'''Build a diverse community of contributors'''

Employees from different companies, freelancers, members of academia, hackers and volunteers should all be welcomed and encouraged to contribute to the project.

== Communication channels ==

'''Mailing list:''' meego-inputmethods@lists.meego.com ([http://lists.meego.com/listinfo/meego-inputmethods listinfo] | [http://lists.meego.com/pipermail/meego-inputmethods/ archives])

'''Bugtracker:''' bugs.meego.com, Product: OS, Component: Virtual Keyboard ([https://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_based_on=virtual%20keyboard&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&component=Virtual%20keyboard&product=OS%20Base&known_name=virtual%20keyboard open bugs] |
[https://bugs.meego.com/enter_bug.cgi?product=OS%20Base&component=Virtual%20keyboard file new bug])

'''IRC:''' Visit us in #meego-inputmethods at freenode.net ([http://webchat.freenode.net/?randomnick=1&channels=meego-inputmethods&uio=d4 webchat])

== Upcoming events ==
* August 6th-12th - Desktop Summit Berlin. Workshops & BoFs planned

== News ==
* 24.06.2011 - MeeGo Freeday presentation/workshop in Berlin. [http://meetmeego.org/2011/06/15/meego-freeday-24-06-2011/ Announcement] (in german), [[Media:Maliit-input-methods-for-meego.pdf|Slides]], [http://www.youtube.com/watch?v=kmR0J699oGA Video]
* 20.06.2011 - First release (Maliit 0.80) as an independent project. [http://lists.meego.com/pipermail/meego-dev/2011-June/483526.html Announcement]
* 17.06.2011 - Session at Qt Collaborator Summit 2011. [http://developer.qt.nokia.com/groups/qt_contributors_summit/wiki/Input_methods_and_Wayland_in_Qt_5 Session summary]
* 07.06.2011 - Session at MeeGo Spring Conference 2011. [http://sf2011.meego.com/program/sessions/developing-custom-input-methods-meego Info, Recording]
* 08.04.2011 - MeeGo Keyboard is relicensed with BSD license: [http://lists.meego.com/pipermail/meego-dev/2011-April/482578.html Announcement]
* 29.03.2011 - Held first offical IRC meeting: [[Maliit/Meetings|How can we simplify development and maintenance of input contexts?]]
* 04.03.2011 - API/ABI break in 0.20.0: [http://lists.meego.com/pipermail/meego-dev/2011-March/481869.html meego-im-framework is removing dependency to libmeegotouch from its API]
* 23.02.2011 - Packages available for Ubuntu Lucid/Maverick to ease development. [http://taschenorakel.de/michael/2011/02/24/meego-input-methods-your-desktop/ Blogpost], [[#Packages for Ubuntu .2810.04 Lucid Lynx .2F 10.10 Maveric Meerkat.29|documentation]]
* 17.02.2011 - Claudio Saavedra started on MeeGo+Gtk integration work, focusing on input methods. [http://people.gnome.org/~csaavedra/news-2011-02.html#D10 Blogpost]
* 13.02.2011 - MeeGo Tablet UX demoed at Mobile World Conference, with Swype keyboard. [http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 Pictures]
* 01.02.2011 - API/ABI break in 0.19.41: [http://lists.meego.com/pipermail/meego-dev/2011-February/481353.html meegoimframework interfaces related to orientation change will be changed]
* 15.11.2010 - Architect and Lead Developer of Maliit give talk at MeeGo Conference. [http://conference2010.meego.com/session/meego-touch-input-method-frameworks Info, Recording]
* 15.11.2010 - Linpus shows off MeeGo based slate at MeeGo Conference, with keyboard based on Maliit.
* 30.06.2010 - MeeGo Handset UX Day 1 release, first public release of MeeGo Input Methods. [http://meego.com/community/blogs/valhalla/2010/meego-handset-project-day-1-here Announcement]

== Maliit in action ==

Maliit is used on a number of devices and form factors, and can easily be adapted to run on new ones.

* [http://www.linpus.com/products_meego_slate.html Linpus Slate] ([http://www.linpus.com/images/slate/kb.png screenshot showing Linpus virtual keyboard])
* [http://appdeveloper.intel.com/en-us/meego-iso-esla Intel MeeGo Tablet] ([http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 pictures showing Swype keyboard])
* [http://www.youtube.com/watch?v=l_7f3Lxd4_I GNOME3 on a WeTab (video)]
* [http://www.youtube.com/watch?v=JOI5g129rtM N9 and Swype integration (video)]
<gallery widths="250px" heights="250px" perrow="3">
Image:Lenovo_meego_vkb.jpg| [[Maliit/MeeGo 1.1#Netbook|MeeGo 1.1 Netbook]] with MeeGo Keyboard on Lenovo S10-3T Ideapad
Image:Meego1.1_handset_on_aava.jpg| [http://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo 1.1 Handset] with MeeGo Keyboard on Aava Mobile
Image:tegra-vkb2.jpg| MeeGo 1.2 prerelease on [[ARM/TEGRA2|Advent Vega, Tegra2]]
Image:Maliit-on-lucid.png | Ubuntu Lucid (10.04)
Image:Maliit-in-GNOME3.jpg | GNOME3 on a WeTab
Image:Maliit-on-KDE-Plasma.jpg | KDE, using Plasma
Image:Maliit-meego-ce-n900-landscape.jpg | MeeGo N900CE (landscape)
Image:Maliit-meego-ce-n900-portrait.jpg | MeeGo N900CE (portrait)
[[File:TransparentPlaceholder.png|link=http://wikipedia.org|caption]]
</gallery>

{{MaliitNavigationBar}}

Maliit/Roadmap

2011-06-27T10:33:44Z

Jonnor: Move Meego sections under "platforms"

{{MaliitNavigationBar}}

Submit your ideas in [[Maliit/Ideas|Ideas page]] to get considered to be put into the roadmap.

== Maliit 1.0 ==
Development in progress.

With Maliit 1.0 the goal is long-term API stability for application and input method plugin API.

* '''0.2x''': Still uses MeeGo Touch.
* '''0.8x''': Compiles MeeGo Touch free version by default, has legacy build option. (DONE)
** Maliit now an [http://lists.meego.com/pipermail/meego-dev/2011-June/483406.html independent project].
** Installation paths, library names and GConf keys now follow new Maliit naming conventions.
** Legacy LMT build can be done using qmake CONFIG+=nomeegotouch (works in -framework and -plugins repo).
** No API changes in plugin or application API! New library structure will require recompilation though.
* '''0.9x''': Alpha release that will lead up to Maliit 1.0
** Will contain API cleanups (not LMT related, but rather about removing cruft and cleanup).
** API cleanup should be done for all Maliit libraries (including engines and feedback API).
** In first release for the 0.9x series, the C++ based reference VKB (Maliit Keyboard) will be LMT-free.
* '''1.0''': Stable release

=== Framework ===
* Use D-Bus datatype instead of serialized Qt types in D-Bus API (DONE)
* [[Maliit/Ideas/Supporting_Non_X11_Platforms|Support for non X11 platform]]
* Better support for Qt applications not linked to MeeGo Touch
** Orientation change
* Unified, UI independent, settings API
** Probably even hide the framework's GConf usage behind some API that can be used by apps and plugins.

=== MeeGo Keyboard ===
* Key magnification and accent pop-ups (DONE)
* New word prediction widgets: Word Ribbon (DONE)
* Extended support for CJK languages
* Remove libmeegotouch dependency

= Platforms =
== MeeGo 1.3 ==
Development in in progress.

MeeGo 1.3 will have Maliit 1.0.

* New maliit-* package-names (DONE)
* Settings applet for meego-ux-settings
* Better integration with standard applications

== MeeGo 1.2 ==
All items in this section are DONE.

=== Framework ===
* private D-Bus connection
* new information exposures:
** anchor position
** cursor position
* libmeegotouch removal
* self-compositing
* self-rotation animation

=== Engine framework ===
* New interface: Handwriting recognition
* New functionality: Dynamic virtual keyboard layout

[[Category:Maliit]]
[[Category:MeeGo Input Methods]]

{{MaliitNavigationBar}}

Maliit

2011-06-24T20:51:49Z

Jonnor: update event/news - Meego Freeday 24 June

{{MaliitNavigationBar}}

[[File:Maliit2.png|448px|link=]]

Maliit provides a flexible and cross-platform input method framework, including a virtual keyboard. It works on all MeeGo user experiences, and in other GNU/Linux distributions.

== Goals ==

Maliit aims to be ''the'' input method project for MeeGo and other GNU/Linux-based embedded/mobile platforms. To achieve this we should provide:

'''A solid input method framework'''

This includes support for traditional input methods such as hardware and virtual keyboards. More exotic input methods should also be possible, such as handwriting recognition and voice input, and special purpose input methods such as date/time pickers, tag clouds, etc.

'''A core set of input methods'''

The default set of input methods should demonstrate the core capabilities of the framework and provide a good user experience that device manufacturers and integrators can use easily.

We also aim to:

'''Empower third-party developers'''

Customizing existing input methods or developing powerful new input methods should be simple, regardless of whether it is for profit, research or fun.

'''Build a diverse community of contributors'''

Employees from different companies, freelancers, members of academia, hackers and volunteers should all be welcomed and encouraged to contribute to the project.

== Communication channels ==

'''Mailing list:''' meego-inputmethods@lists.meego.com ([http://lists.meego.com/listinfo/meego-inputmethods listinfo] | [http://lists.meego.com/pipermail/meego-inputmethods/ archives])

'''Bugtracker:''' bugs.meego.com, Product: OS, Component: Virtual Keyboard ([https://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_based_on=virtual%20keyboard&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&component=Virtual%20keyboard&product=OS%20Base&known_name=virtual%20keyboard open bugs] |
[https://bugs.meego.com/enter_bug.cgi?product=OS%20Base&component=Virtual%20keyboard file new bug])

'''IRC:''' Visit us in #meego-inputmethods at freenode.net ([http://webchat.freenode.net/?randomnick=1&channels=meego-inputmethods&uio=d4 webchat])

== Upcoming events ==
* August 6th-12th - Desktop Summit Berlin. Workshops & BoFs planned

== News ==
* 24.06.2011 - MeeGo Freeday workshop in Berlin. [http://meetmeego.org/2011/06/15/meego-freeday-24-06-2011/ Announcement] (in german)
* 20.06.2011 - First release (Maliit 0.80) as an independent project. [http://lists.meego.com/pipermail/meego-dev/2011-June/483526.html Announcement]
* 17.06.2011 - Session at Qt Collaborator Summit 2011. [http://developer.qt.nokia.com/groups/qt_contributors_summit/wiki/Input_methods_and_Wayland_in_Qt_5 Session summary]
* 07.06.2011 - Session at MeeGo Spring Conference 2011. [http://sf2011.meego.com/program/sessions/developing-custom-input-methods-meego Info, Recording]
* 08.04.2011 - MeeGo Keyboard is relicensed with BSD license: [http://lists.meego.com/pipermail/meego-dev/2011-April/482578.html Announcement]
* 29.03.2011 - Held first offical IRC meeting: [[Maliit/Meetings|How can we simplify development and maintenance of input contexts?]]
* 04.03.2011 - API/ABI break in 0.20.0: [http://lists.meego.com/pipermail/meego-dev/2011-March/481869.html meego-im-framework is removing dependency to libmeegotouch from its API]
* 23.02.2011 - Packages available for Ubuntu Lucid/Maverick to ease development. [http://taschenorakel.de/michael/2011/02/24/meego-input-methods-your-desktop/ Blogpost], [[#Packages for Ubuntu .2810.04 Lucid Lynx .2F 10.10 Maveric Meerkat.29|documentation]]
* 17.02.2011 - Claudio Saavedra started on MeeGo+Gtk integration work, focusing on input methods. [http://people.gnome.org/~csaavedra/news-2011-02.html#D10 Blogpost]
* 13.02.2011 - MeeGo Tablet UX demoed at Mobile World Conference, with Swype keyboard. [http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 Pictures]
* 01.02.2011 - API/ABI break in 0.19.41: [http://lists.meego.com/pipermail/meego-dev/2011-February/481353.html meegoimframework interfaces related to orientation change will be changed]
* 15.11.2010 - Architect and Lead Developer of Maliit give talk at MeeGo Conference. [http://conference2010.meego.com/session/meego-touch-input-method-frameworks Info, Recording]
* 15.11.2010 - Linpus shows off MeeGo based slate at MeeGo Conference, with keyboard based on Maliit.
* 30.06.2010 - MeeGo Handset UX Day 1 release, first public release of MeeGo Input Methods. [http://meego.com/community/blogs/valhalla/2010/meego-handset-project-day-1-here Announcement]

== Maliit in action ==

Maliit is used on a number of devices and form factors, and can easily be adapted to run on new ones.

* [http://www.linpus.com/products_meego_slate.html Linpus Slate] ([http://www.linpus.com/images/slate/kb.png screenshot showing Linpus virtual keyboard])
* [http://appdeveloper.intel.com/en-us/meego-iso-esla Intel MeeGo Tablet] ([http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 pictures showing Swype keyboard])
* [http://www.youtube.com/watch?v=l_7f3Lxd4_I GNOME3 on a WeTab (video)]
* [http://www.youtube.com/watch?v=JOI5g129rtM N9 and Swype integration (video)]

<gallery widths="250px" heights="250px" perrow="3">
Image:Lenovo_meego_vkb.jpg| [[Maliit/MeeGo 1.1#Netbook|MeeGo 1.1 Netbook]] with MeeGo Keyboard on Lenovo S10-3T Ideapad
Image:Meego1.1_handset_on_aava.jpg| [http://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo 1.1 Handset] with MeeGo Keyboard on Aava Mobile
Image:tegra-vkb2.jpg| MeeGo 1.2 prerelease on [[ARM/TEGRA2|Advent Vega, Tegra2]]
Image:Maliit-on-lucid.png | Ubuntu Lucid (10.04)
Image:Maliit-in-GNOME3.jpg | GNOME3 on a WeTab
Image:Maliit-on-KDE-Plasma.jpg | KDE, using Plasma
[[File:TransparentPlaceholder.png|link=http://wikipedia.org|caption]]
</gallery>

{{MaliitNavigationBar}}

Maliit/Ideas

2011-06-24T20:31:43Z

Jonnor: /* Other */ add details to Bluetooth

{{MaliitNavigationBar}}

Here are some ideas for what you could do with Maliit. Some are things we really want to get done (but have not committed to), some are down-to-earth nice-to-have, while others are perhaps a bit more in the crazy, experimental or show-that-it-can-be-done spirit. Feel free to add ideas here. Use the template idea if you want. For bugs or concrete features suggestions, please use the bugtracker.

=== Template Idea ===
Short description of the idea.

'''Difficulty/effort:''' How much work does it take to complete this (assuming a Maliit dev. environent is already set up) Example: Easy, 5 hours of work 
'''Status:''' What is the status of implementing this idea? Example: "In progress, this and that has been done" 
'''Skills required:''' What do people need to know in order to complete the implementation of this idea? Example: Qt | Packaging | Gtk+ | QML 
'''Contact person:''' Who interested people should contact if they want to work on this. This can be a "mentor" that has insight into the relevant areas, or someone who has started working on it. Example: Real Name (ircnick) 

Longer description. Ideas, challenges, and considerations for the implementation. Neccesary tasks to complete. Links to other relevant projects or work. Mockups, video demos, et.c.

== Meego Keyboard Ideas ==

=== Key gestures ===
Input variations of a character using gestures on that key. For instance, to input a upper case A, tap 'a', move upward and release. Accented characters can be done by gesturing sideways.

=== Predictive keyboard ===
Details of idea can be found under [[Predictive_virtual_keyboard]].

'''Difficulty/effort:''' Easy, 10 hours of work 
'''Skills required:''' Meego keyboard, Qt, C++ 
'''Status:''' Experimental merge request available 
'''Contact person:''' Michael Hasselmann (mikhas)

Experimental MRQ available: https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/merge_requests/269

Screenshot/demo video pleaz?
-- Was demonstrated during the Meego Conference San Fransisco talk. Video will hopefully become available

=== Disable invalid keys ===
Mark keys for invalid input characters as "disabled" in the keyboard.

'''Difficulty/effort:''' Simple, 10 hours of work 
'''Skills required:''' Meego keyboard, Qt, C++ 
'''Status:''' Just talk! 
'''Contact person: Jon Nordby (jonnor)'''

Often toolkits will disallow certains characters to be inputted in certain fields. For instance in an URL field or email field, certain characters are invalid. Typically this is indicated by some sort of visual "error" state after the user has tried to input the character. However, it would be nicer if the keyboard would "grey out" or disable keys that are invalid.

This will require the application to transfer the sets of valid (or invalid) characters to the input method, and for the keyboard to disable keys based on this information. This could be done with a JSON string over the extended attributes perhaps. If it is not possible for the application to enumerate all invalid characters, then the input method might have to first inform the application about which characters are available, and then the application tells which of those are invalid.

== Input Method (plugin) Ideas ==

=== Dasher input method ===
Allow input using a [[:wikipedia:Dasher|Dasher]] input method.

'''Difficulty/effort:''' Unknown, 25 hours of work? 
'''Skills required:''' C/C++, Qt, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

Dasher is a simple but innovative way of doing text input, a for this plugin would be very useful, especially for accessibility.
Dasher already has a Qt based UI, so it might be possible to reuse large parts of the code.

* [http://git.gnome.org/browse/dasher/ Homepage]
* [http://git.gnome.org/browse/dasher/ Repository]
* [https://bugzilla.gnome.org/browse.cgi?product=dasher Bugtracker]

=== Tag cloud input method ===
'''Difficulty/effort:''' Simple?, 10 hours of work? 
'''Skills required:''' C/C++, Qt, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

Use the extension attribute API to allow an application to specify a resource that the input method should present.
Perhaps it could use a SPARQL query string somehow and use tracker? Or just a JSON dictionary with key=tagname and value=(relative)occurence?
Would perhaps not be too useful in real life without a way to switch input method from application?

=== Clutter-based plugin ===
Show that input method plugins can be implemented using Clutter.

'''Difficulty/effort:''' Easy, 15 hours of work 
'''Skills required:''' Clutter, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

This should be easy to do using [http://git.clutter-project.org/cgit.cgi?url=clutter-qt/tree/README clutter-qt]. Ideally writing such would not require to compile using C++/Qt, but a C/GObject interface be provided.

=== Gtk+ based plugin ===
Show that input method plugins can be implemented using Gtk+.

'''Difficulty/effort:''' Medium, 15 hours of work 
'''Skills required:''' Gtk+, Qt, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

A bit harder than the Clutter case, but should be possible. In the simple but hacky form have a <code>QWidget</code> and a <code>GtkWidget</code> and syncronize the relevant state between them. Let the GtkWidget render offscreen and paint the GtkWidget content to the <code>QWidget</code> in <code>::paintEvent()</code>.

=== Python input method plugin interface ===
Support writing input methods in [[Python]].

'''Difficulty/effort:''' Medium, 15 hours of work 
'''Skills required:''' Python, PySide, input method API 
'''Status:''' [https://bugs.meego.com/show_bug.cgi?id=19298 In progress!] 
'''Contact person: '''

Python is an officially supported language for Meego. It would be nice if we supported writing plugins using Python. Allowing this can be done in a similar way we currently support QML (see [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/trees/master/input-method-quick input-method-quick code])
Python bindings would have to be generated for the input method API. This should probably be done using [http://www.pyside.org/ PySide].

== Non-Meego run-time environments ==

=== Maliit in Gnome 3 ===
Gnome looks to be interested in expanding to touch-centric environments. Therefore showing that Maliit is the right solution to use for input methods in Gnome would be worth-while.

'''Difficulty/effort:'''
* For prototype demo: Easy, 20 hours of work
* For really good integration: Medium, xxx hours of work
'''Skills required:''' Gnome technology, Maliit integration 
'''Status:''' Prototype work has been demonstrated 
'''Contact person:''' Jon Nordby (jonnor)

* [http://www.jonnor.com/2011/04/introducing-maliit-on-screen-keyboard-in-gnome-3/ Blogpost demoing Maliit in Gnome 3]
* [https://live.gnome.org/ThreePointOne/Features/OnScreenKeyboard Gnome 3.2 Feature page for on-screen keyboard]
* [https://bugzilla.gnome.org/show_bug.cgi?id=612662 Issue in bugtracker for on-screen keyboard]

TODO: document all the things needed for really good integration

=== Maliit on Windows ===
The main goal here would be to allow plugin development to happen on Windows. Since Meego Input Methods is implemented using Qt, this should in theory not be too hard. However, the DBus transport used between framework and inputcontext might need to be replaced by another IPC, and some X specific code might need to be reimplemented or removed.

See also [[Maliit/Ideas/Supporting_Non_X11_Platforms]]

=== Maliit in KDE ===
KDE also seems to be growing an interest in on-screen keyboards, touchscreen centric UI and mobile device form factors.

'''Difficulty/effort:'''
* For prototype demo: Easy, 10 hours of work
* For really good integration: Medium, xxx hours of work
'''Skills required:''' KDE technology, Maliit integration 
'''Status:''' ? 
'''Contact person: '''

* [http://btux1984.wordpress.com/2010/04/28/kdes-onscreen-keyboard Blogpost about onscreen keyboard]
* [http://apachelog.wordpress.com/2011/05/20/kubuntu-11-10-mobile-devices-sneak-peak/ Blogpost annoucing Kubuntu 11.10 Mobile sneak peak]
* [https://bugs.kde.org/show_bug.cgi?id=265452 Related issue in bugtracker]
* [https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-kubuntu-mobile Kubuntu Mobile Oneric blueprint ]
* [http://i.imgur.com/bbVmf.jpg Prototype screenshot]

=== Maliit in Ubuntu ===
* [https://blueprints.launchpad.net/ubuntu/+spec/multimedia-dx-n-virtual-keyboard Natty on-screen keyboard blueprint]

== Other ==
=== Commandline option to switch between D-Bus session bus and direct socket ===
Currently a peer-to-peer connection with a socket file is used for input context <-> framework communication.
Having a option to use the session bus would be nice. This allows one to make use of DBus features like on-demand service activation, or to easily introspect/debug the service.

'''Difficulty/effort:''' Easy, 20 hours of work 
'''Skills required:''' dbus, dbus-glib, C/C++ 
'''Status:''' 

* Basically, revert http://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/commit/1aa9a502005293bf4a808aaed87142f6dbcdffdb
* Add a commandline option to choose between the two methods
* Update the standard input contexts to also support session bus service (and prefer that one over the socket?)

=== Direct C/C++ Input Context API ===
Direct API for input context (no DBus connection).

'''Difficulty/effort:''' Easy, 15 hours 
'''Skills required:''' Qt, C++, input context api 
'''Status:''' 
'''Contact person:''' 

A direct API means that the framework can be tested without having to start up DBus, and that it can run on platforms with DBus.

=== Free and open source correction/prediction plugin ===
Currently there is no free error correction/prediction engine plugin. We of course want to provide this.

'''Difficulty/effort:''' Easy, 20 hours of work 
'''Skills required:''' C/C++, usage of spelling engines 
'''Status:''' Just talk. Help wanted! 

This could be done using one of the existing free spelling engines.
An analysis of the different options should be done before starting on the implementation, looking at the advantages/disadvantages of each. For instance, it might not be that all spelling engines can provide word-prediction.

* [http://aspell.net/ Aspell]
* [http://www.gnu.org/software/ispell/ispell.html Ispell]
* [http://hunspell.sourceforge.net/ Hunspell]
* [http://www.abisource.com/projects/enchant/ Enchant]
* [http://presage.sourceforge.net/ Presage] [http://www.joaquimrocha.com/2010/03/03/text-prediction-on-gnome/ (blogpost)] (for prediction)
* Dasher, might be able to use its backend (for prediction)
* ?

=== Bluetooth keyboard ===
This would allow you to use a device running Maliit as an input device for other Bluetooth enabled devices.

'''Difficulty/effort:''' Unknown, ? hours of work 
'''Skills required:''' C++, Bluetooth 
'''Status:''' Just talk! 

[http://wiki.maemo.org/Bluemaemo BlueMaemo] does this already for Maemo. It could be used as reference, or maybe code can be reused from there.

== Completed or partially-completed ideas ==
Please move ideas here one they have been implemented/explored, and document the effort.

=== QML-based plugin ===
Show that input method plugins can be implemented using Qt Quick and QML.

'''Status:''' Done! 
'''Contact person:''' Michael Hasselmann (mikhas) 

A QML-based input method plugin (keyboard) can be found in the keyboard repositor under meego-keyboard-quick. See [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit/ the blogpost announcement] for more details.

=== Maliit on Freemantle+N900 ===
Demonstrate that Maliit can run on Freemantle/N900.

'''Status:''' Done! 
'''Contact person:''' Michael Hasselmann (mikhas) 

Maliit framework and the Meego Quick keyboard is available in the extras-devel repository. See [[Maliit/Installing]] for how to install. The [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit announcement blogpost] also has some info.

=== Input Method Plugin SDK ===
Development kit to enable third-party developers to easily create new input methods.

'''Difficulty/effort:''' Easy, 20 hours of work 
'''Skills required:''' Input Method plugin API 
'''Status:''' Still room for improvement 
'''Contact person:''' Jon Nordby (jonnor) 

Current plugin SDK available from [[Maliit/Documentation]]

A good SDK would consist of:
* (80%) Comprehensive documentation for plugin API
* (60%) Task-oriented documentation for how to develop a plugin
* (DONE) Skeleton/example code to make it easy to get started
* (DONE) Above items easily available for the target platforms
* (TODO) Tools/utilities to make development easier
** Currently setting the correct plugin requires fiddling with gconf
** Currently one has to run/restart the uiserver manually
** Currently running the test application with the correct inputcontext has to be done manually

=== Window relocation ===
When the application/toolkit does not support widget relocation, fall back to relocating the window to try to keep the text input field visible on screen.

'''Difficulty/effort:''' Medium, 15 hours of work 
'''Skills required:''' X11, ICCM, EWMH 
'''Status:''' Prototype work done 
'''Contact person:''' Jon Nordby (jonnor) 

Branch: https://meego.gitorious.org/~jonnor/meegotouch/jonnors-meegotouch-inputmethodframework/commits/windowrelocation-proto1

Current code will move/resize the focused window to avoid the input method area when it grows, and restore them when input method area shrinks again.

Current challenges and ideas for improvement:
* Applications will use the desktop area to figure out how big they can make override-redirect windows and other UI element, leading them to go above the input method area. Modifying the X atoms that govern the value of this area would improve this alot.
* No way to tell if a given application window supports widget relocation or not. If the app/window supports widget relocation, it should be preferred. Window relocation should either not happen or if the , work as an additional "level" in the relocation chain.
* The current code will move the entire window. Relocation should only happen to ensure that the input widget is not obscured. This can be done by getting that information from input context through the widgetState dictionary.
* There are significant limitations to how much windows can be resized. Not much possible here without changing the application or application framework.
** A concept that might be worth trying is to let applications have scrollable areas, and for the app framework to be responsible for keeping the focused widget inside the window when resized. This could have the benefit that it would work. On the other hand, just doing proper (basic) widget relocation would not be much harder...

{{MaliitNavigationBar}}

Maliit/Ideas

2011-06-24T13:56:53Z

Jonnor: /* Meego Keyboard Ideas */

{{MaliitNavigationBar}}

Here are some ideas for what you could do with Maliit. Some are things we really want to get done (but have not committed to), some are down-to-earth nice-to-have, while others are perhaps a bit more in the crazy, experimental or show-that-it-can-be-done spirit. Feel free to add ideas here. Use the template idea if you want. For bugs or concrete features suggestions, please use the bugtracker.

=== Template Idea ===
Short description of the idea.

'''Difficulty/effort:''' How much work does it take to complete this (assuming a Maliit dev. environent is already set up) Example: Easy, 5 hours of work 
'''Status:''' What is the status of implementing this idea? Example: "In progress, this and that has been done" 
'''Skills required:''' What do people need to know in order to complete the implementation of this idea? Example: Qt | Packaging | Gtk+ | QML 
'''Contact person:''' Who interested people should contact if they want to work on this. This can be a "mentor" that has insight into the relevant areas, or someone who has started working on it. Example: Real Name (ircnick) 

Longer description. Ideas, challenges, and considerations for the implementation. Neccesary tasks to complete. Links to other relevant projects or work. Mockups, video demos, et.c.

== Meego Keyboard Ideas ==

=== Key gestures ===
Input variations of a character using gestures on that key. For instance, to input a upper case A, tap 'a', move upward and release. Accented characters can be done by gesturing sideways.

=== Predictive keyboard ===
Details of idea can be found under [[Predictive_virtual_keyboard]].

'''Difficulty/effort:''' Easy, 10 hours of work 
'''Skills required:''' Meego keyboard, Qt, C++ 
'''Status:''' Experimental merge request available 
'''Contact person:''' Michael Hasselmann (mikhas)

Experimental MRQ available: https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/merge_requests/269

Screenshot/demo video pleaz?
-- Was demonstrated during the Meego Conference San Fransisco talk. Video will hopefully become available

=== Disable invalid keys ===
Mark keys for invalid input characters as "disabled" in the keyboard.

'''Difficulty/effort:''' Simple, 10 hours of work 
'''Skills required:''' Meego keyboard, Qt, C++ 
'''Status:''' Just talk! 
'''Contact person: Jon Nordby (jonnor)'''

Often toolkits will disallow certains characters to be inputted in certain fields. For instance in an URL field or email field, certain characters are invalid. Typically this is indicated by some sort of visual "error" state after the user has tried to input the character. However, it would be nicer if the keyboard would "grey out" or disable keys that are invalid.

This will require the application to transfer the sets of valid (or invalid) characters to the input method, and for the keyboard to disable keys based on this information. This could be done with a JSON string over the extended attributes perhaps. If it is not possible for the application to enumerate all invalid characters, then the input method might have to first inform the application about which characters are available, and then the application tells which of those are invalid.

== Input Method (plugin) Ideas ==

=== Dasher input method ===
Allow input using a [[:wikipedia:Dasher|Dasher]] input method.

'''Difficulty/effort:''' Unknown, 25 hours of work? 
'''Skills required:''' C/C++, Qt, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

Dasher is a simple but innovative way of doing text input, a for this plugin would be very useful, especially for accessibility.
Dasher already has a Qt based UI, so it might be possible to reuse large parts of the code.

* [http://git.gnome.org/browse/dasher/ Homepage]
* [http://git.gnome.org/browse/dasher/ Repository]
* [https://bugzilla.gnome.org/browse.cgi?product=dasher Bugtracker]

=== Tag cloud input method ===
'''Difficulty/effort:''' Simple?, 10 hours of work? 
'''Skills required:''' C/C++, Qt, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

Use the extension attribute API to allow an application to specify a resource that the input method should present.
Perhaps it could use a SPARQL query string somehow and use tracker? Or just a JSON dictionary with key=tagname and value=(relative)occurence?
Would perhaps not be too useful in real life without a way to switch input method from application?

=== Clutter-based plugin ===
Show that input method plugins can be implemented using Clutter.

'''Difficulty/effort:''' Easy, 15 hours of work 
'''Skills required:''' Clutter, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

This should be easy to do using [http://git.clutter-project.org/cgit.cgi?url=clutter-qt/tree/README clutter-qt]. Ideally writing such would not require to compile using C++/Qt, but a C/GObject interface be provided.

=== Gtk+ based plugin ===
Show that input method plugins can be implemented using Gtk+.

'''Difficulty/effort:''' Medium, 15 hours of work 
'''Skills required:''' Gtk+, Qt, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

A bit harder than the Clutter case, but should be possible. In the simple but hacky form have a <code>QWidget</code> and a <code>GtkWidget</code> and syncronize the relevant state between them. Let the GtkWidget render offscreen and paint the GtkWidget content to the <code>QWidget</code> in <code>::paintEvent()</code>.

=== Python input method plugin interface ===
Support writing input methods in [[Python]].

'''Difficulty/effort:''' Medium, 15 hours of work 
'''Skills required:''' Python, PySide, input method API 
'''Status:''' [https://bugs.meego.com/show_bug.cgi?id=19298 In progress!] 
'''Contact person: '''

Python is an officially supported language for Meego. It would be nice if we supported writing plugins using Python. Allowing this can be done in a similar way we currently support QML (see [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/trees/master/input-method-quick input-method-quick code])
Python bindings would have to be generated for the input method API. This should probably be done using [http://www.pyside.org/ PySide].

== Non-Meego run-time environments ==

=== Maliit in Gnome 3 ===
Gnome looks to be interested in expanding to touch-centric environments. Therefore showing that Maliit is the right solution to use for input methods in Gnome would be worth-while.

'''Difficulty/effort:'''
* For prototype demo: Easy, 20 hours of work
* For really good integration: Medium, xxx hours of work
'''Skills required:''' Gnome technology, Maliit integration 
'''Status:''' Prototype work has been demonstrated 
'''Contact person:''' Jon Nordby (jonnor)

* [http://www.jonnor.com/2011/04/introducing-maliit-on-screen-keyboard-in-gnome-3/ Blogpost demoing Maliit in Gnome 3]
* [https://live.gnome.org/ThreePointOne/Features/OnScreenKeyboard Gnome 3.2 Feature page for on-screen keyboard]
* [https://bugzilla.gnome.org/show_bug.cgi?id=612662 Issue in bugtracker for on-screen keyboard]

TODO: document all the things needed for really good integration

=== Maliit on Windows ===
The main goal here would be to allow plugin development to happen on Windows. Since Meego Input Methods is implemented using Qt, this should in theory not be too hard. However, the DBus transport used between framework and inputcontext might need to be replaced by another IPC, and some X specific code might need to be reimplemented or removed.

See also [[Maliit/Ideas/Supporting_Non_X11_Platforms]]

=== Maliit in KDE ===
KDE also seems to be growing an interest in on-screen keyboards, touchscreen centric UI and mobile device form factors.

'''Difficulty/effort:'''
* For prototype demo: Easy, 10 hours of work
* For really good integration: Medium, xxx hours of work
'''Skills required:''' KDE technology, Maliit integration 
'''Status:''' ? 
'''Contact person: '''

* [http://btux1984.wordpress.com/2010/04/28/kdes-onscreen-keyboard Blogpost about onscreen keyboard]
* [http://apachelog.wordpress.com/2011/05/20/kubuntu-11-10-mobile-devices-sneak-peak/ Blogpost annoucing Kubuntu 11.10 Mobile sneak peak]
* [https://bugs.kde.org/show_bug.cgi?id=265452 Related issue in bugtracker]
* [https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-kubuntu-mobile Kubuntu Mobile Oneric blueprint ]
* [http://i.imgur.com/bbVmf.jpg Prototype screenshot]

=== Maliit in Ubuntu ===
* [https://blueprints.launchpad.net/ubuntu/+spec/multimedia-dx-n-virtual-keyboard Natty on-screen keyboard blueprint]

== Other ==
=== Commandline option to switch between D-Bus session bus and direct socket ===
Currently a peer-to-peer connection with a socket file is used for input context <-> framework communication.
Having a option to use the session bus would be nice. This allows one to make use of DBus features like on-demand service activation, or to easily introspect/debug the service.

'''Difficulty/effort:''' Easy, 20 hours of work 
'''Skills required:''' dbus, dbus-glib, C/C++ 
'''Status:''' 

* Basically, revert http://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/commit/1aa9a502005293bf4a808aaed87142f6dbcdffdb
* Add a commandline option to choose between the two methods
* Update the standard input contexts to also support session bus service (and prefer that one over the socket?)

=== Direct C/C++ Input Context API ===
Direct API for input context (no DBus connection).

'''Difficulty/effort:''' Easy, 15 hours 
'''Skills required:''' Qt, C++, input context api 
'''Status:''' 
'''Contact person:''' 

A direct API means that the framework can be tested without having to start up DBus, and that it can run on platforms with DBus.

=== Free and open source correction/prediction plugin ===
Currently there is no free error correction/prediction engine plugin. We of course want to provide this.

'''Difficulty/effort:''' Easy, 20 hours of work 
'''Skills required:''' C/C++, usage of spelling engines 
'''Status:''' Just talk. Help wanted! 

This could be done using one of the existing free spelling engines.
An analysis of the different options should be done before starting on the implementation, looking at the advantages/disadvantages of each. For instance, it might not be that all spelling engines can provide word-prediction.

* [http://aspell.net/ Aspell]
* [http://www.gnu.org/software/ispell/ispell.html Ispell]
* [http://hunspell.sourceforge.net/ Hunspell]
* [http://www.abisource.com/projects/enchant/ Enchant]
* [http://presage.sourceforge.net/ Presage] [http://www.joaquimrocha.com/2010/03/03/text-prediction-on-gnome/ (blogpost)] (for prediction)
* Dasher, might be able to use its backend (for prediction)
* ?

=== Bluetooth keyboard ===
This would allow you to use your Meego device as a keyboard for other Bluetooth enabled devices.

== Completed or partially-completed ideas ==
Please move ideas here one they have been implemented/explored, and document the effort.

=== QML-based plugin ===
Show that input method plugins can be implemented using Qt Quick and QML.

'''Status:''' Done! 
'''Contact person:''' Michael Hasselmann (mikhas) 

A QML-based input method plugin (keyboard) can be found in the keyboard repositor under meego-keyboard-quick. See [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit/ the blogpost announcement] for more details.

=== Maliit on Freemantle+N900 ===
Demonstrate that Maliit can run on Freemantle/N900.

'''Status:''' Done! 
'''Contact person:''' Michael Hasselmann (mikhas) 

Maliit framework and the Meego Quick keyboard is available in the extras-devel repository. See [[Maliit/Installing]] for how to install. The [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit announcement blogpost] also has some info.

=== Input Method Plugin SDK ===
Development kit to enable third-party developers to easily create new input methods.

'''Difficulty/effort:''' Easy, 20 hours of work 
'''Skills required:''' Input Method plugin API 
'''Status:''' Still room for improvement 
'''Contact person:''' Jon Nordby (jonnor) 

Current plugin SDK available from [[Maliit/Documentation]]

A good SDK would consist of:
* (80%) Comprehensive documentation for plugin API
* (60%) Task-oriented documentation for how to develop a plugin
* (DONE) Skeleton/example code to make it easy to get started
* (DONE) Above items easily available for the target platforms
* (TODO) Tools/utilities to make development easier
** Currently setting the correct plugin requires fiddling with gconf
** Currently one has to run/restart the uiserver manually
** Currently running the test application with the correct inputcontext has to be done manually

=== Window relocation ===
When the application/toolkit does not support widget relocation, fall back to relocating the window to try to keep the text input field visible on screen.

'''Difficulty/effort:''' Medium, 15 hours of work 
'''Skills required:''' X11, ICCM, EWMH 
'''Status:''' Prototype work done 
'''Contact person:''' Jon Nordby (jonnor) 

Branch: https://meego.gitorious.org/~jonnor/meegotouch/jonnors-meegotouch-inputmethodframework/commits/windowrelocation-proto1

Current code will move/resize the focused window to avoid the input method area when it grows, and restore them when input method area shrinks again.

Current challenges and ideas for improvement:
* Applications will use the desktop area to figure out how big they can make override-redirect windows and other UI element, leading them to go above the input method area. Modifying the X atoms that govern the value of this area would improve this alot.
* No way to tell if a given application window supports widget relocation or not. If the app/window supports widget relocation, it should be preferred. Window relocation should either not happen or if the , work as an additional "level" in the relocation chain.
* The current code will move the entire window. Relocation should only happen to ensure that the input widget is not obscured. This can be done by getting that information from input context through the widgetState dictionary.
* There are significant limitations to how much windows can be resized. Not much possible here without changing the application or application framework.
** A concept that might be worth trying is to let applications have scrollable areas, and for the app framework to be responsible for keeping the focused widget inside the window when resized. This could have the benefit that it would work. On the other hand, just doing proper (basic) widget relocation would not be much harder...

{{MaliitNavigationBar}}

Maliit/Ideas

2011-06-24T13:08:21Z

Jonnor: /* Input Method (plugin) Ideas */ tag input method

{{MaliitNavigationBar}}

Here are some ideas for what you could do with Maliit. Some are things we really want to get done (but have not committed to), some are down-to-earth nice-to-have, while others are perhaps a bit more in the crazy, experimental or show-that-it-can-be-done spirit. Feel free to add ideas here. Use the template idea if you want. For bugs or concrete features suggestions, please use the bugtracker.

=== Template Idea ===
Short description of the idea.

'''Difficulty/effort:''' How much work does it take to complete this (assuming a Maliit dev. environent is already set up) Example: Easy, 5 hours of work 
'''Status:''' What is the status of implementing this idea? Example: "In progress, this and that has been done" 
'''Skills required:''' What do people need to know in order to complete the implementation of this idea? Example: Qt | Packaging | Gtk+ | QML 
'''Contact person:''' Who interested people should contact if they want to work on this. This can be a "mentor" that has insight into the relevant areas, or someone who has started working on it. Example: Real Name (ircnick) 

Longer description. Ideas, challenges, and considerations for the implementation. Neccesary tasks to complete. Links to other relevant projects or work. Mockups, video demos, et.c.

== Meego Keyboard Ideas ==

=== Key gestures ===
Input variations of a character using gestures on that key. For instance, to input a upper case A, tap 'a', move upward and release. Accented characters can be done by gesturing sideways.

=== Predictive keyboard ===
Details of idea can be found under [[Predictive_virtual_keyboard]].

'''Difficulty/effort:''' Easy, 10 hours of work 
'''Skills required:''' Meego keyboard, Qt, C++ 
'''Status:''' Experimental merge request available 
'''Contact person:''' Michael Hasselmann (mikhas)

Experimental MRQ available: https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/merge_requests/269

Screenshot/demo video pleaz?
-- Was demonstrated during the Meego Conference San Fransisco talk. Video will hopefully become available

== Input Method (plugin) Ideas ==

=== Dasher input method ===
Allow input using a [[:wikipedia:Dasher|Dasher]] input method.

'''Difficulty/effort:''' Unknown, 25 hours of work? 
'''Skills required:''' C/C++, Qt, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

Dasher is a simple but innovative way of doing text input, a for this plugin would be very useful, especially for accessibility.
Dasher already has a Qt based UI, so it might be possible to reuse large parts of the code.

* [http://git.gnome.org/browse/dasher/ Homepage]
* [http://git.gnome.org/browse/dasher/ Repository]
* [https://bugzilla.gnome.org/browse.cgi?product=dasher Bugtracker]

=== Tag cloud input method ===
'''Difficulty/effort:''' Simple?, 10 hours of work? 
'''Skills required:''' C/C++, Qt, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

Use the extension attribute API to allow an application to specify a resource that the input method should present.
Perhaps it could use a SPARQL query string somehow and use tracker? Or just a JSON dictionary with key=tagname and value=(relative)occurence?
Would perhaps not be too useful in real life without a way to switch input method from application?

=== Clutter-based plugin ===
Show that input method plugins can be implemented using Clutter.

'''Difficulty/effort:''' Easy, 15 hours of work 
'''Skills required:''' Clutter, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

This should be easy to do using [http://git.clutter-project.org/cgit.cgi?url=clutter-qt/tree/README clutter-qt]. Ideally writing such would not require to compile using C++/Qt, but a C/GObject interface be provided.

=== Gtk+ based plugin ===
Show that input method plugins can be implemented using Gtk+.

'''Difficulty/effort:''' Medium, 15 hours of work 
'''Skills required:''' Gtk+, Qt, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

A bit harder than the Clutter case, but should be possible. In the simple but hacky form have a <code>QWidget</code> and a <code>GtkWidget</code> and syncronize the relevant state between them. Let the GtkWidget render offscreen and paint the GtkWidget content to the <code>QWidget</code> in <code>::paintEvent()</code>.

=== Python input method plugin interface ===
Support writing input methods in [[Python]].

'''Difficulty/effort:''' Medium, 15 hours of work 
'''Skills required:''' Python, PySide, input method API 
'''Status:''' [https://bugs.meego.com/show_bug.cgi?id=19298 In progress!] 
'''Contact person: '''

Python is an officially supported language for Meego. It would be nice if we supported writing plugins using Python. Allowing this can be done in a similar way we currently support QML (see [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/trees/master/input-method-quick input-method-quick code])
Python bindings would have to be generated for the input method API. This should probably be done using [http://www.pyside.org/ PySide].

== Non-Meego run-time environments ==

=== Maliit in Gnome 3 ===
Gnome looks to be interested in expanding to touch-centric environments. Therefore showing that Maliit is the right solution to use for input methods in Gnome would be worth-while.

'''Difficulty/effort:'''
* For prototype demo: Easy, 20 hours of work
* For really good integration: Medium, xxx hours of work
'''Skills required:''' Gnome technology, Maliit integration 
'''Status:''' Prototype work has been demonstrated 
'''Contact person:''' Jon Nordby (jonnor)

* [http://www.jonnor.com/2011/04/introducing-maliit-on-screen-keyboard-in-gnome-3/ Blogpost demoing Maliit in Gnome 3]
* [https://live.gnome.org/ThreePointOne/Features/OnScreenKeyboard Gnome 3.2 Feature page for on-screen keyboard]
* [https://bugzilla.gnome.org/show_bug.cgi?id=612662 Issue in bugtracker for on-screen keyboard]

TODO: document all the things needed for really good integration

=== Maliit on Windows ===
The main goal here would be to allow plugin development to happen on Windows. Since Meego Input Methods is implemented using Qt, this should in theory not be too hard. However, the DBus transport used between framework and inputcontext might need to be replaced by another IPC, and some X specific code might need to be reimplemented or removed.

See also [[Maliit/Ideas/Supporting_Non_X11_Platforms]]

=== Maliit in KDE ===
KDE also seems to be growing an interest in on-screen keyboards, touchscreen centric UI and mobile device form factors.

'''Difficulty/effort:'''
* For prototype demo: Easy, 10 hours of work
* For really good integration: Medium, xxx hours of work
'''Skills required:''' KDE technology, Maliit integration 
'''Status:''' ? 
'''Contact person: '''

* [http://btux1984.wordpress.com/2010/04/28/kdes-onscreen-keyboard Blogpost about onscreen keyboard]
* [http://apachelog.wordpress.com/2011/05/20/kubuntu-11-10-mobile-devices-sneak-peak/ Blogpost annoucing Kubuntu 11.10 Mobile sneak peak]
* [https://bugs.kde.org/show_bug.cgi?id=265452 Related issue in bugtracker]
* [https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-kubuntu-mobile Kubuntu Mobile Oneric blueprint ]
* [http://i.imgur.com/bbVmf.jpg Prototype screenshot]

=== Maliit in Ubuntu ===
* [https://blueprints.launchpad.net/ubuntu/+spec/multimedia-dx-n-virtual-keyboard Natty on-screen keyboard blueprint]

== Other ==
=== Commandline option to switch between D-Bus session bus and direct socket ===
Currently a peer-to-peer connection with a socket file is used for input context <-> framework communication.
Having a option to use the session bus would be nice. This allows one to make use of DBus features like on-demand service activation, or to easily introspect/debug the service.

'''Difficulty/effort:''' Easy, 20 hours of work 
'''Skills required:''' dbus, dbus-glib, C/C++ 
'''Status:''' 

* Basically, revert http://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/commit/1aa9a502005293bf4a808aaed87142f6dbcdffdb
* Add a commandline option to choose between the two methods
* Update the standard input contexts to also support session bus service (and prefer that one over the socket?)

=== Direct C/C++ Input Context API ===
Direct API for input context (no DBus connection).

'''Difficulty/effort:''' Easy, 15 hours 
'''Skills required:''' Qt, C++, input context api 
'''Status:''' 
'''Contact person:''' 

A direct API means that the framework can be tested without having to start up DBus, and that it can run on platforms with DBus.

=== Free and open source correction/prediction plugin ===
Currently there is no free error correction/prediction engine plugin. We of course want to provide this.

'''Difficulty/effort:''' Easy, 20 hours of work 
'''Skills required:''' C/C++, usage of spelling engines 
'''Status:''' Just talk. Help wanted! 

This could be done using one of the existing free spelling engines.
An analysis of the different options should be done before starting on the implementation, looking at the advantages/disadvantages of each. For instance, it might not be that all spelling engines can provide word-prediction.

* [http://aspell.net/ Aspell]
* [http://www.gnu.org/software/ispell/ispell.html Ispell]
* [http://hunspell.sourceforge.net/ Hunspell]
* [http://www.abisource.com/projects/enchant/ Enchant]
* [http://presage.sourceforge.net/ Presage] [http://www.joaquimrocha.com/2010/03/03/text-prediction-on-gnome/ (blogpost)] (for prediction)
* Dasher, might be able to use its backend (for prediction)
* ?

=== Bluetooth keyboard ===
This would allow you to use your Meego device as a keyboard for other Bluetooth enabled devices.

== Completed or partially-completed ideas ==
Please move ideas here one they have been implemented/explored, and document the effort.

=== QML-based plugin ===
Show that input method plugins can be implemented using Qt Quick and QML.

'''Status:''' Done! 
'''Contact person:''' Michael Hasselmann (mikhas) 

A QML-based input method plugin (keyboard) can be found in the keyboard repositor under meego-keyboard-quick. See [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit/ the blogpost announcement] for more details.

=== Maliit on Freemantle+N900 ===
Demonstrate that Maliit can run on Freemantle/N900.

'''Status:''' Done! 
'''Contact person:''' Michael Hasselmann (mikhas) 

Maliit framework and the Meego Quick keyboard is available in the extras-devel repository. See [[Maliit/Installing]] for how to install. The [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit announcement blogpost] also has some info.

=== Input Method Plugin SDK ===
Development kit to enable third-party developers to easily create new input methods.

'''Difficulty/effort:''' Easy, 20 hours of work 
'''Skills required:''' Input Method plugin API 
'''Status:''' Still room for improvement 
'''Contact person:''' Jon Nordby (jonnor) 

Current plugin SDK available from [[Maliit/Documentation]]

A good SDK would consist of:
* (80%) Comprehensive documentation for plugin API
* (60%) Task-oriented documentation for how to develop a plugin
* (DONE) Skeleton/example code to make it easy to get started
* (DONE) Above items easily available for the target platforms
* (TODO) Tools/utilities to make development easier
** Currently setting the correct plugin requires fiddling with gconf
** Currently one has to run/restart the uiserver manually
** Currently running the test application with the correct inputcontext has to be done manually

=== Window relocation ===
When the application/toolkit does not support widget relocation, fall back to relocating the window to try to keep the text input field visible on screen.

'''Difficulty/effort:''' Medium, 15 hours of work 
'''Skills required:''' X11, ICCM, EWMH 
'''Status:''' Prototype work done 
'''Contact person:''' Jon Nordby (jonnor) 

Branch: https://meego.gitorious.org/~jonnor/meegotouch/jonnors-meegotouch-inputmethodframework/commits/windowrelocation-proto1

Current code will move/resize the focused window to avoid the input method area when it grows, and restore them when input method area shrinks again.

Current challenges and ideas for improvement:
* Applications will use the desktop area to figure out how big they can make override-redirect windows and other UI element, leading them to go above the input method area. Modifying the X atoms that govern the value of this area would improve this alot.
* No way to tell if a given application window supports widget relocation or not. If the app/window supports widget relocation, it should be preferred. Window relocation should either not happen or if the , work as an additional "level" in the relocation chain.
* The current code will move the entire window. Relocation should only happen to ensure that the input widget is not obscured. This can be done by getting that information from input context through the widgetState dictionary.
* There are significant limitations to how much windows can be resized. Not much possible here without changing the application or application framework.
** A concept that might be worth trying is to let applications have scrollable areas, and for the app framework to be responsible for keeping the focused widget inside the window when resized. This could have the benefit that it would work. On the other hand, just doing proper (basic) widget relocation would not be much harder...

{{MaliitNavigationBar}}

Maliit/Ideas

2011-06-24T12:43:05Z

Jonnor: /* Python input method plugin interface */ status update

{{MaliitNavigationBar}}

Here are some ideas for what you could do with Maliit. Some are things we really want to get done (but have not committed to), some are down-to-earth nice-to-have, while others are perhaps a bit more in the crazy, experimental or show-that-it-can-be-done spirit. Feel free to add ideas here. Use the template idea if you want. For bugs or concrete features suggestions, please use the bugtracker.

=== Template Idea ===
Short description of the idea.

'''Difficulty/effort:''' How much work does it take to complete this (assuming a Maliit dev. environent is already set up) Example: Easy, 5 hours of work 
'''Status:''' What is the status of implementing this idea? Example: "In progress, this and that has been done" 
'''Skills required:''' What do people need to know in order to complete the implementation of this idea? Example: Qt | Packaging | Gtk+ | QML 
'''Contact person:''' Who interested people should contact if they want to work on this. This can be a "mentor" that has insight into the relevant areas, or someone who has started working on it. Example: Real Name (ircnick) 

Longer description. Ideas, challenges, and considerations for the implementation. Neccesary tasks to complete. Links to other relevant projects or work. Mockups, video demos, et.c.

== Meego Keyboard Ideas ==

=== Key gestures ===
Input variations of a character using gestures on that key. For instance, to input a upper case A, tap 'a', move upward and release. Accented characters can be done by gesturing sideways.

=== Predictive keyboard ===
Details of idea can be found under [[Predictive_virtual_keyboard]].

'''Difficulty/effort:''' Easy, 10 hours of work 
'''Skills required:''' Meego keyboard, Qt, C++ 
'''Status:''' Experimental merge request available 
'''Contact person:''' Michael Hasselmann (mikhas)

Experimental MRQ available: https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/merge_requests/269

Screenshot/demo video pleaz?
-- Was demonstrated during the Meego Conference San Fransisco talk. Video will hopefully become available

== Input Method (plugin) Ideas ==

=== Dasher input method ===
Allow input using a [[:wikipedia:Dasher|Dasher]] input method.

'''Difficulty/effort:''' Unknown, 25 hours of work? 
'''Skills required:''' C/C++, Qt, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

Dasher is a simple but innovative way of doing text input, a for this plugin would be very useful, especially for accessibility.
Dasher already has a Qt based UI, so it might be possible to reuse large parts of the code.

* [http://git.gnome.org/browse/dasher/ Homepage]
* [http://git.gnome.org/browse/dasher/ Repository]
* [https://bugzilla.gnome.org/browse.cgi?product=dasher Bugtracker]

=== Clutter-based plugin ===
Show that input method plugins can be implemented using Clutter.

'''Difficulty/effort:''' Easy, 15 hours of work 
'''Skills required:''' Clutter, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

This should be easy to do using [http://git.clutter-project.org/cgit.cgi?url=clutter-qt/tree/README clutter-qt]. Ideally writing such would not require to compile using C++/Qt, but a C/GObject interface be provided.

=== Gtk+ based plugin ===
Show that input method plugins can be implemented using Gtk+.

'''Difficulty/effort:''' Medium, 15 hours of work 
'''Skills required:''' Gtk+, Qt, input method API 
'''Status:''' Just talk! 
'''Contact person:'''

A bit harder than the Clutter case, but should be possible. In the simple but hacky form have a <code>QWidget</code> and a <code>GtkWidget</code> and syncronize the relevant state between them. Let the GtkWidget render offscreen and paint the GtkWidget content to the <code>QWidget</code> in <code>::paintEvent()</code>.

=== Python input method plugin interface ===
Support writing input methods in [[Python]].

'''Difficulty/effort:''' Medium, 15 hours of work 
'''Skills required:''' Python, PySide, input method API 
'''Status:''' [https://bugs.meego.com/show_bug.cgi?id=19298 In progress!] 
'''Contact person: '''

Python is an officially supported language for Meego. It would be nice if we supported writing plugins using Python. Allowing this can be done in a similar way we currently support QML (see [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/trees/master/input-method-quick input-method-quick code])
Python bindings would have to be generated for the input method API. This should probably be done using [http://www.pyside.org/ PySide].

== Non-Meego run-time environments ==

=== Maliit in Gnome 3 ===
Gnome looks to be interested in expanding to touch-centric environments. Therefore showing that Maliit is the right solution to use for input methods in Gnome would be worth-while.

'''Difficulty/effort:'''
* For prototype demo: Easy, 20 hours of work
* For really good integration: Medium, xxx hours of work
'''Skills required:''' Gnome technology, Maliit integration 
'''Status:''' Prototype work has been demonstrated 
'''Contact person:''' Jon Nordby (jonnor)

* [http://www.jonnor.com/2011/04/introducing-maliit-on-screen-keyboard-in-gnome-3/ Blogpost demoing Maliit in Gnome 3]
* [https://live.gnome.org/ThreePointOne/Features/OnScreenKeyboard Gnome 3.2 Feature page for on-screen keyboard]
* [https://bugzilla.gnome.org/show_bug.cgi?id=612662 Issue in bugtracker for on-screen keyboard]

TODO: document all the things needed for really good integration

=== Maliit on Windows ===
The main goal here would be to allow plugin development to happen on Windows. Since Meego Input Methods is implemented using Qt, this should in theory not be too hard. However, the DBus transport used between framework and inputcontext might need to be replaced by another IPC, and some X specific code might need to be reimplemented or removed.

See also [[Maliit/Ideas/Supporting_Non_X11_Platforms]]

=== Maliit in KDE ===
KDE also seems to be growing an interest in on-screen keyboards, touchscreen centric UI and mobile device form factors.

'''Difficulty/effort:'''
* For prototype demo: Easy, 10 hours of work
* For really good integration: Medium, xxx hours of work
'''Skills required:''' KDE technology, Maliit integration 
'''Status:''' ? 
'''Contact person: '''

* [http://btux1984.wordpress.com/2010/04/28/kdes-onscreen-keyboard Blogpost about onscreen keyboard]
* [http://apachelog.wordpress.com/2011/05/20/kubuntu-11-10-mobile-devices-sneak-peak/ Blogpost annoucing Kubuntu 11.10 Mobile sneak peak]
* [https://bugs.kde.org/show_bug.cgi?id=265452 Related issue in bugtracker]
* [https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-kubuntu-mobile Kubuntu Mobile Oneric blueprint ]
* [http://i.imgur.com/bbVmf.jpg Prototype screenshot]

=== Maliit in Ubuntu ===
* [https://blueprints.launchpad.net/ubuntu/+spec/multimedia-dx-n-virtual-keyboard Natty on-screen keyboard blueprint]

== Other ==
=== Commandline option to switch between D-Bus session bus and direct socket ===
Currently a peer-to-peer connection with a socket file is used for input context <-> framework communication.
Having a option to use the session bus would be nice. This allows one to make use of DBus features like on-demand service activation, or to easily introspect/debug the service.

'''Difficulty/effort:''' Easy, 20 hours of work 
'''Skills required:''' dbus, dbus-glib, C/C++ 
'''Status:''' 

* Basically, revert http://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/commit/1aa9a502005293bf4a808aaed87142f6dbcdffdb
* Add a commandline option to choose between the two methods
* Update the standard input contexts to also support session bus service (and prefer that one over the socket?)

=== Direct C/C++ Input Context API ===
Direct API for input context (no DBus connection).

'''Difficulty/effort:''' Easy, 15 hours 
'''Skills required:''' Qt, C++, input context api 
'''Status:''' 
'''Contact person:''' 

A direct API means that the framework can be tested without having to start up DBus, and that it can run on platforms with DBus.

=== Free and open source correction/prediction plugin ===
Currently there is no free error correction/prediction engine plugin. We of course want to provide this.

'''Difficulty/effort:''' Easy, 20 hours of work 
'''Skills required:''' C/C++, usage of spelling engines 
'''Status:''' Just talk. Help wanted! 

This could be done using one of the existing free spelling engines.
An analysis of the different options should be done before starting on the implementation, looking at the advantages/disadvantages of each. For instance, it might not be that all spelling engines can provide word-prediction.

* [http://aspell.net/ Aspell]
* [http://www.gnu.org/software/ispell/ispell.html Ispell]
* [http://hunspell.sourceforge.net/ Hunspell]
* [http://www.abisource.com/projects/enchant/ Enchant]
* [http://presage.sourceforge.net/ Presage] [http://www.joaquimrocha.com/2010/03/03/text-prediction-on-gnome/ (blogpost)] (for prediction)
* Dasher, might be able to use its backend (for prediction)
* ?

=== Bluetooth keyboard ===
This would allow you to use your Meego device as a keyboard for other Bluetooth enabled devices.

== Completed or partially-completed ideas ==
Please move ideas here one they have been implemented/explored, and document the effort.

=== QML-based plugin ===
Show that input method plugins can be implemented using Qt Quick and QML.

'''Status:''' Done! 
'''Contact person:''' Michael Hasselmann (mikhas) 

A QML-based input method plugin (keyboard) can be found in the keyboard repositor under meego-keyboard-quick. See [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit/ the blogpost announcement] for more details.

=== Maliit on Freemantle+N900 ===
Demonstrate that Maliit can run on Freemantle/N900.

'''Status:''' Done! 
'''Contact person:''' Michael Hasselmann (mikhas) 

Maliit framework and the Meego Quick keyboard is available in the extras-devel repository. See [[Maliit/Installing]] for how to install. The [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit announcement blogpost] also has some info.

=== Input Method Plugin SDK ===
Development kit to enable third-party developers to easily create new input methods.

'''Difficulty/effort:''' Easy, 20 hours of work 
'''Skills required:''' Input Method plugin API 
'''Status:''' Still room for improvement 
'''Contact person:''' Jon Nordby (jonnor) 

Current plugin SDK available from [[Maliit/Documentation]]

A good SDK would consist of:
* (80%) Comprehensive documentation for plugin API
* (60%) Task-oriented documentation for how to develop a plugin
* (DONE) Skeleton/example code to make it easy to get started
* (DONE) Above items easily available for the target platforms
* (TODO) Tools/utilities to make development easier
** Currently setting the correct plugin requires fiddling with gconf
** Currently one has to run/restart the uiserver manually
** Currently running the test application with the correct inputcontext has to be done manually

=== Window relocation ===
When the application/toolkit does not support widget relocation, fall back to relocating the window to try to keep the text input field visible on screen.

'''Difficulty/effort:''' Medium, 15 hours of work 
'''Skills required:''' X11, ICCM, EWMH 
'''Status:''' Prototype work done 
'''Contact person:''' Jon Nordby (jonnor) 

Branch: https://meego.gitorious.org/~jonnor/meegotouch/jonnors-meegotouch-inputmethodframework/commits/windowrelocation-proto1

Current code will move/resize the focused window to avoid the input method area when it grows, and restore them when input method area shrinks again.

Current challenges and ideas for improvement:
* Applications will use the desktop area to figure out how big they can make override-redirect windows and other UI element, leading them to go above the input method area. Modifying the X atoms that govern the value of this area would improve this alot.
* No way to tell if a given application window supports widget relocation or not. If the app/window supports widget relocation, it should be preferred. Window relocation should either not happen or if the , work as an additional "level" in the relocation chain.
* The current code will move the entire window. Relocation should only happen to ensure that the input widget is not obscured. This can be done by getting that information from input context through the widgetState dictionary.
* There are significant limitations to how much windows can be resized. Not much possible here without changing the application or application framework.
** A concept that might be worth trying is to let applications have scrollable areas, and for the app framework to be responsible for keeping the focused widget inside the window when resized. This could have the benefit that it would work. On the other hand, just doing proper (basic) widget relocation would not be much harder...

{{MaliitNavigationBar}}

Maliit

2011-06-24T10:49:37Z

Jonnor: reorder sections, remove superficial sections that only linked to other pages (the navigation bar does that job)

{{MaliitNavigationBar}}

[[File:Maliit2.png|448px|link=]]

Maliit provides a flexible and cross-platform input method framework, including a virtual keyboard. It works on all MeeGo user experiences, and in other GNU/Linux distributions.

== Goals ==

Maliit aims to be ''the'' input method project for MeeGo and other GNU/Linux-based embedded/mobile platforms. To achieve this we should provide:

'''A solid input method framework'''

This includes support for traditional input methods such as hardware and virtual keyboards. More exotic input methods should also be possible, such as handwriting recognition and voice input, and special purpose input methods such as date/time pickers, tag clouds, etc.

'''A core set of input methods'''

The default set of input methods should demonstrate the core capabilities of the framework and provide a good user experience that device manufacturers and integrators can use easily.

We also aim to:

'''Empower third-party developers'''

Customizing existing input methods or developing powerful new input methods should be simple, regardless of whether it is for profit, research or fun.

'''Build a diverse community of contributors'''

Employees from different companies, freelancers, members of academia, hackers and volunteers should all be welcomed and encouraged to contribute to the project.

== Communication channels ==

'''Mailing list:''' meego-inputmethods@lists.meego.com ([http://lists.meego.com/listinfo/meego-inputmethods listinfo] | [http://lists.meego.com/pipermail/meego-inputmethods/ archives])

'''Bugtracker:''' bugs.meego.com, Product: OS, Component: Virtual Keyboard ([https://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_based_on=virtual%20keyboard&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&component=Virtual%20keyboard&product=OS%20Base&known_name=virtual%20keyboard open bugs] |
[https://bugs.meego.com/enter_bug.cgi?product=OS%20Base&component=Virtual%20keyboard file new bug])

'''IRC:''' Visit us in #meego-inputmethods at freenode.net ([http://webchat.freenode.net/?randomnick=1&channels=meego-inputmethods&uio=d4 webchat])

== Upcoming events ==
* June 24th, MeeGo Freeday workshop, details TBA.
* August 6th-12th - Desktop Summit Berlin.

== News ==
* 20.06.2011 - First release (Maliit 0.80) as an independent project. [http://lists.meego.com/pipermail/meego-dev/2011-June/483526.html Announcement]
* 17.06.2011 - Session at Qt Collaborator Summit 2011. [http://developer.qt.nokia.com/groups/qt_contributors_summit/wiki/Input_methods_and_Wayland_in_Qt_5 Session summary]
* 07.06.2011 - Session at MeeGo Spring Conference 2011. [http://sf2011.meego.com/program/sessions/developing-custom-input-methods-meego Info, Recording]
* 08.04.2011 - MeeGo Keyboard is relicensed with BSD license: [http://lists.meego.com/pipermail/meego-dev/2011-April/482578.html Announcement]
* 29.03.2011 - Held first offical IRC meeting: [[Maliit/Meetings|How can we simplify development and maintenance of input contexts?]]
* 04.03.2011 - API/ABI break in 0.20.0: [http://lists.meego.com/pipermail/meego-dev/2011-March/481869.html meego-im-framework is removing dependency to libmeegotouch from its API]
* 23.02.2011 - Packages available for Ubuntu Lucid/Maverick to ease development. [http://taschenorakel.de/michael/2011/02/24/meego-input-methods-your-desktop/ Blogpost], [[#Packages for Ubuntu .2810.04 Lucid Lynx .2F 10.10 Maveric Meerkat.29|documentation]]
* 17.02.2011 - Claudio Saavedra started on MeeGo+Gtk integration work, focusing on input methods. [http://people.gnome.org/~csaavedra/news-2011-02.html#D10 Blogpost]
* 13.02.2011 - MeeGo Tablet UX demoed at Mobile World Conference, with Swype keyboard. [http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 Pictures]
* 01.02.2011 - API/ABI break in 0.19.41: [http://lists.meego.com/pipermail/meego-dev/2011-February/481353.html meegoimframework interfaces related to orientation change will be changed]
* 15.11.2010 - Architect and Lead Developer of Maliit give talk at MeeGo Conference. [http://conference2010.meego.com/session/meego-touch-input-method-frameworks Info, Recording]
* 15.11.2010 - Linpus shows off MeeGo based slate at MeeGo Conference, with keyboard based on Maliit.
* 30.06.2010 - MeeGo Handset UX Day 1 release, first public release of MeeGo Input Methods. [http://meego.com/community/blogs/valhalla/2010/meego-handset-project-day-1-here Announcement]

== Maliit in action ==

Maliit is used on a number of devices and form factors, and can easily be adapted to run on new ones.

* [http://www.linpus.com/products_meego_slate.html Linpus Slate] ([http://www.linpus.com/images/slate/kb.png screenshot showing Linpus virtual keyboard])
* [http://appdeveloper.intel.com/en-us/meego-iso-esla Intel MeeGo Tablet] ([http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 pictures showing Swype keyboard])
* [http://www.youtube.com/watch?v=l_7f3Lxd4_I GNOME3 on a WeTab (video)]

<gallery widths="250px" heights="250px" perrow="3">
Image:Lenovo_meego_vkb.jpg| [[Maliit/MeeGo 1.1#Netbook|MeeGo 1.1 Netbook]] with MeeGo Keyboard on Lenovo S10-3T Ideapad
Image:Meego1.1_handset_on_aava.jpg| [http://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo 1.1 Handset] with MeeGo Keyboard on Aava Mobile
Image:tegra-vkb2.jpg| MeeGo 1.2 prerelease on [[ARM/TEGRA2|Advent Vega, Tegra2]]
Image:Maliit-on-lucid.png | Ubuntu Lucid (10.04)
Image:Maliit-in-GNOME3.jpg | GNOME3 on a WeTab
Image:Maliit-on-KDE-Plasma.jpg | KDE, using Plasma
[[File:TransparentPlaceholder.png|link=http://wikipedia.org|caption]]
</gallery>

{{MaliitNavigationBar}}

Template:MaliitNavigationBar

2011-06-24T10:36:33Z

Jonnor: whitespace fix

{| class="wikitable" style="width:100%;text-align:center"
! [[Maliit|Maliit - Input Methods for MeeGo]]
|-
| [[Maliit|Overview]] · [[Maliit/Features|Features]] · [[Maliit/Documentation|Documentation]] · [[Maliit/Development|Development]] · [[Maliit/Installing|Installing]] · [[Maliit/Roadmap|Roadmap]] · [[Maliit/Ideas|Ideas]] · [[Maliit/Team|Team]]
|}

[[Category:Maliit]][[Category:MeeGo Input Methods]]

Template:MaliitNavigationBar

2011-06-24T10:33:12Z

Jonnor: add features page

{| class="wikitable" style="width:100%;text-align:center"
! [[Maliit|Maliit - Input Methods for MeeGo]]
|-
| [[Maliit|Overview]] · [[Maliit/Features|Features]]· [[Maliit/Documentation|Documentation]] · [[Maliit/Development|Development]] · [[Maliit/Installing|Installing]] · [[Maliit/Roadmap|Roadmap]] · [[Maliit/Ideas|Ideas]] · [[Maliit/Team|Team]]
|}

[[Category:Maliit]][[Category:MeeGo Input Methods]]

Maliit/Features

2011-06-24T10:31:55Z

Jonnor: moved out from parent page

{{MaliitNavigationBar}}

== Features ==

=== For end users ===
Following are the high level end-user features supported by Maliit:

* Multitouch virtual keyboard
** Landscape and portrait QWERTY with dedicated symbol views
** Support for multiple languages and scripts (e.g. latin, cyrillic, arabic, chinese)
*** See current layouts at [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/m-keyboard/layouts MeeGo gitorius]
** Number/phone number layouts for entering numbers/phone numbers
* Context sensitive and dynamic action key
** e.g. replacing enter icon with search icon and highlighting the key in search fields - and respective search key inactive when search field empty
* Context sensitive layouts
** e.g. replacing ',' key with '@' in e-mail address fields
* Simple interactions (as defined in [http://meego.com/developers/ui-design-guidelines/handset/meego-basics MeeGo Basics])
** Swipe sideways to easily switch between different active keyboard layouts and other input methods
** Swipe down to close virtual keyboard or alternatively tap outiside the active input area to close keyboard
* Low-latency haptics typing feedback (with feedback framework backend); sound,tactile

[[File:Text-input-1.png|Virtual keyboard interaction : opening and closing the keyboard]]

* Cut/Copy/Paste for text input
** Separate text editor widget for text input fields
* Error correction / word prediction for virtual keyboard (with error correction / prediction engine)
** Separate widget for correction/prediction candidates
* Hardware keyboard
** Long pressing of keys either to autorepeat (e.g. arrow keys, backspace) or to input secondary characters (e.g. numbers, symbols)
** Possibility to extend hardware keys with virtual keys (e.g. for additional symbols)

[[File:Text-input-2a.png|Text input with hardware keyboard]]

* Toolbar for appliction specific input content
** For placing buttons, labels etc.
** Toolbar located on top of virtual keyboard, with hardware keyboard in the bottom of the screen

[[File:Confirming.png|Placing application specific actions in the input toolbar, when application UI is not visible or "Enter" action is not adequate]]

* External input methods
** e.g. Bluetooth keyboards

=== For integrators and developers ===
* Input Methods can be implemented as plugins
* Error correction/prediction engines can be implemented as plugins
* Framework is licensed LGPL
* Keyboard has theming abilities via CSS file
* Meego Keyboard has customizable layout files
* Meego Feedback framework has swappable backends (for haptics et.c.)
* Support for additional toolkits can be done by using the DBus connection for the Input Context

{{MaliitNavigationBar}}

Maliit

2011-06-24T10:31:40Z

Jonnor: /* Features */ Moved to subpage

{{MaliitNavigationBar}}

[[File:Maliit2.png|448px|link=]]

Maliit provides a flexible and cross-platform input method framework, including a virtual keyboard. It works on all MeeGo user experiences, and in other GNU/Linux distributions.

== Goals ==

Maliit aims to be ''the'' input method project for MeeGo and other GNU/Linux-based embedded/mobile platforms. To achieve this we should provide:

'''A solid input method framework'''

This includes support for traditional input methods such as hardware and virtual keyboards. More exotic input methods should also be possible, such as handwriting recognition and voice input, and special purpose input methods such as date/time pickers, tag clouds, etc.

'''A core set of input methods'''

The default set of input methods should demonstrate the core capabilities of the framework and provide a good user experience that device manufacturers and integrators can use easily.

We also aim to:

'''Empower third-party developers'''

Customizing existing input methods or developing powerful new input methods should be simple, regardless of whether it is for profit, research or fun.

'''Build a diverse community of contributors'''

Employees from different companies, freelancers, members of academia, hackers and volunteers should all be welcomed and encouraged to contribute to the project.

== Maliit in action ==

Maliit is used on a number of devices and form factors, and can easily be adapted to run on new ones.

* [http://www.linpus.com/products_meego_slate.html Linpus Slate] ([http://www.linpus.com/images/slate/kb.png screenshot showing Linpus virtual keyboard])
* [http://appdeveloper.intel.com/en-us/meego-iso-esla Intel MeeGo Tablet] ([http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 pictures showing Swype keyboard])
* [http://www.youtube.com/watch?v=l_7f3Lxd4_I GNOME3 on a WeTab (video)]

<gallery widths="250px" heights="250px" perrow="3">
Image:Lenovo_meego_vkb.jpg| [[Maliit/MeeGo 1.1#Netbook|MeeGo 1.1 Netbook]] with MeeGo Keyboard on Lenovo S10-3T Ideapad
Image:Meego1.1_handset_on_aava.jpg| [http://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo 1.1 Handset] with MeeGo Keyboard on Aava Mobile
Image:tegra-vkb2.jpg| MeeGo 1.2 prerelease on [[ARM/TEGRA2|Advent Vega, Tegra2]]
Image:Maliit-on-lucid.png | Ubuntu Lucid (10.04)
Image:Maliit-in-GNOME3.jpg | GNOME3 on a WeTab
Image:Maliit-on-KDE-Plasma.jpg | KDE, using Plasma
[[File:TransparentPlaceholder.png|link=http://wikipedia.org|caption]]
</gallery>

== Communication channels ==

'''Mailing list:''' meego-inputmethods@lists.meego.com ([http://lists.meego.com/listinfo/meego-inputmethods listinfo] | [http://lists.meego.com/pipermail/meego-inputmethods/ archives])

'''Bugtracker:''' bugs.meego.com, Product: OS, Component: Virtual Keyboard ([https://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_based_on=virtual%20keyboard&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=INDEFINITION&bug_status=ASSIGNED&bug_status=ACCEPTED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=WAITING&bug_status=REOPENED&component=Virtual%20keyboard&product=OS%20Base&known_name=virtual%20keyboard open bugs] |
[https://bugs.meego.com/enter_bug.cgi?product=OS%20Base&component=Virtual%20keyboard file new bug])

'''IRC:''' Visit us in #meego-inputmethods at freenode.net ([http://webchat.freenode.net/?randomnick=1&channels=meego-inputmethods&uio=d4 webchat])

== News ==
* 20.06.2011 - First release (Maliit 0.80) as an independent project. [http://lists.meego.com/pipermail/meego-dev/2011-June/483526.html Announcement]
* 17.06.2011 - Session at Qt Collaborator Summit 2011. [http://developer.qt.nokia.com/groups/qt_contributors_summit/wiki/Input_methods_and_Wayland_in_Qt_5 Session summary]
* 07.06.2011 - Session at MeeGo Spring Conference 2011. [http://sf2011.meego.com/program/sessions/developing-custom-input-methods-meego Info, Recording]
* 08.04.2011 - MeeGo Keyboard is relicensed with BSD license: [http://lists.meego.com/pipermail/meego-dev/2011-April/482578.html Announcement]
* 29.03.2011 - Held first offical IRC meeting: [[Maliit/Meetings|How can we simplify development and maintenance of input contexts?]]
* 04.03.2011 - API/ABI break in 0.20.0: [http://lists.meego.com/pipermail/meego-dev/2011-March/481869.html meego-im-framework is removing dependency to libmeegotouch from its API]
* 23.02.2011 - Packages available for Ubuntu Lucid/Maverick to ease development. [http://taschenorakel.de/michael/2011/02/24/meego-input-methods-your-desktop/ Blogpost], [[#Packages for Ubuntu .2810.04 Lucid Lynx .2F 10.10 Maveric Meerkat.29|documentation]]
* 17.02.2011 - Claudio Saavedra started on MeeGo+Gtk integration work, focusing on input methods. [http://people.gnome.org/~csaavedra/news-2011-02.html#D10 Blogpost]
* 13.02.2011 - MeeGo Tablet UX demoed at Mobile World Conference, with Swype keyboard. [http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 Pictures]
* 01.02.2011 - API/ABI break in 0.19.41: [http://lists.meego.com/pipermail/meego-dev/2011-February/481353.html meegoimframework interfaces related to orientation change will be changed]
* 15.11.2010 - Architect and Lead Developer of Maliit give talk at MeeGo Conference. [http://conference2010.meego.com/session/meego-touch-input-method-frameworks Info, Recording]
* 15.11.2010 - Linpus shows off MeeGo based slate at MeeGo Conference, with keyboard based on Maliit.
* 30.06.2010 - MeeGo Handset UX Day 1 release, first public release of MeeGo Input Methods. [http://meego.com/community/blogs/valhalla/2010/meego-handset-project-day-1-here Announcement]

== Roadmap ==
See [[Maliit/Roadmap]]

== Upcoming events ==
* June 24th, MeeGo Freeday workshop, details TBA.
* August 6th-12th - Desktop Summit Berlin.

== Ideas ==
See [[Maliit/Ideas]]

== Developers ==
See [[Maliit/Development]]

== Documentation ==
See [[Maliit/Documentation]]

{{MaliitNavigationBar}}

Maliit/Documentation

2011-06-23T09:11:59Z

Jonnor: /* Important cases */

[[Category:Maliit]][[Category:MeeGo Input Methods]]
{{MaliitNavigationBar}}

== FAQ ==
Frequently asked questions.

'''1. How to write my own input method?''' 
The recommended way to get started is to use the Maliit Plugin SDK and follow the [[Maliit/Documentation#Plugin_development_Quickstart|quickstart documentation]].

For developing an input method plugin, the primary interface is Qt and C++. The most relevant classes are: [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/minputmethodplugin.h MInputMethodPlugin],
[https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/mabstractinputmethod.h MAbstractInputMethod] and [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/mabstractinputmethodhost.h MAbstractInputMethodHost].

Since version 0.20.9-1 of the framework (May 2011), the MInputMethodQuick API allows one to also easily write input
methods using QML. See the [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/meego-keyboard-quick MeegoKeyboardQuick code] for an example.
As of May 2011 this interface is not yet feature complete with the C++ one. Contributions welcomed.

=== Unanswered questions ===
Please add any questions you may have here.

* Does Maliit work with non-compositing Window Managers?
* Which window managers are currently supported?

== Plugin Development Quickstart ==
How to get started developing plugins. This documentation is mainly for framework version 0.20.11-1 and newer. The C++ plugin API is compatible with all 0.20.x versions, and the QML interface is available from 0.20.9-1. Meego 1.2 has version 0.20.6. To develop there, one can install packages from Trunk/1.3.

Note that this is not intended to be 100% copy'n'paste step-by-step instructions. You may need to use common sense.

* [[Maliit/Installing|Install Maliit]] for your development environment
* [http://www.jonnor.com/files/maliit/maliit-plugin-sdk-0.1.0.tar.gz Download] the Maliit Plugin SDK
* Extract the examples
# In your favorite terminal:
tar -xf maliit-plugin-sdk-*.tar.gz
cd maliit-plugin-sdk/examples/
* Compile them
qmake
make
make install
* Have a look around. In the examples directory you will find a QML based plugin and a C++ based plugin.
# QML plugin code
ls plugins/quick/
# C++ plugin code
ls plugins/standard
* Try out one of the examples
# First enable both of the example input methods, along with the meego keyboard
gconftool-2 -s /meegotouch/inputmethods/onscreen/enabled -t list --list-type strings \
[libmeego-keyboard.so,en_gb.xml,libmeego-keyboard-quick.so,,libhelloworldplugin.so,,libexampleplugin.so,ExamplePluginSubview1]
# To activate the QML example
gconftool-2 -s /meegotouch/inputmethods/onscreen/active -t list --list-type string [libhelloworldplugin.so,]
# To instead activate the C++ example
gconftool-2 -s /meegotouch/inputmethods/onscreen/active -t list --list-type string [libexampleplugin.so,ExamplePluginSubview1]

# To test, start the Maliit server and a application with a Maliit inputcontext loaded
# Note: More documentation on this can be found on the Installing page
meego-im-uiserver > server.log &
QT_IM_MODULE=MInputContext apps/plainqt/plainqt

# Tap/double tap on a text field to activate the input method
# You should now be able to see an input method which allows you to click to input "Hello World"

* Try changing the plugin code a bit, and reinstall and restart the Maliit server to try again.
# Do changes (start simple, maybe by changing the "Hello World" string to something else)

# Rebuild and reinstall plugins
make && make install
# Remember to restart the Maliit server for it to pick up the changed plugin

If you have any issues, first try to solve the problem by reading the instructions again, and maybe other documentation. If you cannot solve it, ask for help through one of our communication channels.

There are also several open source input plugins that one look at. See for instance
* [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/m-keyboard Meego Keyboard]
* [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/meego-keyboard-quick Meego Keyboard Quick]
* [https://github.com/foolegg/cute-input-method/tree/maliit cute-input-method]

== Feature documentation ==
See [[Maliit#Features]]

== API documentation ==
* [http://apidocs.meego.com/1.1/platform/html/meego-im-framework/main.html Old MeeGo 1.1 Input method engine and framework] - note that there has been changes in API since then
* Documentation webpage for the latest git version and Meego version has been requested. See [https://bugs.meego.com/show_bug.cgi?id=14382 bug 14382] and [https://bugs.meego.com/show_bug.cgi?id=14994 bug 14994]
* Generate from source code with doxygen.

Some of the documentation is slighly outdated, and we are working to improve this. Use our [[Maliit#Communication_Channels|communication channels]] if there are any issues.

== Technical documentation ==
* [[Media:Technical-overview-widget-reloc.pdf|Widget relocation in MTF]]
* More to come!

== Blogposts et.c. ==
(most recent first)
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/06/20/brave-new-world/ Brave New World]
* Michael Hasselmannn: [http://taschenorakel.de/michael/2011/06/10/decent-examples-last/ Decent examples, at last!]
* Jon Nordby: [http://www.jonnor.com/2011/06/example-plugins-for-maliit-available/ Example plugins for Maliit]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/06/07/maliit-session-meego-spring-conference-2011/ Maliit Session at MeeGo Spring Conference 2011]
* Jan Arne Petersen: [http://blog.jpetersen.org/2011/05/29/maliit-packages-for-fedora/ Maliit packages for Fedora]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit/ Writing QML-based input methods for Maliit]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/05/10/painting-strategy-meegos-virtual-keyboard/ Painting Strategy in MeeGo's Virtual Keyboard]
* Jon Nordby: [http://www.jonnor.com/2011/04/introducing-maliit-on-screen-keyboard-in-gnome-3/ Introducing; Maliit on-screen keyboard in Gnome 3]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/04/10/customizing-meego-keyboard/ Customizing the Meego Keyboard]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/02/24/meego-input-methods-your-desktop/ MeeGo Input Methods for your desktop]

== Documentation working area ==
Here is the working area to keep track of the status of and work on the documentation.

* Goal: Every aspect of Maliit is well-documented, and the documentation easily accessible.
* Primary focus is on consumers of Maliit: Third-party developers and integrators

=== Important cases ===
* Developing a new input method plugin
* Using Maliit in an application
* Integrating Maliit in a product
* Developing a new engine plugin
* Adding support for additional application toolkits

=== Documentation status ===

{|border="1" cellpadding="4" class="wikitable"
|-
! Item
! Status
! Description
|-
| wiki.meego.com/Maliit || 90% || Our public webpage/wiki page, starting point for all information about our project. In pretty good shape.
|-
| apidocs.meego.com/git-tip || 10% || Our docs should be shown here. [https://bugs.meego.com/show_bug.cgi?id=14382 Bug 14382]
|-
| apidocs.meego.com/1.2 || 10% || Our docs should be shown here. [https://bugs.meego.com/show_bug.cgi?id=14994 Bug 14994]
|-
| colspan=3 | '''Framework'''
|-
| Overall architecture || 30% || Some docs exists in framework source tree, but is very outdated
|-
| Input Method/framework settings system || 0% ||
|-
| Input Method Plugin<->Framework interaction || 0% || What the interaction concepts are (both user and technical), and what is done on each side to support this
|-
| Input Method Framework Window handling || 0% || Passthrough window, Self-compositing, plugin pixmap drawing, rotation animation. Maybe covered by above item?
|-
| Input Method Plugin API || 60% || Example plugins exists, initial plugin SDK published. Need to remove the outdated tutorial from framework docs
|-
| Input Context DBus API || 0% ||
|-
| Toolkit integration concepts || 20% || Key concepts like pre-edit injection, and widget relocation should be documented. Purpose: make it easy for others to improve toolkit integration, and to bring new people up to date. Widget relocation is documented.
|-
| Toolkit integration/support status || 10% || Implicitly all keyboard features/IM are available for MTF. No documentation about plain Qt, QML, Clutter or Gtk+
|-
| Engine interfaces || ? || Correction/prediction/suggestion/handwriting, both plugin side and IM side
|-
| Feedback framework || ? ||
|-
| colspan=3 | '''Plugins'''
|-
| Meego Keyboard theming (CSS) || 100% || Docs in keyboard source tree. ||
|-
| Meego Keyboard layouts || 100% || Docs in keyboard source tree. ||
|-
| Meego Keyboard features || 100% || Documented on wiki page. ||
|-
|}

{{MaliitNavigationBar}}

Maliit/Documentation

2011-06-23T09:11:16Z

Jonnor: /* Documentation status */

[[Category:Maliit]][[Category:MeeGo Input Methods]]
{{MaliitNavigationBar}}

== FAQ ==
Frequently asked questions.

'''1. How to write my own input method?''' 
The recommended way to get started is to use the Maliit Plugin SDK and follow the [[Maliit/Documentation#Plugin_development_Quickstart|quickstart documentation]].

For developing an input method plugin, the primary interface is Qt and C++. The most relevant classes are: [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/minputmethodplugin.h MInputMethodPlugin],
[https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/mabstractinputmethod.h MAbstractInputMethod] and [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/mabstractinputmethodhost.h MAbstractInputMethodHost].

Since version 0.20.9-1 of the framework (May 2011), the MInputMethodQuick API allows one to also easily write input
methods using QML. See the [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/meego-keyboard-quick MeegoKeyboardQuick code] for an example.
As of May 2011 this interface is not yet feature complete with the C++ one. Contributions welcomed.

=== Unanswered questions ===
Please add any questions you may have here.

* Does Maliit work with non-compositing Window Managers?
* Which window managers are currently supported?

== Plugin Development Quickstart ==
How to get started developing plugins. This documentation is mainly for framework version 0.20.11-1 and newer. The C++ plugin API is compatible with all 0.20.x versions, and the QML interface is available from 0.20.9-1. Meego 1.2 has version 0.20.6. To develop there, one can install packages from Trunk/1.3.

Note that this is not intended to be 100% copy'n'paste step-by-step instructions. You may need to use common sense.

* [[Maliit/Installing|Install Maliit]] for your development environment
* [http://www.jonnor.com/files/maliit/maliit-plugin-sdk-0.1.0.tar.gz Download] the Maliit Plugin SDK
* Extract the examples
# In your favorite terminal:
tar -xf maliit-plugin-sdk-*.tar.gz
cd maliit-plugin-sdk/examples/
* Compile them
qmake
make
make install
* Have a look around. In the examples directory you will find a QML based plugin and a C++ based plugin.
# QML plugin code
ls plugins/quick/
# C++ plugin code
ls plugins/standard
* Try out one of the examples
# First enable both of the example input methods, along with the meego keyboard
gconftool-2 -s /meegotouch/inputmethods/onscreen/enabled -t list --list-type strings \
[libmeego-keyboard.so,en_gb.xml,libmeego-keyboard-quick.so,,libhelloworldplugin.so,,libexampleplugin.so,ExamplePluginSubview1]
# To activate the QML example
gconftool-2 -s /meegotouch/inputmethods/onscreen/active -t list --list-type string [libhelloworldplugin.so,]
# To instead activate the C++ example
gconftool-2 -s /meegotouch/inputmethods/onscreen/active -t list --list-type string [libexampleplugin.so,ExamplePluginSubview1]

# To test, start the Maliit server and a application with a Maliit inputcontext loaded
# Note: More documentation on this can be found on the Installing page
meego-im-uiserver > server.log &
QT_IM_MODULE=MInputContext apps/plainqt/plainqt

# Tap/double tap on a text field to activate the input method
# You should now be able to see an input method which allows you to click to input "Hello World"

* Try changing the plugin code a bit, and reinstall and restart the Maliit server to try again.
# Do changes (start simple, maybe by changing the "Hello World" string to something else)

# Rebuild and reinstall plugins
make && make install
# Remember to restart the Maliit server for it to pick up the changed plugin

If you have any issues, first try to solve the problem by reading the instructions again, and maybe other documentation. If you cannot solve it, ask for help through one of our communication channels.

There are also several open source input plugins that one look at. See for instance
* [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/m-keyboard Meego Keyboard]
* [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/meego-keyboard-quick Meego Keyboard Quick]
* [https://github.com/foolegg/cute-input-method/tree/maliit cute-input-method]

== Feature documentation ==
See [[Maliit#Features]]

== API documentation ==
* [http://apidocs.meego.com/1.1/platform/html/meego-im-framework/main.html Old MeeGo 1.1 Input method engine and framework] - note that there has been changes in API since then
* Documentation webpage for the latest git version and Meego version has been requested. See [https://bugs.meego.com/show_bug.cgi?id=14382 bug 14382] and [https://bugs.meego.com/show_bug.cgi?id=14994 bug 14994]
* Generate from source code with doxygen.

Some of the documentation is slighly outdated, and we are working to improve this. Use our [[Maliit#Communication_Channels|communication channels]] if there are any issues.

== Technical documentation ==
* [[Media:Technical-overview-widget-reloc.pdf|Widget relocation in MTF]]
* More to come!

== Blogposts et.c. ==
(most recent first)
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/06/20/brave-new-world/ Brave New World]
* Michael Hasselmannn: [http://taschenorakel.de/michael/2011/06/10/decent-examples-last/ Decent examples, at last!]
* Jon Nordby: [http://www.jonnor.com/2011/06/example-plugins-for-maliit-available/ Example plugins for Maliit]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/06/07/maliit-session-meego-spring-conference-2011/ Maliit Session at MeeGo Spring Conference 2011]
* Jan Arne Petersen: [http://blog.jpetersen.org/2011/05/29/maliit-packages-for-fedora/ Maliit packages for Fedora]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit/ Writing QML-based input methods for Maliit]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/05/10/painting-strategy-meegos-virtual-keyboard/ Painting Strategy in MeeGo's Virtual Keyboard]
* Jon Nordby: [http://www.jonnor.com/2011/04/introducing-maliit-on-screen-keyboard-in-gnome-3/ Introducing; Maliit on-screen keyboard in Gnome 3]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/04/10/customizing-meego-keyboard/ Customizing the Meego Keyboard]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/02/24/meego-input-methods-your-desktop/ MeeGo Input Methods for your desktop]

== Documentation working area ==
Here is the working area to keep track of the status of and work on the documentation.

* Goal: Every aspect of Maliit is well-documented, and the documentation easily accessible.
* Primary focus is on consumers of Maliit: Third-party developers and integrators

=== Important cases ===
* Developing a new input method plugin
* Developing a new engine plugin
* Integrating Maliit in a product
* Adding support for additional application toolkits

=== Documentation status ===

{|border="1" cellpadding="4" class="wikitable"
|-
! Item
! Status
! Description
|-
| wiki.meego.com/Maliit || 90% || Our public webpage/wiki page, starting point for all information about our project. In pretty good shape.
|-
| apidocs.meego.com/git-tip || 10% || Our docs should be shown here. [https://bugs.meego.com/show_bug.cgi?id=14382 Bug 14382]
|-
| apidocs.meego.com/1.2 || 10% || Our docs should be shown here. [https://bugs.meego.com/show_bug.cgi?id=14994 Bug 14994]
|-
| colspan=3 | '''Framework'''
|-
| Overall architecture || 30% || Some docs exists in framework source tree, but is very outdated
|-
| Input Method/framework settings system || 0% ||
|-
| Input Method Plugin<->Framework interaction || 0% || What the interaction concepts are (both user and technical), and what is done on each side to support this
|-
| Input Method Framework Window handling || 0% || Passthrough window, Self-compositing, plugin pixmap drawing, rotation animation. Maybe covered by above item?
|-
| Input Method Plugin API || 60% || Example plugins exists, initial plugin SDK published. Need to remove the outdated tutorial from framework docs
|-
| Input Context DBus API || 0% ||
|-
| Toolkit integration concepts || 20% || Key concepts like pre-edit injection, and widget relocation should be documented. Purpose: make it easy for others to improve toolkit integration, and to bring new people up to date. Widget relocation is documented.
|-
| Toolkit integration/support status || 10% || Implicitly all keyboard features/IM are available for MTF. No documentation about plain Qt, QML, Clutter or Gtk+
|-
| Engine interfaces || ? || Correction/prediction/suggestion/handwriting, both plugin side and IM side
|-
| Feedback framework || ? ||
|-
| colspan=3 | '''Plugins'''
|-
| Meego Keyboard theming (CSS) || 100% || Docs in keyboard source tree. ||
|-
| Meego Keyboard layouts || 100% || Docs in keyboard source tree. ||
|-
| Meego Keyboard features || 100% || Documented on wiki page. ||
|-
|}

{{MaliitNavigationBar}}

Maliit/Documentation

2011-06-22T17:22:43Z

Jonnor: /* Documentation status */

[[Category:Maliit]][[Category:MeeGo Input Methods]]
{{MaliitNavigationBar}}

== FAQ ==
Frequently asked questions.

'''1. How to write my own input method?''' 
The recommended way to get started is to use the Maliit Plugin SDK and follow the [[Maliit/Documentation#Plugin_development_Quickstart|quickstart documentation]].

For developing an input method plugin, the primary interface is Qt and C++. The most relevant classes are: [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/minputmethodplugin.h MInputMethodPlugin],
[https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/mabstractinputmethod.h MAbstractInputMethod] and [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/mabstractinputmethodhost.h MAbstractInputMethodHost].

Since version 0.20.9-1 of the framework (May 2011), the MInputMethodQuick API allows one to also easily write input
methods using QML. See the [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/meego-keyboard-quick MeegoKeyboardQuick code] for an example.
As of May 2011 this interface is not yet feature complete with the C++ one. Contributions welcomed.

=== Unanswered questions ===
Please add any questions you may have here.

* Does Maliit work with non-compositing Window Managers?
* Which window managers are currently supported?

== Plugin Development Quickstart ==
How to get started developing plugins. This documentation is mainly for framework version 0.20.11-1 and newer. The C++ plugin API is compatible with all 0.20.x versions, and the QML interface is available from 0.20.9-1. Meego 1.2 has version 0.20.6. To develop there, one can install packages from Trunk/1.3.

Note that this is not intended to be 100% copy'n'paste step-by-step instructions. You may need to use common sense.

* [[Maliit/Installing|Install Maliit]] for your development environment
* [http://www.jonnor.com/files/maliit/maliit-plugin-sdk-0.1.0.tar.gz Download] the Maliit Plugin SDK
* Extract the examples
# In your favorite terminal:
tar -xf maliit-plugin-sdk-*.tar.gz
cd maliit-plugin-sdk/examples/
* Compile them
qmake
make
make install
* Have a look around. In the examples directory you will find a QML based plugin and a C++ based plugin.
# QML plugin code
ls plugins/quick/
# C++ plugin code
ls plugins/standard
* Try out one of the examples
# First enable both of the example input methods, along with the meego keyboard
gconftool-2 -s /meegotouch/inputmethods/onscreen/enabled -t list --list-type strings \
[libmeego-keyboard.so,en_gb.xml,libmeego-keyboard-quick.so,,libhelloworldplugin.so,,libexampleplugin.so,ExamplePluginSubview1]
# To activate the QML example
gconftool-2 -s /meegotouch/inputmethods/onscreen/active -t list --list-type string [libhelloworldplugin.so,]
# To instead activate the C++ example
gconftool-2 -s /meegotouch/inputmethods/onscreen/active -t list --list-type string [libexampleplugin.so,ExamplePluginSubview1]

# To test, start the Maliit server and a application with a Maliit inputcontext loaded
# Note: More documentation on this can be found on the Installing page
meego-im-uiserver > server.log &
QT_IM_MODULE=MInputContext apps/plainqt/plainqt

# Tap/double tap on a text field to activate the input method
# You should now be able to see an input method which allows you to click to input "Hello World"

* Try changing the plugin code a bit, and reinstall and restart the Maliit server to try again.
# Do changes (start simple, maybe by changing the "Hello World" string to something else)

# Rebuild and reinstall plugins
make && make install
# Remember to restart the Maliit server for it to pick up the changed plugin

If you have any issues, first try to solve the problem by reading the instructions again, and maybe other documentation. If you cannot solve it, ask for help through one of our communication channels.

There are also several open source input plugins that one look at. See for instance
* [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/m-keyboard Meego Keyboard]
* [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/meego-keyboard-quick Meego Keyboard Quick]
* [https://github.com/foolegg/cute-input-method/tree/maliit cute-input-method]

== Feature documentation ==
See [[Maliit#Features]]

== API documentation ==
* [http://apidocs.meego.com/1.1/platform/html/meego-im-framework/main.html Old MeeGo 1.1 Input method engine and framework] - note that there has been changes in API since then
* Documentation webpage for the latest git version and Meego version has been requested. See [https://bugs.meego.com/show_bug.cgi?id=14382 bug 14382] and [https://bugs.meego.com/show_bug.cgi?id=14994 bug 14994]
* Generate from source code with doxygen.

Some of the documentation is slighly outdated, and we are working to improve this. Use our [[Maliit#Communication_Channels|communication channels]] if there are any issues.

== Technical documentation ==
* [[Media:Technical-overview-widget-reloc.pdf|Widget relocation in MTF]]
* More to come!

== Blogposts et.c. ==
(most recent first)
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/06/20/brave-new-world/ Brave New World]
* Michael Hasselmannn: [http://taschenorakel.de/michael/2011/06/10/decent-examples-last/ Decent examples, at last!]
* Jon Nordby: [http://www.jonnor.com/2011/06/example-plugins-for-maliit-available/ Example plugins for Maliit]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/06/07/maliit-session-meego-spring-conference-2011/ Maliit Session at MeeGo Spring Conference 2011]
* Jan Arne Petersen: [http://blog.jpetersen.org/2011/05/29/maliit-packages-for-fedora/ Maliit packages for Fedora]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit/ Writing QML-based input methods for Maliit]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/05/10/painting-strategy-meegos-virtual-keyboard/ Painting Strategy in MeeGo's Virtual Keyboard]
* Jon Nordby: [http://www.jonnor.com/2011/04/introducing-maliit-on-screen-keyboard-in-gnome-3/ Introducing; Maliit on-screen keyboard in Gnome 3]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/04/10/customizing-meego-keyboard/ Customizing the Meego Keyboard]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/02/24/meego-input-methods-your-desktop/ MeeGo Input Methods for your desktop]

== Documentation working area ==
Here is the working area to keep track of the status of and work on the documentation.

* Goal: Every aspect of Maliit is well-documented, and the documentation easily accessible.
* Primary focus is on consumers of Maliit: Third-party developers and integrators

=== Important cases ===
* Developing a new input method plugin
* Developing a new engine plugin
* Integrating Maliit in a product
* Adding support for additional application toolkits

=== Documentation status ===

{|border="1" cellpadding="4" class="wikitable"
|-
! Item
! Status
! Description
|-
| wiki.meego.com/Maliit || 90% || Our public webpage/wiki page, starting point for all information about our project. In pretty good shape.
|-
| apidocs.meego.com/git-tip || 10% || Our docs should be shown here. [https://bugs.meego.com/show_bug.cgi?id=14382 Bug 14382]
|-
| apidocs.meego.com/1.2 || 10% || Our docs should be shown here. [https://bugs.meego.com/show_bug.cgi?id=14994 Bug 14994]
|-
| colspan=3 | '''Framework'''
|-
| Overall architecture || 30% || Some docs exists in framework source tree, but is very outdated
|-
| Input Method/framework settings system || 0% ||
|-
| Input Method Plugin<->Framework interaction || 0% || What the interaction concepts are (both user and technical), and what is done on each side to support this
|-
| Input Method Framework Window handling || 0% || Passthrough window, Self-compositing, plugin pixmap drawing, rotation animation. Maybe covered by above item?
|-
| Input Method Plugin API || 60% || Example plugins exists, initial plugin SDK published. Need to remove the outdated tutorial from framework docs
|-
| Input Context DBus API || 0% ||
|-
| Toolkit integration concepts || 20% || Key concepts like pre-edit injection, and widget relocation should be documented. Purpose: make it easy for others to improve toolkit integration, and to bring new people up to date. Widget relocation is documented.
|-
| Toolkit integration/support status || 10% || Implicitly all keyboard features/IM are available for MTF. No documentation about plain Qt, QML, Clutter or Gtk+
|-
| Engine interfaces || ? || Correction/prediction/suggestion/handwriting, both plugin side and IM side
|-
| Feedback framework || ? ||
|-
| colspan=3 | '''Meego Keyboard'''
|-
| Meego Keyboard theming (CSS) || 100% || Docs in keyboard source tree. ||
|-
| Meego Keyboard layouts || 100% || Docs in keyboard source tree. ||
|-
| Meego Keyboard features || 100% || Documented on wiki page. ||
|-
|}

{{MaliitNavigationBar}}

Maliit/Roadmap

2011-06-22T09:27:06Z

Jonnor: /* MeeGo 1.3 */

{{MaliitNavigationBar}}

Submit your ideas in [[Maliit/Ideas|Ideas page]] to get considered to be put into the roadmap.

== MeeGo 1.3 ==
Development in in progress.

MeeGo 1.3 will have Maliit 1.0.

* New maliit-* package-names (DONE)
* Settings applet for meego-ux-settings
* Better integration with standard applications

== Maliit 1.0 ==
Development in progress.

With Maliit 1.0 the goal is long-term API stability for application and input method plugin API.

* '''0.2x''': Still uses MeeGo Touch.
* '''0.8x''': Compiles MeeGo Touch free version by default, has legacy build option. (DONE)
** Maliit now an [http://lists.meego.com/pipermail/meego-dev/2011-June/483406.html independent project].
** Installation paths, library names and GConf keys now follow new Maliit naming conventions.
** Legacy LMT build can be done using qmake CONFIG+=nomeegotouch (works in -framework and -plugins repo).
** No API changes in plugin or application API! New library structure will require recompilation though.
* '''0.9x''': Alpha release that will lead up to Maliit 1.0
** Will contain API cleanups (not LMT related, but rather about removing cruft and cleanup).
** API cleanup should be done for all Maliit libraries (including engines and feedback API).
** In first release for the 0.9x series, the C++ based reference VKB (Maliit Keyboard) will be LMT-free.
* '''1.0''': Stable release

=== Framework ===
* Use D-Bus datatype instead of serialized Qt types in D-Bus API (DONE)
* [[Maliit/Ideas/Supporting_Non_X11_Platforms|Support for non X11 platform]]
* Better support for Qt applications not linked to MeeGo Touch
** Orientation change
* Unified, UI independent, settings API
** Probably even hide the framework's GConf usage behind some API that can be used by apps and plugins.

=== MeeGo Keyboard ===
* Key magnification and accent pop-ups (DONE)
* New word prediction widgets: Word Ribbon (DONE)
* Extended support for CJK languages
* Remove libmeegotouch dependency

== MeeGo 1.2 ==
All items in this section are DONE.

=== Framework ===
* private D-Bus connection
* new information exposures:
** anchor position
** cursor position
* libmeegotouch removal
* self-compositing
* self-rotation animation

=== Engine framework ===
* New interface: Handwriting recognition
* New functionality: Dynamic virtual keyboard layout

[[Category:Maliit]]
[[Category:MeeGo Input Methods]]

{{MaliitNavigationBar}}

Maliit/Roadmap

2011-06-22T09:26:44Z

Jonnor: /* MeeGo 1.3 */

{{MaliitNavigationBar}}

Submit your ideas in [[Maliit/Ideas|Ideas page]] to get considered to be put into the roadmap.

== MeeGo 1.3 ==
Development in in progress.

MeeGo 1.3 will have Maliit 1.0.

* New package-names (DONE)
* Settings applet for meego-ux-settings
* Better integration with standard applications

== Maliit 1.0 ==
Development in progress.

With Maliit 1.0 the goal is long-term API stability for application and input method plugin API.

* '''0.2x''': Still uses MeeGo Touch.
* '''0.8x''': Compiles MeeGo Touch free version by default, has legacy build option. (DONE)
** Maliit now an [http://lists.meego.com/pipermail/meego-dev/2011-June/483406.html independent project].
** Installation paths, library names and GConf keys now follow new Maliit naming conventions.
** Legacy LMT build can be done using qmake CONFIG+=nomeegotouch (works in -framework and -plugins repo).
** No API changes in plugin or application API! New library structure will require recompilation though.
* '''0.9x''': Alpha release that will lead up to Maliit 1.0
** Will contain API cleanups (not LMT related, but rather about removing cruft and cleanup).
** API cleanup should be done for all Maliit libraries (including engines and feedback API).
** In first release for the 0.9x series, the C++ based reference VKB (Maliit Keyboard) will be LMT-free.
* '''1.0''': Stable release

=== Framework ===
* Use D-Bus datatype instead of serialized Qt types in D-Bus API (DONE)
* [[Maliit/Ideas/Supporting_Non_X11_Platforms|Support for non X11 platform]]
* Better support for Qt applications not linked to MeeGo Touch
** Orientation change
* Unified, UI independent, settings API
** Probably even hide the framework's GConf usage behind some API that can be used by apps and plugins.

=== MeeGo Keyboard ===
* Key magnification and accent pop-ups (DONE)
* New word prediction widgets: Word Ribbon (DONE)
* Extended support for CJK languages
* Remove libmeegotouch dependency

== MeeGo 1.2 ==
All items in this section are DONE.

=== Framework ===
* private D-Bus connection
* new information exposures:
** anchor position
** cursor position
* libmeegotouch removal
* self-compositing
* self-rotation animation

=== Engine framework ===
* New interface: Handwriting recognition
* New functionality: Dynamic virtual keyboard layout

[[Category:Maliit]]
[[Category:MeeGo Input Methods]]

{{MaliitNavigationBar}}

Maliit/Roadmap

2011-06-21T16:50:17Z

Jonnor: /* Framework */

{{MaliitNavigationBar}}

Submit your ideas in [[Maliit/Ideas|Ideas page]] to get considered to be put into the roadmap.

== MeeGo 1.3 ==
Development in in progress.

=== Maliit 1.0 ===
With http://lists.meego.com/pipermail/meego-dev/2011-June/483406.html Maliit declared itself as an independent project. To strengthen the position of Maliit, we decided to go with a proper rebranding. This involves cleaning up old Harmattan/MeeGo Touch cruft in source code, installation paths, GConf keys, etc.

The upcoming changes will be reflected in new package names for MeeGo and the following version numbers for the framework libraries:
* '''0.2x''': Still uses MeeGo Touch.
* '''0.8x''': Compiles MeeGo Touch free version by default.
** Installation paths, library names and GConf keys now follow new Maliit naming conventions.
** This is a transitional release where legacy LMT support still exists. Legacy LMT build can be surpressed with qmake CONFIG+=nomeegotouch, (works in framework and plugins repo).
** No API changes in plugin or application API! New library structure will require recompilation though.
* '''0.9x''': Alpha release that will lead up to Maliit 1.0
** Will contain API cleanups (not LMT related, but rather about removing cruft and cleanup).
** API cleanup should be done for all Maliit libraries (including engines and feedback API).
** In first release for the 0.9x series, the C++ based reference VKB (Maliit Keyboard) will be LMT-free.
* '''1.0'''
** From here on, we would consider our API stable, goal is API compatibility (not necessarily BC) for MeeGo 1.4, too, as we really don't want to force input method developers to keep adjusting to changing API's.

=== Framework ===
* Use D-Bus datatype instead of serialized Qt types in D-Bus API (DONE)
* [[Maliit/Ideas/Supporting_Non_X11_Platforms|Support for non X11 platform]]
* Better support for Qt applications not linked to MeeGo Touch
** Orientation change
* Control panel replacement
** Unify settings, probably even hide the framework's GConf usage behind some API that can be used by apps and plugins.
** Take a look at meego-ux-settings, and how we could integrate into that, contact tripzero.

=== MeeGo Keyboard ===
* Key magnification and accent pop-ups (DONE)
* New word prediction widgets: Word Ribbon (DONE)
* Extended support for CJK languages
* Remove libmeegotouch dependency (or perhaps develop the qml keyboard further?)

== MeeGo 1.2 ==
All items in this section are DONE.

=== Framework ===
* private D-Bus connection
* new information exposures:
** anchor position
** cursor position
* libmeegotouch removal
* self-compositing
* self-rotation animation

=== Engine framework ===
* New interface: Handwriting recognition
* New functionality: Dynamic virtual keyboard layout

[[Category:Maliit]]
[[Category:MeeGo Input Methods]]

{{MaliitNavigationBar}}

Maliit/Rebranding

2011-06-21T16:49:43Z

Jonnor: Replaced content with "Moved to Maliit/Roadmap"

Moved to [[Maliit/Roadmap]]

Maliit/Roadmap

2011-06-21T16:49:19Z

Jonnor: /* MeeGo 1.3 */ move maliit 1.0 / rebranding page into roadmap

{{MaliitNavigationBar}}

Submit your ideas in [[Maliit/Ideas|Ideas page]] to get considered to be put into the roadmap.

== MeeGo 1.3 ==
Development in in progress.

=== Maliit 1.0 ===
With http://lists.meego.com/pipermail/meego-dev/2011-June/483406.html Maliit declared itself as an independent project. To strengthen the position of Maliit, we decided to go with a proper rebranding. This involves cleaning up old Harmattan/MeeGo Touch cruft in source code, installation paths, GConf keys, etc.

The upcoming changes will be reflected in new package names for MeeGo and the following version numbers for the framework libraries:
* '''0.2x''': Still uses MeeGo Touch.
* '''0.8x''': Compiles MeeGo Touch free version by default.
** Installation paths, library names and GConf keys now follow new Maliit naming conventions.
** This is a transitional release where legacy LMT support still exists. Legacy LMT build can be surpressed with qmake CONFIG+=nomeegotouch, (works in framework and plugins repo).
** No API changes in plugin or application API! New library structure will require recompilation though.
* '''0.9x''': Alpha release that will lead up to Maliit 1.0
** Will contain API cleanups (not LMT related, but rather about removing cruft and cleanup).
** API cleanup should be done for all Maliit libraries (including engines and feedback API).
** In first release for the 0.9x series, the C++ based reference VKB (Maliit Keyboard) will be LMT-free.
* '''1.0'''
** From here on, we would consider our API stable, goal is API compatibility (not necessarily BC) for MeeGo 1.4, too, as we really don't want to force input method developers to keep adjusting to changing API's.

=== Framework ===
* Use D-Bus datatype instead of serialized Qt types in D-Bus API (DONE)
* [[Maliit/Ideas/Supporting_Non_X11_Platforms|Support for non X11 platform]]
* Better support for Qt applications not linked to MeeGo Touch
** Orientation change
* Control panel replacement
** Unify settings, probably even hide the framework's GConf usage behind some API that can be used by apps and plugins.
** Take a look at meego-ux-settings, and how we could integrate into that, contact tripzero.
* [[Maliit/Rebranding|Maliit rebranding]]

=== MeeGo Keyboard ===
* Key magnification and accent pop-ups (DONE)
* New word prediction widgets: Word Ribbon (DONE)
* Extended support for CJK languages
* Remove libmeegotouch dependency (or perhaps develop the qml keyboard further?)

== MeeGo 1.2 ==
All items in this section are DONE.

=== Framework ===
* private D-Bus connection
* new information exposures:
** anchor position
** cursor position
* libmeegotouch removal
* self-compositing
* self-rotation animation

=== Engine framework ===
* New interface: Handwriting recognition
* New functionality: Dynamic virtual keyboard layout

[[Category:Maliit]]
[[Category:MeeGo Input Methods]]

{{MaliitNavigationBar}}

Devices/ExoPC

2011-06-15T09:19:54Z

Jonnor: /* How to install latest MeeGo Snapshot */

ExoPCs were given out at the Mobile World Congress 2011 and [[Local MeeGo Networks/MeeGo Network Finland/MeeGo Summit FI|MeeGo Summit.fi in Apr 2011]].

== How to install latest MeeGo Snapshot ==
* Download img from http://download.meego.com/snapshots/latest/images/meego-tablet-ia32-pinetrail/
* Write to your usb stick with '''dd if=meego.img of=/dev/sdb bs=4M'''
* Put usb stick in tablet and boot up, press "BBS" (on the touchscreen), select usb stick, now you need a usb keyboard to select install only option
** You can go through the bootloader using the button in the top left corner of the screen, short press to move to the next entry, long press to boot it. USB keyboard is optional.

== Mobile World Congress 2011 / MeeGo Summit.fi Machines : Update Repos ==

These machines were pre-installed with MeeGo 1.1 using a trunk-daily build of 1.1.90.2.20110209.4 (see /etc/zypp/repos/core.repo on the device); this is no longer available.

In the absence of a more stable repo an alternative is to track the latest package set by setting
baseurl=http://download.meego.com/trunk-daily/builds/trunk/latest/repos/oss/ia32/packages/
in the core.repo file.

Then:
zypper ref

(If anyone is brave enough to run ''zypper up'' and potentially need to reinstall then please say how this works.)

I tried that against the latest weekly repo at that time (http://repo.meego.com/MeeGo/builds/1.1.90/1.1.99.2.20110412.6/repos/oss/ia32/packages/) and first it hung on updating libc. After a reboot it ran through, but after one more reboot the Tablet UX didn't come back up anymore. Didn't investigate it further. I'll most likely use these instructions: http://meego.com/downloads/releases/1.2/meego-tablet-developer-preview and the image for aforementioned weekly.

--[[User:Dm8tbr|Dm8tbr]] 04:30, 18 April 2011 (UTC)

== Connecting Qt Creator to the Device ==
Go to Tools->Options; then Projects section, MeeGo Device Configurations tab.

Note that the meego user seems to need sudo rights to be able to run the remote execution:
cat <<EOF > /etc/sudoers.d/su-meego
meego ALL=(ALL) NOPASSWD: ALL
EOF
chmod 440 /etc/sudoers.d/su-meego

sed -i -e's/##includedir/#includedir/' /etc/sudoers

Also, for some reason, /usr/local and /usr/local/bin end up as root:root, mode 770. Fix this with:
sudo chmod 755 /usr/local
sudo chmod 755 /usr/local/bin
This looks like it's due to Qt Creator packaging

== Old Installation Notes ==

'''Warning:''' both the handset and netbook images running on the ExoPC have some problems as
of 1/30/2011. See below.
'''Warning:''' as with any other device, if you incorrectly reflash the bootloader and/or kernel, you may '''brick''' your system.

Sometimes the unit won't boot when a USB mouse is plugged in. An external keyboard doesn't cause the same problems. A mouse can be attached as soon as the MeeGo splashscreen appears. This might be a power problem that would be resolved by a USB hub with an external supply.

Installing the Handset image before the Netbook saves a bit of trouble if both are desired.

The version of parted that is invoked by the MeeGo installers [http://bugs.meego.com/show_bug.cgi?id=12945 will not resize an NTFS partition], so if you want to preserve Windows, use another partitioning tool before booting the MeeGo USB stick. [http://www.sysresccd.org/Main_Page systemrescuecd] worked fine.

The installation described here shrank the Windows partition to the (recommended minimum) 20 GB, then created an extended (logical) partition in the remaining space with a 2 GB swap partition and two primary (Is this right?) partitions of equal size in the remaining space.

Windows may come up and say that the partition table has been corrupted and that it will repair it ;-). The result is that the boot flag is set for the Win System partition, which prevents the extlinux bootloader from starting. To fix the problem, boot once more from the handy systemrescuecd stick and clear the duplicate boot flag from the System partition. Presto: your MeeGo install is again accessible.

== Installation ==

[[File:systemrescuecd_gparted_ExoPC.jpg|750px|frameless|Result of successful partitioning for triple-boot. Booting Windows may cause it to set the "boot" flag on its System partition as shown here and prevent extlinux from loading. Boot again with the systemrescuecd stick to clear the duplicate flag.]]

The ExoPC has an unlocked bootloader, so installation is relatively simple. First [http://meego.com/devices/netbook/installing-meego-your-netbook prepare a USB stick] with the image of your choice. After holding the power button for 4 seconds to start the boot process, touch the "Setup" soft button in the upper-righthand corner of the screen and disable "Quiet Boot." Boot again and touch the "BBS" soft button to manually select your USB drive as the boot device.

The netbook image does not create a useful /boot/extlinux/extlinux.conf file. One way of solving the problem is to install the handset image first, mount the handset image from the netbook image and just copy over the extlinux.conf file. Copy the entry for the handset image over to the end of the extlinux.conf file and change the details in order to create a file that works for all the images, then copy back to the handset image.

Don't forget to run "zypper update" from a terminal window as soon as your image is installed.

Warning: always unmount the USB filesystem before pulling the Flash drive out of the slot.

== Handset-specific notes ==

Touchscreen works great in the as-installed image. WiFi does not. A symptom of the problem is that both the ath9k (correct) and ath3K (wrong) kernel modules are autoloaded at boot time. Edit /etc/modprobe.d/blacklist.conf and add "blacklist ath3k" and then reboot. Unfortunately, WiFi still doesn't come up even though "lsmod" shows the same drivers as on netbook image, whose WiFi works great. "dmesg" says "ADDRCONF(NETDEV_UP): wlan0: link is not ready.

Before WiFi is working the easiest ways to get files onto the handset images are either from a mounted USB stick filesystem or by mounting the MeeGo netbook filesystem read-only and copying. In order to accomplish the latter, type "fdisk -l" to list the existing partitions. Create the directory where the netbook filesystem will be mounted, e.g. "mkdir -p /netbook". Then, assuming your netbook partition is /dev/sdaX and the filesystem type is ext3, enter "mount -t ext3 -o ro /dev/sdaX /netbook". Then "ls /netbook" will display the files on the netbook partition.

== Netbook-specific notes ==

WiFi works great with the as-installed netbook image.

As installed, the netbook image [http://bugs.meego.com/show_bug.cgi?id=9524 does not have a working touchscreen]. The system responds to a screen touch by darkening slightly and moving the cursor to the upper-lefthand corner. The needed driver, hid_egalax, is not autoloaded. Manually loading the driver with "modprobe -i hid_egalax" makes the touchscreen fully functional about half the time. Other times the behavior seems to be unaffected by the driver load.

=== Netbook trunk (1.2) ===

Some notes about installing a more recent MeeGo netbook image (I used meego-netbook-ia32-1.2.80.0.20110503.2.img) on ExoPC hardware:

# Installation needs an external keyboard, but went smoothly. However, on first boot (where you have to enter default user/password etc.), the external keyboard seemed to cause some power issue (even with the tablet plugged into its adapter), where X respawns too quickly.
#: To work around this, I followed [http://forum.meego.com/showthread.php?t=447 these instructions], summarised here:
## Plug in USB keyboard.
## Boot and start bashing the space key on the external keyboard (to interrupt grub).
## In the grub menu, press Tab so you can edit the kernel boot options.
## Append ' s' (space then 's', no quotation marks). This will mean you can boot into single user mode before X starts (and the keyboard causes X to continually respawn).
## Once you have a console available, run <code>startx</code> to get a minimal X environment.
## In the terminal window, run <code>/usr/bin/firstboot</code>. This starts the normal firstboot environment with the keyboard plugged in. Fill in the necessary.
## Once you're done with firstboot, back in the terminal, use the <code>halt</code> command to shut down.
## You should now be able to boot the tablet with the keyboard plugged in.
# Once you've booted successfully, you'll probably need to use the Terminal application to do stuff.
# With more recent images, hid_egalax does appear to be autoloaded (see the previous section). However, the pointer behaviour is still a little skittish. I found that installing evtouch stabilised it a bit:
#: <code>zypper in xorg-x11-drv-evtouch</code>
# To hide the pointer, edit /etc/sysconfig/uxlaunch and add a line like this to the end of the file:
#: <code>xopts=-nocursor</code>
#: But, once the pointer is gone, it is tricky to put the pointer to the top of the screen to see the toolbar (with links to MyZone etc.). However, if you've got an external keyboard plugged in, you can press the Windows key on the external keyboard to get there.
# This one is for those of you interested in running HTML5/JS web apps on netbook: The version of Chromium installed by default on the netbook image is quite old, and behaves pretty poorly for frameworks like [http://www.sencha.com/products/touch/ Sencha Touch]. You can instead install a developer build of Chrome, which works much better.
#:# Install lsb:
#:#: <code>sudo zypper in lsb</code>
#:# Download a developer build of Chrome (to replace Chromium) from
#:#: http://www.google.com/chrome/intl/en/eula_dev.html?dl=unstable_i386_rpm
#:# Install the RPM:
#:#: <code>sudo rpm -i google-chrome-unstable_current_i386.rpm</code>
#:# Run it:
#:#: <pre>google-chrome</pre>
#:#: NB on first run, it asks you to select a search engine; I chose Yahoo!, as selecting Google didn't work (ironically).
# On the other hand, if you're happy with the version of Chromium on the netbook image, and just want to be able to use it with touch, the [https://chrome.google.com/webstore/detail/ncegfehgjifmmpnjaihnjpbpddjjebme chromeTouch extension] works pretty well. However, this mucks up touch tracking in Sencha Touch.
# I had pretty much zero luck getting a decent virtual keyboard to work. I tried matchbox-keyboard, the meegotouch keyboard ([http://wiki.meego.com/Maliit Maliit]), and fvkbd. matchbox-keyboard and fvkbd at least appeared onscreen; I had no luck with the meegotouch keyboard at all.
#: I ended up keeping fvkbd with the following small edits:
#:* I changed its .desktop file (/usr/share/applications/fvkbd.desktop) to run the keyboard docked to the bottom of the screen, by changing the Exec line to:
#:*: <code>Exec=fvkbd-gtk -d -l keyboard-s.xml</code>
#:*: (note the extra -d to dock to the bottom of the screen)
#:* I also edited the keyboard-s.xml file (/usr/share/fvkbd/keyboard-s.xml) and set the width to 1366 and height to 330 (attributes on the outermost XML element). This makes the keyboard properly span the screen without being truncated (though I didn't work out how to centre the keys on the background)
#: To use the keyboard, start the fvkbd application first (from the Applications zone), then the application you want to use. The keyboard then sits on top of the application. This can be useful for emergencies, but it's not really adequate for full, everyday use.
# For some reason I couldn't discover, the screen dims when the power lead is unplugged. I was unable to figure out how to prevent this from happening (I tried looking through the BIOS, using xset, looking at upower, tried to turn off acpi etc. to no avail). However, there is a utility for setting the backlight brightness called <code>xbacklight</code> which at least helps you reset the screen brightness (the netbook image has no software control for this, and the tablet has no hardware keys for it).
#: Install it with:
#: <code>sudo zypper in xbacklight</code>
#: Then, to set the backlight brightness to 100%, do:
#: <code>xbacklight -set 100</code>
#: (Obviously, this is less than ideal. If anyone knows how to permanently prevent the screen from dimming when the power is unplugged, please let me know.)
# The ExoPC has a light sensor (tiny rectangle next to the power LEDs in the top left). When it's on, a reduction in the ambient light causes the screen to dim. This can be quite annoying in a British spring as bright sunlight rapidly alternates with storm clouds.
#: You can turn off the light sensor temporarily with:
#: <code>sudo echo 0 > /sys/devices/platform/asus_laptop/ls_switch</code>
#: However, you have to do this manually on each boot. There's probably some way to switch it off permanently, but no one on the internet has written it down. So the easiest thing for me to do was write a script in <code>/etc/init.d/ls_switch</code> to run on each boot (see below).
#: Make sure you <code>sudo chmod +x /etc/init.d/ls_switch</code> too.
#: With this script in place, set it to run on each boot with:
#: <code>chkconfig --add ls_switch</code>
#: When you reboot, the light sensor should be off.

<pre>
# script to go in /etc/init.d/ls_switch
#!/bin/sh
#
# ls_switch Turn light sensor off
#
# chkconfig: 2345 08 92
# description: Turns light sensor off on boot
#
#
### BEGIN INIT INFO
# Provides: ls_switch
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: turn off light sensor
# Description: turn off light sensor
### END INIT INFO

# Source function library.
. /etc/init.d/functions

case "$1" in
start)
echo "disabling light sensor"
echo 0 > /sys/devices/platform/asus_laptop/ls_switch
RETVAL=$?
;;
stop)
RETVAL=0
;;
*)
echo "Usage: ls_switch {start|stop}"
RETVAL=2
;;
esac

exit $RETVAL
</pre>

=== Acknowledgements ===

Hat-tip to Bill Pearson of Intel for recommending the ExoPC.

[[Category:Hardware]]

== Hardware Fixes ==

Please add steps here how to get hardware features working on MeeGo Tablet UX that don't work out of the box:

=== HDMI Output ===

This can be enabled by copying the following two files from a WeTab OS installation ([http://www.wetab-community.com/index.php?/topic/12074-hdmi-ausgang/ source link]):

<pre>
/usr/bin/tiitoo-hdmi-daemon
/lib/firmware/chrontel/fw7036.bin
</pre>

After you have copied the files, you need to load two kernel modules and start the HDMI Daemon:

<pre>
sudo modprobe i2c-i801
sudo modprobe i2c-dev
sudo tiitoo-hdmi-daemon
</pre>

=== Accelerometer ===

The fix to [http://bugs.meego.com/10886 bug 10886] was to remove the MeeGo Sensors module in the kickstart file of the Tablet Image. This, however, causes the sensor to not be accessible to Qt Mobility ([http://bugs.meego.com/17461 bug 17461]). The workaround as described in [http://bugs.meego.com/17461 bug 17461] is as follows:

* Download the RPM: [http://download.meego.com/snapshots/1.2.0.90.1.20110525.2/repos/oss/ia32/packages/i586/libqtsensors1-1.2.0~beta0+git2726-10.11.i586.rpm libqtsensors1-1.2.0~beta0+git2726-10.11.i586.rpm]
* Extract it: <code>rpm2cpio libqtsensors1-1.2.0~beta0+git2726-10.11.i586.rpm | cpio -idv</code>
* Copy the module (as root): <code>cp usr/lib/qt4/plugins/sensors/libqtsensors_meego.so /usr/lib/qt4/plugins/sensors/</code>

To test, you can install the '''qt-mobility-examples''' package (using <code>zypper install qt-mobility-examples</code>) and run one of the examples:

$ /usr/lib/qtmobility/examples/accel
loaded the Generic plugin
loaded the grue plugin
Loaded the MeeGo sensor plugin
New sensor "accelerometersensor" interface created with session id 10 ...
acceleration: "0.12 0.27 2.35"
acceleration: "0.12 0.29 2.39"
acceleration: "0.10 0.29 2.39"
acceleration: "0.11 0.30 2.33"

=== Display brightness ===

If for some reason the display backlight becomes too dark, you can use the following command as root to set the brightness:

echo 15 >/sys/devices/virtual/backlight/acpi_video0/brightness

The value 15 has been obtained from the file <code>/sys/devices/virtual/backlight/acpi_video0/max_brightness</code>.

Another option is to install xbacklight (available in the MeeGo repos) and run:

xbacklight -set 100

You don't need to be root to do this.

Maliit/Installing

2011-06-10T15:16:49Z

Jonnor: /* openSUSE */

[[Category:Maliit]][[Category:MeeGo Input Methods]]
{{MaliitNavigationBar}}

== Installing ==

=== Meego ===
Meego Input Methods comes preinstalled on:
* Meego Handset UX 1.1 and later
* Meego Tablet UX 1.2 and later

'''Meego Netbook UX'''

These steps have been tested on Meego 1.1.

* Enable the 'handset' repository. For example:

$ sudo zypper addrepo <nowiki>http://repo.meego.com/MeeGo/releases/1.1/handset/repos/ia32/packages/</nowiki> handset
$ sudo zypper refresh

* Install these packages:
** meegotouch-inputmethodbridges
** meegotouch-inputmethodkeyboard

sudo zypper install meegotouch-inputmethodkeyboard meegotouch-inputmethodbridges

* Modify <code>/etc/xdg/autostart/meego-im-uiserver.desktop</code> to look like this:

[Desktop Entry]
Exec=/usr/bin/meego-im-uiserver -target slate -bypass-wm-hint
X-Moblin-Priority=High
OnlyShowIn=X-MEEGO-HS;X-MEEGO-NB

This will work with 1024x600 resolution. Replace 'slate' with other code if you have different resolution. See /etc/meegotouch/devices.conf for different codes.

* Add this line to ~/.bashrc (any better place in X configs? /etc/X11/xinitrc-common failed for me) to activate the inputmethod plugin for Qt-based programs:
export QT_IM_MODULE=MInputContext

* Relogin (or reboot) to desktop

=== Ubuntu (10.04 Lucid Lynx / 10.10 Maveric Meerkat) ===
The MeeGo Input Methods are not yet in any official Ubuntu repository. However, the packages are available through [http://launchpad.net Launchpad]. They are provided to ease development of input method plugins, without the need of using the MeeGo SDK or even scratchbox.

To install the packages, you will need to add two Launchpad PPA's to your system's software sources:
* Under System → Administration → Software Sources, select "Other Software" '''or'''
**Alternatively you can run Synaptics Package Manager and choose the menu ''Setting'' --> ''Package Sources'' where you can add the following PPA's in the tab "Other Software"
*<code>Add ppa:openismus-team/openismus-meego-im</code>
*<code>Add ppa:kubuntu-ppa/backports</code> (needed for Qt 4.7, on Lucid/Meerkat)
*Install meego-keyboard-dev and meegotouch-demos-widgetsgallery (for simple testing) through Synaptics Package Manager '''or'''
**using this command line command(make sure that Synaptics is closed already):
sudo apt-get update && sudo apt-get install meego-keyboard-dev meegotouch-demos-widgetsgallery

=== Debian, and Ubuntu derivatives ===
You might be able to use the packages above. Let us know to which extend you succeed with this.

=== Fedora ===
For Fedora there are no Maliit packages available in the Fedora repository. But there are packages built with the [http://openbuildservice.org/ Open Build Service (OBS)]. To install them:
* Download [http://download.opensuse.org/repositories/home:/janarnepetersen/Fedora_15/home:janarnepetersen.repo .repo file] and save it as ''/etc/yum.repos.d/maliit.repo''.
* Install the packages ''meego-inputmethodkeyboard'' and ''meego-inputmethodbridges'' with the ''Add/Remove Software application''

For testing Maliit:
* As user start ''meego-im-uiserver'' in a terminal
* Run ''GTK_IM_MODULE=meego-im gedit''

=== openSUSE 11.4 & Factory ===
The work-in-progress can be found at

http://download.opensuse.org/repositories/home:/janarnepetersen/openSUSE_11.4/

http://download.opensuse.org/repositories/home:/janarnepetersen/openSUSE_Factory/

=== Arch Linux ===
Preliminary git packages are available [http://aur.archlinux.org/packages.php?O=0&K=meegotouch-input&do_Search=Go in AUR]

To install framework, keyboard, Qt and Gtk+ support:
yaourt -S meegotouch-inputmethodkeyboard meegotouch-inputmethodbridges

Substitute yaourt with your favorite AUR helper.

=== Maemo 5 (Fremantle) ===

Warning: This is a rough tech demo and as such, fairly useless. Also, don't activate [http://wiki.maemo.org/Extras-devel Maemo's extras-devel repo] unless you exactly know what you are doing - it can brick your device!

* Install meego-keyboard-quick (needs extras-devel),
* Install meego-im-demos
* Open a terminal, start the MeeGo Input Methods service:

$ meego-im-uiserver -bypass-wm-hint -software -graphicssystem raster

* Open a second terminal, to run the meego-im-demos-plainqt application:

$ export QT_IM_MODULE=MInputContext
$ meego-im-demo-plainqt -fullscreen -software -graphicssystem raster

Instead of the test application, one should be able to use it in any other Qt application, as long as the MeeGo Input Methods service is running and the QT_IM_MODULE environment variable is set correctly.

=== Other GNU/Linux ===
Grab the source source code from the git repositories above.

Meego Input Methods uses the qmake build system. So, to do a standard build and install, do:
qmake
make
make install

'''Dependencies'''
* All components have a hard dependency on Qt 4.7.
* Framework uses libmeegotouch by default. Pass CONFIG+=nomeegotouch to qmake to disable.
* Framework will build a setting applet for meegotouch-controlpanel by default. Pass CONFIG+=noduicontrolpanel to qmake to disable.
* Keyboard uses meego feedback framework (with reactionmaps) by default. Pass CONFIG+=noreactionmaps to qmake to disable.
* Keyboard currently has a hard dependency on libmeegotouch.

Work is ongoing to reduce the amount of dependencies in the different components.

== Using ==
To quickly test your installation, it is recommended to use the widgetsgallery:
# Make sure you have a compositing window manager running: Go to System → Appearance, select "Visual Effects" and choose either normal or extra.
# Start the meego-im-uiserver (responsible for handling input method plugins and communication with the application) using a shell:
meego-im-uiserver -software -bypass-wm-hint
# Test virtual keyboard in MeeGo Touch's widgetsgallery (in a seperate shell):
QT_IM_MODULE=MInputContext widgetsgallery

To integrate it with your system or product, use the distro-recommended way to start above daemon and setting the environment variable for all applications.

== Debugging tips ==
# Verify that the correct environment variables are set to load the correct input context (see above).
# Run meego-im-uiserver with the "-output-level debug" flag (in addition to any other existing flags).
# If problems with QT-based application, set the MIC_ENABLE_DEBUG=true. This will make the inputcontext output debug information.
# If problems with GTK+ applications, recompile meegotouch-inputmethodbridges with the --enable-debug flag. This will make the inputcontext output debug information.

{{MaliitNavigationBar}}

Maliit/Documentation

2011-06-10T08:35:31Z

Jonnor: reorder sections to put the important stuff on top

[[Category:Maliit]][[Category:MeeGo Input Methods]]
{{MaliitNavigationBar}}

== FAQ ==
Frequently asked questions.

'''1. How to write my own input method?''' 
The recommended way to get started is to use the Maliit Plugin SDK and follow the [[Maliit/Documentation#Plugin_development_Quickstart|quickstart documentation]].

For developing an input method plugin, the primary interface is Qt and C++. The most relevant classes are: [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/minputmethodplugin.h MInputMethodPlugin],
[https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/mabstractinputmethod.h MAbstractInputMethod] and [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework/blobs/master/src/mabstractinputmethodhost.h MAbstractInputMethodHost].

Since version 0.20.9-1 of the framework (May 2011), the MInputMethodQuick API allows one to also easily write input
methods using QML. See the [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/meego-keyboard-quick MeegoKeyboardQuick code] for an example.
As of May 2011 this interface is not yet feature complete with the C++ one. Contributions welcomed.

=== Unanswered questions ===
Please add any questions you may have here.

== Plugin Development Quickstart ==
How to get started developing plugins. This documentation is mainly for framework version 0.20.11-1 and newer. The C++ plugin API is compatible with all 0.20.x versions, and the QML interface is available from 0.20.9-1. Meego 1.2 has version 0.20.6. To develop there, one can install packages from Trunk/1.3.

Note that this is not intended to be 100% copy'n'paste step-by-step instructions. You may need to use common sense.

* [[Maliit/Installing|Install Maliit]] for your development environment
* [http://www.jonnor.com/files/maliit/maliit-plugin-sdk-0.1.0.tar.gz Download] the Maliit Plugin SDK
* Extract the examples
# In your favorite terminal:
tar -xf maliit-plugin-sdk-*.tar.gz
cd maliit-plugin-sdk/examples/
* Compile them
qmake
make
make install
* Have a look around. In the examples directory you will find a QML based plugin and a C++ based plugin.
# QML plugin code
ls plugins/quick/
# C++ plugin code
ls plugins/standard
* Try out one of the examples
# First enable both of the example input methods, along with the meego keyboard
gconftool-2 -s /meegotouch/inputmethods/onscreen/enabled -t list --list-type strings \
[libmeego-keyboard.so,en_gb.xml,libmeego-keyboard-quick.so,,libhelloworldplugin.so,,libexampleplugin.so,ExamplePluginSubview1]
# To activate the QML example
gconftool-2 -s /meegotouch/inputmethods/onscreen/active -t list --list-type string [libhelloworldplugin.so,]
# To instead activate the C++ example
gconftool-2 -s /meegotouch/inputmethods/onscreen/active -t list --list-type string [libexampleplugin.so,ExamplePluginSubview1]

# To test, start the Maliit server and a application with a Maliit inputcontext loaded
# Note: More documentation on this can be found on the Installing page
meego-im-uiserver > server.log &
QT_IM_MODULE=MInputContext apps/plainqt/plainqt

# Tap/double tap on a text field to activate the input method
# You should now be able to see an input method which allows you to click to input "Hello World"

* Try changing the plugin code a bit, and reinstall and restart the Maliit server to try again.
# Do changes (start simple, maybe by changing the "Hello World" string to something else)

# Rebuild and reinstall plugins
make && make install
# Remember to restart the Maliit server for it to pick up the changed plugin

If you have any issues, first try to solve the problem by reading the instructions again, and maybe other documentation. If you cannot solve it, ask for help through one of our communication channels.

There are also several open source input plugins that one look at. See for instance
* [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/m-keyboard Meego Keyboard]
* [https://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard/trees/master/meego-keyboard-quick Meego Keyboard Quick]
* [https://github.com/foolegg/cute-input-method/tree/maliit cute-input-method]

== Feature documentation ==
See [[Maliit#Features]]

== API documentation ==
* [http://apidocs.meego.com/1.1/platform/html/meego-im-framework/main.html Old MeeGo 1.1 Input method engine and framework] - note that there has been changes in API since then
* Documentation webpage for the latest git version and Meego version has been requested. See [https://bugs.meego.com/show_bug.cgi?id=14382 bug 14382] and [https://bugs.meego.com/show_bug.cgi?id=14994 bug 14994]
* Generate from source code with doxygen.

Some of the documentation is slighly outdated, and we are working to improve this. Use our [[Maliit#Communication_Channels|communication channels]] if there are any issues.

== Technical documentation ==
* [[Media:Technical-overview-widget-reloc.pdf|Widget relocation in MTF]]
* More to come!

== Blogposts et.c. ==
(most recent first)
* Michael Hasselmannn: [http://taschenorakel.de/michael/2011/06/10/decent-examples-last/ Decent examples, at last!]
* Jon Nordby: [http://www.jonnor.com/2011/06/example-plugins-for-maliit-available/ Example plugins for Maliit]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/06/07/maliit-session-meego-spring-conference-2011/ Maliit Session at MeeGo Spring Conference 2011]
* Jan Arne Petersen: [http://blog.jpetersen.org/2011/05/29/maliit-packages-for-fedora/ Maliit packages for Fedora]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/05/12/writing-qml-based-input-methods-maliit/ Writing QML-based input methods for Maliit]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/05/10/painting-strategy-meegos-virtual-keyboard/ Painting Strategy in MeeGo's Virtual Keyboard]
* Jon Nordby: [http://www.jonnor.com/2011/04/introducing-maliit-on-screen-keyboard-in-gnome-3/ Introducing; Maliit on-screen keyboard in Gnome 3]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/04/10/customizing-meego-keyboard/ Customizing the Meego Keyboard]
* Michael Hasselmann: [http://taschenorakel.de/michael/2011/02/24/meego-input-methods-your-desktop/ MeeGo Input Methods for your desktop]

== Documentation working area ==
Here is the working area to keep track of the status of and work on the documentation.

* Goal: Every aspect of Maliit is well-documented, and the documentation easily accessible.
* Primary focus is on consumers of Maliit: Third-party developers and integrators

=== Important cases ===
* Developing a new input method plugin
* Developing a new engine plugin
* Integrating Maliit in a product
* Adding support for additional application toolkits

=== Documentation status ===

{|border="1" cellpadding="4" class="wikitable"
|-
! Item
! Status
! Description
|-
| wiki.meego.com/Maliit || 90% || Our public webpage/wiki page, starting point for all information about our project. In pretty good shape.
|-
| apidocs.meego.com/git-tip || 10% || Our docs should be shown here. [https://bugs.meego.com/show_bug.cgi?id=14382 Bug 14382]
|-
| apidocs.meego.com/1.2 || 10% || Our docs should be shown here. [https://bugs.meego.com/show_bug.cgi?id=14994 Bug 14994]
|-
| colspan=3 | '''Framework'''
|-
| Overall architecture || 30% || Some docs exists in framework source tree, but is very outdated
|-
| Input Method/framework settings system || 0% ||
|-
| Input Method Plugin<->Framework interaction || 0% || What the interaction concepts are (both user and technical), and what is done on each side to support this
|-
| Input Method Framework Window handling || 0% || Passthrough window, Self-compositing, plugin pixmap drawing, rotation animation. Maybe covered by above item?
|-
| Input Method Plugin API || 40% || Tutorial is outdated. Should provide a well-commented plugin example/skeleton that is built as part of our build (to avoid bitrot)
|-
| Input Context DBus API || 0% ||
|-
| Toolkit integration concepts || 20% || Key concepts like pre-edit injection, and widget relocation should be documented. Purpose: make it easy for others to improve toolkit integration, and to bring new people up to date. Widget relocation is documented.
|-
| Toolkit integration/support status || 10% || Implicitly all keyboard features/IM are available for MTF. No documentation about plain Qt, QML, Clutter or Gtk+
|-
| Engine interfaces || ? || Correction/prediction/suggestion/handwriting, both plugin side and IM side
|-
| Feedback framework || ? ||
|-
| colspan=3 | '''Meego Keyboard'''
|-
| Meego Keyboard theming (CSS) || 100% || Docs in keyboard source tree. ||
|-
| Meego Keyboard layouts || 100% || Docs in keyboard source tree. ||
|-
| Meego Keyboard features || 100% || Documented on wiki page. ||
|-
|}

{{MaliitNavigationBar}}

Maliit/Team

2011-06-10T08:22:47Z

Jonnor:

{{MaliitNavigationBar}}

== Team ==
* [http://meego.com/users/otso Otso Virtanen] (Product Manager)
* [http://meego.com/users/x2 Richard Sun] (Project Manager)
* [http://meego.com/users/mdamt Mohammad Anwari] (Architect)
* Aapo Kojo (ScrumMaster)
* Pekka Vuorela (Lead Developer)
* Kimmo Surakka (Lead Developer)
* [http://meego.com/users/mikhas Michael Hasselmann] (Developer)
* Viacheslav Sobolev (Developer)
* Ning Chi (Developer)
* Hannu Könönen (Test Developer)
* Rakesh Cherian (Test Developer, Bug Triager)
* [http://meego.com/users/brangi Gibran Rodriguez] (Test Engineer)
* [http://meego.com/users/jpetersen Jan Arne Petersen] (Developer)
* [http://meego.com/users/jonnor Jon Nordby] (Developer)
* Luis Araujo

== MeeGo Integration Team ==
* Luis Araujo (lead)
* Rakesh Cherian (Test Developer, Bug Triager)
* [http://meego.com/users/jonnor Jon Nordby] (Developer)

{{MaliitNavigationBar}}