MeeGo wiki - User contributions [en]

Maliit/Ideas/Supporting Non X11 Platforms

2011-06-17T15:47:10Z

Mdamt: /* Out-of-process */

At the moment, the X11 platform is the only platform supported by the Input Method. This page describes the approaches that can be taken to support non-x11 platforms. When we are talking about non-X11 platforms the following feature may be affected:
* Input method's process host
* Self-compositing
* Hardware keyboard mapping
* D-Bus API input context connection

The ideas in this page basically built on using Wayland as the display server.
https://meego.gitorious.org/~krh/meego-ux/krhs-meego-ux-daemon can be used as a reference.

== Process host ==
For the host of the input method, basically there are two approaches that can be done, depending on the requirements of the system that we want to support, and we want to support both approach and can be easily switch between those.

=== In-process ===
This approach will bring the input method in the same process as the application. The memory consumed by input method is shared with the application. It also affects the startup time of the application.

==== Implementation details ====
* Instantiate the MIMPluginManager inside an input context plugin
* Have a widget to show the plugin UI, replacing the MIMApplication passthrough window
* Some tricks needed so the widget does not steal the focus of the text entry widget (which would cause the input method plugin UI to be hidden).

This approach would be feasible for these use cases:
* QtCreator support: developing Qt application will automatically use MeeGo Input Method when text entry is activated
* Symbian support: overriding Symbian's default input method and use MeeGo Input Method instead in Qt applications (might not work in legacy Avkon applications)
* single process Lighthouse/Wayland: The startup time and memory consumption are no longer relevant here as there would be a single instance of input method in a single process Lighthouse scenario.

===== D-Bus connection =====
When used in-process, even though if the platform supports GLib D-Bus API, there is no point of having the connection using D-Bus API. Here the MInputContext may need to be modified to do direct call to the input method plugin.

=== Out-of-process ===
This approach will still need the presence of compositor or be part of the compositor.

==== Implementation details ====
The details here assume that QtQuick 2's QML based compositor would be implemented. In there, everything is a QSceneGraphItem and managed by the compositor. Furthermore, we can't use QtQuick 1.0 and nor the QGraphicsView based plugins inside this world.

===== First approach =====
This approach is to display input method as one of the client window of the compositor.

* Instantiate MIMPluginManager inside a Wayland compositor by using a normal QML plugin infrastructure. So here, the MIMPluginManager needs to be possible to be recompiled as a QDeclarativeExtensionPlugin. The MIMPluginManager then exposed to QML world as QSceneGraphItem as "InputMethod".
* In the compositor's main QML file, Maliit needs to be included, eg. something like:
<pre>
import QtQuick 2.0
import Maliit 1.0 // Import Maliit's plugin manager

...
InputMethod {
id: inputMethod
anchors {
fill: parent
}
}
...

</pre>
* The QML needs to be crafted so the InputMethod needs to be on top of everything which needs input method.
* MIMPluginManager would still need to be responsible to insert the plugin's UI into the scene by just reparenting the plugin's UI into the <tt>inputMethod</tt> object there.

===== Second approach =====
This approach is to display input method graphics into an item specified by the application. The application still need to include an item like this:

<pre>
import QtQuick 2.0
import Maliit 1.0 // Import Maliit's plugin manager

...
InputMethod {
id: inputMethod
anchors {
fill: parent
}
}
...

Then, the compositor need to be aware of this special item, and blit the graphics of the input method plugin into the area and handle the input events accordingly. This may need a quite an effort in the compositor side.

</pre>

Both approaches would be feasible for multiprocess Lighthouse applications setup. Modification to MImPluginManager is quite easy and minimal, removing the X11-tied classes out from the project files.

===== Input Context =====
The application may be easier to use a declarative version of MInputContext instead of using the normal QInputContext interface, as they are not QWidget nor QGraphicsView which is now heavily used in MInputContext.

== Hardware keyboard mapping ==
Internally Wayland is still using xkb, but having a dedicated interface to manage the hardware keyboard would make sense.

[[Category:Maliit]]

Maliit/Ideas/Supporting Non X11 Platforms

2011-06-17T15:36:25Z

Mdamt: /* Implementation details */

At the moment, the X11 platform is the only platform supported by the Input Method. This page describes the approaches that can be taken to support non-x11 platforms. When we are talking about non-X11 platforms the following feature may be affected:
* Input method's process host
* Self-compositing
* Hardware keyboard mapping
* D-Bus API input context connection

The ideas in this page basically built on using Wayland as the display server.
https://meego.gitorious.org/~krh/meego-ux/krhs-meego-ux-daemon can be used as a reference.

== Process host ==
For the host of the input method, basically there are two approaches that can be done, depending on the requirements of the system that we want to support, and we want to support both approach and can be easily switch between those.

=== In-process ===
This approach will bring the input method in the same process as the application. The memory consumed by input method is shared with the application. It also affects the startup time of the application.

==== Implementation details ====
* Instantiate the MIMPluginManager inside an input context plugin
* Have a widget to show the plugin UI, replacing the MIMApplication passthrough window
* Some tricks needed so the widget does not steal the focus of the text entry widget (which would cause the input method plugin UI to be hidden).

This approach would be feasible for these use cases:
* QtCreator support: developing Qt application will automatically use MeeGo Input Method when text entry is activated
* Symbian support: overriding Symbian's default input method and use MeeGo Input Method instead in Qt applications (might not work in legacy Avkon applications)
* single process Lighthouse/Wayland: The startup time and memory consumption are no longer relevant here as there would be a single instance of input method in a single process Lighthouse scenario.

===== D-Bus connection =====
When used in-process, even though if the platform supports GLib D-Bus API, there is no point of having the connection using D-Bus API. Here the MInputContext may need to be modified to do direct call to the input method plugin.

=== Out-of-process ===
This approach will still need the presence of compositor or be part of the compositor.

==== Implementation details ====
The details here assume that QtQuick 2's QML based compositor would be implemented. And here, we can't use QtQuick 1.0 and nor the QGraphicsView based plugins.

* Instantiate MIMPluginManager inside a Wayland compositor by using a normal QML plugin infrastructure. So here, the MIMPluginManager needs to be possible to be recompiled as a QDeclarativeExtensionPlugin. The MIMPluginManager then exposed to QML world as QSceneGraphItem as "InputMethod".
* In the compositor's main QML file, Maliit needs to be included, eg. something like:
<pre>
import QtQuick 2.0
import Maliit 1.0 // Import Maliit's plugin manager

...
InputMethod {
id: inputMethod
anchors {
fill: parent
}
}
...

</pre>
* The QML needs to be crafted so the InputMethod needs to be on top of everything which needs input method.
* MIMPluginManager would still need to be responsible to insert the plugin's UI into the scene by just reparenting the plugin's UI into the <tt>inputMethod</tt> object there.

This approach would be feasible for multiprocess Lighthouse applications setup.

== Hardware keyboard mapping ==
Internally Wayland is still using xkb, but having a dedicated interface to manage the hardware keyboard would make sense.

[[Category:Maliit]]

Maliit/Ideas/Supporting Non X11 Platforms

2011-06-17T15:36:08Z

Mdamt: /* Implementation details */

At the moment, the X11 platform is the only platform supported by the Input Method. This page describes the approaches that can be taken to support non-x11 platforms. When we are talking about non-X11 platforms the following feature may be affected:
* Input method's process host
* Self-compositing
* Hardware keyboard mapping
* D-Bus API input context connection

The ideas in this page basically built on using Wayland as the display server.
https://meego.gitorious.org/~krh/meego-ux/krhs-meego-ux-daemon can be used as a reference.

== Process host ==
For the host of the input method, basically there are two approaches that can be done, depending on the requirements of the system that we want to support, and we want to support both approach and can be easily switch between those.

=== In-process ===
This approach will bring the input method in the same process as the application. The memory consumed by input method is shared with the application. It also affects the startup time of the application.

==== Implementation details ====
* Instantiate the MIMPluginManager inside an input context plugin
* Have a widget to show the plugin UI, replacing the MIMApplication passthrough window
* Some tricks needed so the widget does not steal the focus of the text entry widget (which would cause the input method plugin UI to be hidden).

This approach would be feasible for these use cases:
* QtCreator support: developing Qt application will automatically use MeeGo Input Method when text entry is activated
* Symbian support: overriding Symbian's default input method and use MeeGo Input Method instead in Qt applications (might not work in legacy Avkon applications)
* single process Lighthouse/Wayland: The startup time and memory consumption are no longer relevant here as there would be a single instance of input method in a single process Lighthouse scenario.

===== D-Bus connection =====
When used in-process, even though if the platform supports GLib D-Bus API, there is no point of having the connection using D-Bus API. Here the MInputContext may need to be modified to do direct call to the input method plugin.

=== Out-of-process ===
This approach will still need the presence of compositor or be part of the compositor.

==== Implementation details ====
The details here assume that QtQuick 2's QML based compositor would be implemented. And here, we can't use QtQuick 1.0 and possibly also the QGraphicsView based plugins.

* Instantiate MIMPluginManager inside a Wayland compositor by using a normal QML plugin infrastructure. So here, the MIMPluginManager needs to be possible to be recompiled as a QDeclarativeExtensionPlugin. The MIMPluginManager then exposed to QML world as QSceneGraphItem as "InputMethod".
* In the compositor's main QML file, Maliit needs to be included, eg. something like:
<pre>
import QtQuick 2.0
import Maliit 1.0 // Import Maliit's plugin manager

...
InputMethod {
id: inputMethod
anchors {
fill: parent
}
}
...

</pre>
* The QML needs to be crafted so the InputMethod needs to be on top of everything which needs input method.
* MIMPluginManager would still need to be responsible to insert the plugin's UI into the scene by just reparenting the plugin's UI into the <tt>inputMethod</tt> object there.

This approach would be feasible for multiprocess Lighthouse applications setup.

== Hardware keyboard mapping ==
Internally Wayland is still using xkb, but having a dedicated interface to manage the hardware keyboard would make sense.

[[Category:Maliit]]

Maliit/Ideas/Supporting Non X11 Platforms

2011-06-16T23:21:06Z

Mdamt: /* Implementation details */

At the moment, the X11 platform is the only platform supported by the Input Method. This page describes the approaches that can be taken to support non-x11 platforms. When we are talking about non-X11 platforms the following feature may be affected:
* Input method's process host
* Self-compositing
* Hardware keyboard mapping
* D-Bus API input context connection

The ideas in this page basically built on using Wayland as the display server.

== Process host ==
For the host of the input method, basically there are two approaches that can be done, depending on the requirements of the system that we want to support, and we want to support both approach and can be easily switch between those.

=== In-process ===
This approach will bring the input method in the same process as the application. The memory consumed by input method is shared with the application. It also affects the startup time of the application.

==== Implementation details ====
* Instantiate the MIMPluginManager inside an input context plugin
* Have a widget to show the plugin UI, replacing the MIMApplication passthrough window
* Some tricks needed so the widget does not steal the focus of the text entry widget (which would cause the input method plugin UI to be hidden).

This approach would be feasible for these use cases:
* QtCreator support: developing Qt application will automatically use MeeGo Input Method when text entry is activated
* Symbian support: overriding Symbian's default input method and use MeeGo Input Method instead in Qt applications (might not work in legacy Avkon applications)
* single process Lighthouse/Wayland: The startup time and memory consumption are no longer relevant here as there would be a single instance of input method in a single process Lighthouse scenario.

===== D-Bus connection =====
When used in-process, even though if the platform supports GLib D-Bus API, there is no point of having the connection using D-Bus API. Here the MInputContext may need to be modified to do direct call to the input method plugin.

=== Out-of-process ===
This approach will still need the presence of compositor or be part of the compositor.

==== Implementation details ====
The details here assume that QtQuick 2's QML based compositor would be implemented. And here, we can't use QtQuick 1.0 and possibly also the QGraphicsView based plugins.

* Instantiate MIMPluginManager inside a Wayland compositor by using a normal QML plugin infrastructure. So here, the MIMPluginManager needs to be possible to be recompiled as a QDeclarativeExtensionPlugin.
* In the compositor's main QML file, Maliit needs to be included, eg. something like:
<pre>
import QtQuick 2.0
import Maliit // Import Maliit's plugin manager

...
InputMethod {
id: inputMethod
anchors {
fill: parent
}
}
...

</pre>
* The QML needs to be crafted so the InputMethod needs to be on top of everything which needs input method.
* MIMPluginManager would still need to be responsible to insert the plugin's UI into the scene by just reparenting the plugin's UI into the <tt>inputMethod</tt> object there.

This approach would be feasible for multiprocess Lighthouse applications setup.

== Hardware keyboard mapping ==
Internally Wayland is still using xkb, but having a dedicated interface to manage the hardware keyboard would make sense.

[[Category:Maliit]]

Maliit/Ideas/Supporting Non X11 Platforms

2011-06-16T23:20:29Z

Mdamt: /* Implementation details */

At the moment, the X11 platform is the only platform supported by the Input Method. This page describes the approaches that can be taken to support non-x11 platforms. When we are talking about non-X11 platforms the following feature may be affected:
* Input method's process host
* Self-compositing
* Hardware keyboard mapping
* D-Bus API input context connection

The ideas in this page basically built on using Wayland as the display server.

== Process host ==
For the host of the input method, basically there are two approaches that can be done, depending on the requirements of the system that we want to support, and we want to support both approach and can be easily switch between those.

=== In-process ===
This approach will bring the input method in the same process as the application. The memory consumed by input method is shared with the application. It also affects the startup time of the application.

==== Implementation details ====
* Instantiate the MIMPluginManager inside an input context plugin
* Have a widget to show the plugin UI, replacing the MIMApplication passthrough window
* Some tricks needed so the widget does not steal the focus of the text entry widget (which would cause the input method plugin UI to be hidden).

This approach would be feasible for these use cases:
* QtCreator support: developing Qt application will automatically use MeeGo Input Method when text entry is activated
* Symbian support: overriding Symbian's default input method and use MeeGo Input Method instead in Qt applications (might not work in legacy Avkon applications)
* single process Lighthouse/Wayland: The startup time and memory consumption are no longer relevant here as there would be a single instance of input method in a single process Lighthouse scenario.

===== D-Bus connection =====
When used in-process, even though if the platform supports GLib D-Bus API, there is no point of having the connection using D-Bus API. Here the MInputContext may need to be modified to do direct call to the input method plugin.

=== Out-of-process ===
This approach will still need the presence of compositor or be part of the compositor.

==== Implementation details ====
The details here assume that QtQuick 2's QML based compositor would be implemented. And here, we can't use QtQuick 1.0 and possibly also the QGraphicsView based plugins.

* Instantiate MIMPluginManager inside a Wayland compositor by using a normal QML plugin infrastructure. So here, the MIMPluginManager needs to be possible to be recompiled as a QDeclarativeExtensionPlugin.
* In the compositor's main QML file, Maliit needs to be included, eg. something like:
<code>
import QtQuick 2.0
import Maliit // Import Maliit's plugin manager

...
InputMethod {
id: inputMethod
anchors {
fill: parent
}
}
...

</code>
* The QML needs to be crafted so the InputMethod needs to be on top of everything which needs input method.
* MIMPluginManager would still need to be responsible to insert the plugin's UI into the scene by just reparenting the plugin's UI into the <tt>inputMethod</tt> object there.

This approach would be feasible for multiprocess Lighthouse applications setup.

== Hardware keyboard mapping ==
Internally Wayland is still using xkb, but having a dedicated interface to manage the hardware keyboard would make sense.

[[Category:Maliit]]

Maliit/Roadmap

2011-04-21T10:09:10Z

Mdamt: /* MeeGo Keyboard */

{{MaliitNavigationBar}}

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

== MeeGo 1.3 ==
=== Framework ===
* use D-Bus datatype instead of serialized Qt types in D-Bus API
* [[Maliit/Ideas/Supporting_Non_X11_Platforms|support for non X11 platform]]
* support for Qt applications not linked to MeeGo Touch
** orientation change

=== MeeGo Keyboard ===
* key magnification and accent pop-ups
* new word prediction widgets: Word Ribbon
* extended support for CJK languages
* libmeegotouch removal (or perhaps develop the qml keyboard further?)

== MeeGo 1.2 ==
=== 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-04-21T07:02:16Z

Mdamt: /* MeeGo Keyboard */

{{MaliitNavigationBar}}

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

== MeeGo 1.3 ==
=== Framework ===
* use D-Bus datatype instead of serialized Qt types in D-Bus API
* [[Maliit/Ideas/Supporting_Non_X11_Platforms|support for non X11 platform]]
* support for Qt applications not linked to MeeGo Touch
** orientation change

=== MeeGo Keyboard ===
* key magnification and accent pop-ups
* extended support for CJK languages
* libmeegotouch removal (or perhaps develop the qml keyboard further?)

== MeeGo 1.2 ==
=== 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-04-20T10:31:44Z

Mdamt: /* Framework */

{{MaliitNavigationBar}}

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

== MeeGo 1.3 ==
=== Framework ===
* use D-Bus datatype instead of serialized Qt types in D-Bus API
* [[Maliit/Ideas/Supporting_Non_X11_Platforms|support for non X11 platform]]
* support for Qt applications not linked to MeeGo Touch
** orientation change

=== MeeGo Keyboard ===
* key magnification and accent pop-ups
* extended support for CJK languages
* libmeegotouch removal

== MeeGo 1.2 ==
=== 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/Ideas/Supporting Non X11 Platforms

2011-04-20T10:29:37Z

Mdamt: Created page with "= Supporting Non-X11 Platforms = At the moment, the X11 platform is the only platform supported by the Input Method. This page describes the approaches that can be taken to suppo..."

= Supporting Non-X11 Platforms =
At the moment, the X11 platform is the only platform supported by the Input Method. This page describes the approaches that can be taken to support non-x11 platforms. When we are talking about non-X11 platforms the following feature may be affected:
* Input method's process host
* Self-compositing
* Hardware keyboard mapping
* D-Bus API input context connection

The ideas in this page basically built on using Wayland as the display server.

== Process host ==
For the host of the input method, basically there are two approaches that can be done, depending on the requirements of the system that we want to support, and we want to support both approach and can be easily switch between those.

=== In-process ===
This approach will bring the input method in the same process as the application. The memory consumed by input method is shared with the application. It also affects the startup time of the application.

==== Implementation details ====
* Instantiate the MIMPluginManager inside an input context plugin
* Have a widget to show the plugin UI, replacing the MIMApplication passthrough window
* Some tricks needed so the widget does not steal the focus of the text entry widget (which would cause the input method plugin UI to be hidden).

This approach would be feasible for these use cases:
* QtCreator support: developing Qt application will automatically use MeeGo Input Method when text entry is activated
* Symbian support: overriding Symbian's default input method and use MeeGo Input Method instead in Qt applications (might not work in legacy Avkon applications)
* single process Lighthouse/Wayland: The startup time and memory consumption are no longer relevant here as there would be a single instance of input method in a single process Lighthouse scenario.

===== D-Bus connection =====
When used in-process, even though if the platform supports GLib D-Bus API, there is no point of having the connection using D-Bus API. Here the MInputContext may need to be modified to do direct call to the input method plugin.

=== Out-of-process ===
This approach will still need the presence of compositor or be part of the compositor.

==== Implementation details ====
* Instantiate MIMPluginManager inside a Wayland compositor, preferably a QML based compositor.
* Have an option to use a QML element as the UI host of the plugin so total solution would be QML based widgets.

This approach would be feasible for multiprocess Lighthouse applications setup.

== Hardware keyboard mapping ==
Internally Wayland is still using xkb, but having a dedicated interface to manage the hardware keyboard would make sense.

Maliit

2011-04-15T07:39:16Z

Mdamt: /* News */

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

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

Maliit provides a flexible and cross graphical user interface toolkit input method framework. It is usable on all MeeGo user experiences, and in other GNU/Linux distributions as well.

== 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 ==
* 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 ==
* May 23-25th - Meego Conference San Fransisco. Proposed sessions: [http://sf2011.meego.com/program/sessions/introduction-meego-text-input Introduction], [http://sf2011.meego.com/program/sessions/developing-custom-input-methods-meego Developing input method plugins], [http://sf2011.meego.com/program/sessions/better-interaction-after-application-meets-software-input-method Input method and application interaction]
* August 6th-12th - Desktop Summit Berlin. Proposed session: [https://www.desktopsummit.org/sessions/meego-input-methods-not-just-meego Meego Input Methods - not just for Meego] (currently not published)

== Goals ==

The overall goal of Maliit is to be ''the'' input method project for MeeGo and other GNU/Linux-based embedded/mobile platforms. To achieve this we aim to:

'''Provide a solid input method framework'''

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

'''Provide a core set of input methods'''

The default set of input methods should demonstrate the core capabilites of the framework, and provide a good user experience that device manufacturers and integrators can use with little to no adaptation.

'''Empower third-party developers'''

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

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

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

[[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
* Support for other toolkits can be done by using the DBus connection for the Input Context

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

<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)
[[File:TransparentPlaceholder.png|link=http://wikipedia.org|caption]]
</gallery>

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

== Developers ==

See [[Maliit/ForDevelopers]]

== Technical Documentation ==

* [[Media:Technical-overview-widget-reloc.pdf|Widget relocation in MTF]]

== 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)
* [http://meego.com/users/jonnor Jon Nordby] (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)

Maliit

2011-04-15T07:38:11Z

Mdamt: /* News */

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

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

Maliit provides a flexible and cross graphical user interface toolkit input method framework. It is usable on all MeeGo user experiences, and in other GNU/Linux distributions as well.

== 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 ==
* 08.04.2011 - MeeGo Keyboard is relicensed with BSD license: [[http://lists.meego.com/pipermail/meego-dev/2011-April/482578.html Read the announcement here]]
* 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 ==
* May 23-25th - Meego Conference San Fransisco. Proposed sessions: [http://sf2011.meego.com/program/sessions/introduction-meego-text-input Introduction], [http://sf2011.meego.com/program/sessions/developing-custom-input-methods-meego Developing input method plugins], [http://sf2011.meego.com/program/sessions/better-interaction-after-application-meets-software-input-method Input method and application interaction]
* August 6th-12th - Desktop Summit Berlin. Proposed session: [https://www.desktopsummit.org/sessions/meego-input-methods-not-just-meego Meego Input Methods - not just for Meego] (currently not published)

== Goals ==

The overall goal of Maliit is to be ''the'' input method project for MeeGo and other GNU/Linux-based embedded/mobile platforms. To achieve this we aim to:

'''Provide a solid input method framework'''

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

'''Provide a core set of input methods'''

The default set of input methods should demonstrate the core capabilites of the framework, and provide a good user experience that device manufacturers and integrators can use with little to no adaptation.

'''Empower third-party developers'''

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

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

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

[[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
* Support for other toolkits can be done by using the DBus connection for the Input Context

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

<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)
[[File:TransparentPlaceholder.png|link=http://wikipedia.org|caption]]
</gallery>

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

== Developers ==

See [[Maliit/ForDevelopers]]

== Technical Documentation ==

* [[Media:Technical-overview-widget-reloc.pdf|Widget relocation in MTF]]

== 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)
* [http://meego.com/users/jonnor Jon Nordby] (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)

Maliit/Roadmap

2011-04-15T07:36:18Z

Mdamt:

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

= MeeGo 1.3 =
== Framework ==
* use D-Bus datatype instead of serialized Qt types in D-Bus API
* support for non X11 platform
* support for Qt applications not linked to MeeGo Touch
** orientation change

== MeeGo Keyboard ==
* key magnification and accent pop-ups
* extended support for CJK languages
* libmeegotouch removal

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

Maliit/Roadmap

2011-04-15T07:34:07Z

Mdamt: /* Unmapped */

= MeeGo 1.3 =
== Framework ==
* use D-Bus datatype instead of serialized Qt types in D-Bus API
* support for non X11 platform
* support for Qt applications not linked to MeeGo Touch
** orientation change

== MeeGo Keyboard ==
* key magnification and accent pop-ups
* extended support for CJK languages
* libmeegotouch removal

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

Maliit/Roadmap

2011-04-15T07:33:40Z

Mdamt: /* Framework */

= Unmapped =
== Framework ==
== MeeGo Keyboard ==
== MeeGo Keyboard ==

= MeeGo 1.3 =
== Framework ==
* use D-Bus datatype instead of serialized Qt types in D-Bus API
* support for non X11 platform
* support for Qt applications not linked to MeeGo Touch
** orientation change

== MeeGo Keyboard ==
* key magnification and accent pop-ups
* extended support for CJK languages
* libmeegotouch removal

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

Maliit/Roadmap

2011-04-15T07:33:27Z

Mdamt: /* Framework */

= Unmapped =
== Framework ==
== MeeGo Keyboard ==
== MeeGo Keyboard ==

= MeeGo 1.3 =
== Framework ==
* use D-Bus datatype instead of serialized Qt types in D-Bus API
* support for non X11 platform
* support for Qt applications not linked to MeeGo Touch
* orientation change

== MeeGo Keyboard ==
* key magnification and accent pop-ups
* extended support for CJK languages
* libmeegotouch removal

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

Maliit/Roadmap

2011-04-15T07:32:26Z

Mdamt: Created page with "= Unmapped = == Framework == == MeeGo Keyboard == == MeeGo Keyboard == = MeeGo 1.3 = == Framework == * use D-Bus datatype instead of serialized Qt types in D-Bus API * support f..."

= Unmapped =
== Framework ==
== MeeGo Keyboard ==
== MeeGo Keyboard ==

= MeeGo 1.3 =
== Framework ==
* use D-Bus datatype instead of serialized Qt types in D-Bus API
* support for non X11 platform
* support for Qt applications not linked to MeeGo Touch
* orientation change

== MeeGo Keyboard ==
* key magnification and accent pop-ups
* extended support for CJK languages
* libmeegotouch removal

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

Maliit

2011-04-08T14:30:56Z

Mdamt: /* News */

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

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

Maliit provides a flexible and cross graphical user interface toolkit input method framework. It is usable on all MeeGo user experiences, and in other GNU/Linux distributions as well.

== 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 ==
* 08.04.2011 - MeeGo Keyboard is relicensed with BSD license: [[http://lists.meego.com/pipermail/meego-dev/2011-April/482578.html Read the announcement here]]
* 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]

== Upcoming events ==
* May 23-25th - Meego Conference San Fransisco. Proposed sessions: [http://sf2011.meego.com/program/sessions/introduction-meego-text-input Introduction], [http://sf2011.meego.com/program/sessions/developing-custom-input-methods-meego Developing input method plugins], [http://sf2011.meego.com/program/sessions/better-interaction-after-application-meets-software-input-method Input method and application interaction]
* August 6th-12th - Desktop Summit Berlin. Proposed session: [https://www.desktopsummit.org/sessions/meego-input-methods-not-just-meego Meego Input Methods - not just for Meego] (currently not published)

== Goals ==

The overall goal of Maliit is to be ''the'' input method project for MeeGo and other GNU/Linux-based embedded/mobile platforms. To achieve this we aim to:

'''Provide a solid input method framework'''

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

'''Provide a core set of input methods'''

The default set of input methods should demonstrate the core capabilites of the framework, and provide a good user experience that device manufacturers and integrators can use with little to no adaptation.

'''Empower third-party developers'''

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

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

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

[[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
* Support for other toolkits can be done by using the DBus connection for the Input Context

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

<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)
[[File:TransparentPlaceholder.png|link=http://wikipedia.org|caption]]
</gallery>

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

== Developers ==

See [[Maliit/ForDevelopers]]

== Technical Documentation ==

* [[Media:Technical-overview-widget-reloc.pdf|Widget relocation in MTF]]

== 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)
* [http://meego.com/users/jonnor Jon Nordby] (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)

GSoC 2011/Ideas

2011-03-18T05:14:30Z

Mdamt: /* Medium */

'''Add your project ideas to the table below.'''

'''If you are a mentor or want to be come one of the possible projects, add your name to the table with your meego.com username'''.

Everybody can add ideas to the list, there's no need to be a mentor or a student. Don't try to guess if your idea will ever be used in MeeGo or not, just add it to the list. We will try to avoid duplicated work.

This list is not exclusive. If you are a student and have an idea that is not listed here, don't hesitate to apply with your own idea. Note that it is good practice to ask opinions about it in the MeeGo community, though!

Also consider the [https://bugs.meego.com/buglist.cgi?query_format=advanced&short_desc=%5BFEA%5D&bug_status=NEW&short_desc_type=allwordssubstr current list of pending feature requests] in Bugzilla.

== Ideas list ==

{| class="wikitable"
| style="background:LightGreen" | Final proposal
| style="background:Orange" | Study of alternatives needed
| style="background:Tomato" | Draft proposal
|}

=== Easy ===

{| class="wikitable"
|- style="background-color: #eef"
! Title !! Abstract/Description !! Skills !! Reporter !! Possible Mentor(s) !! Comments
|-style="background:LightGreen"
| ''The best thing ever'' || This is a sample idea I used to build this table. Ideally, the project abstract should be around this long, explaining what the idea is about. Remember to give some headroom in order for potential students to apply their own spin to it. || having good ideas || [http://meego.com/users/javispedro javispedro] || [http://meego.com/users/javispedro javispedro] || Please use this row as template!
|-style="background:Tomato"
| ''Filmaster.com client'' || The [http://filmaster.com/ Filmaster.com] "Film buffs community" could use a nice mobile client for MeeGo. They're already working on iPhone / Android apps, MeeGo should have one, too! || Qt / QML? || [http://meego.com/users/Saviq Saviq] || ||
|-style="background:Tomato"
| ''orkut.com client'' || orkut.com is the most popular Social Network in Brazil, we can create a client for MeeGo to interact on this network. || Qt / QML opensocial api || [http://meego.com/users/barroca barroca] || [http://meego.com/users/barroca barroca] || Maybe Using intel SDK for MeeGo
|-style="background:Tomato"
| ''google latitude client'' || Update location information using Google Latitude and display friends Latitude information. || Qt / QML latitude api || [http://meego.com/users/barroca barroca] || [http://meego.com/users/barroca barroca] ||
|-style="background:Tomato"
| ''Bluetooth keyboard input method support'' || Disable on-screen virtual keyboard when a bluetooth keyboard is connected and activates it again when the bluetooth keyboard is disconnected. || Bluetooth api, MeeGo Input Methods || [http://meego.com/users/mdamt mdamt] || [http://meego.com/users/mdamt mdamt] ||
|}

=== Medium ===
{| class="wikitable"
|- style="background-color: #eef"
! Title !! Abstract/Description !! Skills !! Reporter !! Possible Mentor(s) !! Comments
|-style="background:LightGreen"
| ''The best thing ever'' || This is a sample idea I used to build this table. Ideally, the project abstract should be around this long, explaining what the idea is about. Remember to give some headroom in order for potential students to apply their own spin to it. || having good ideas || [http://meego.com/users/javispedro javispedro] || [http://meego.com/users/javispedro javispedro] || Please use this row as template!

|-style="background:Tomato"
| ''hardware monitor'' || Hardware Monitor for MeeGo developed using the SDK || Qt / QML || [http://meego.com/users/barroca barroca] || [http://meego.com/users/barroca barroca] ||
|-style="background:Tomato"
| ''voice dictation'' || Voice dictation using MeeGo Input Methods framework || MeeGo Input Methods API, Voice input engine || [http://meego.com/users/mdamt mdamt] || [http://meego.com/users/mdamt mdamt] ||
|-style="background:Tomato"
| ''Predicition text input engine'' || Prediction text input engine using MeeGo Input Methods Engine framework || MeeGo Input Methods Engine API, Prediction engine API || [http://meego.com/users/mdamt mdamt] || [http://meego.com/users/mdamt mdamt] ||
|}

=== Hard ===
{| class="wikitable"
|- style="background-color: #eef"
! Title !! Abstract/Description !! Skills !! Reporter !! Possible Mentor(s) !! Comments
|-style="background:LightGreen"
| ''The best thing ever'' || This is a sample idea I used to build this table. Ideally, the project abstract should be around this long, explaining what the idea is about. Remember to give some headroom in order for potential students to apply their own spin to it. || having good ideas || [http://meego.com/users/javispedro javispedro] || [http://meego.com/users/javispedro javispedro] || Please use this row as template!

|-style="background:Tomato"
| ''picture viewer editor'' || Picture viewer and editor that supports multi-touch gestures written on QML or using SDK. || Qt / QML MeeGo SDK || [http://meego.com/users/barroca barroca] || ||

|-style="background:Tomato"
| ''MeeGo on Mac'' || Install MeeGo on Mac and fix issues. || || [http://meego.com/users/barroca barroca] || ||

|-style="background:Tomato"
| ''MeeGo Input Methods on QtCreator'' || Run MeeGo Input Methods inside applications run by QtCreator, it should work on platforms supported by Qt Creator || QInputContext, platform specific IPC, Qt || [http://meego.com/users/mdamt mdamt] || [http://meego.com/users/mdamt mdamt] ||

|}

GSoC 2011/Ideas

2011-03-18T05:11:17Z

Mdamt: /* Easy */

'''Add your project ideas to the table below.'''

'''If you are a mentor or want to be come one of the possible projects, add your name to the table with your meego.com username'''.

Everybody can add ideas to the list, there's no need to be a mentor or a student. Don't try to guess if your idea will ever be used in MeeGo or not, just add it to the list. We will try to avoid duplicated work.

This list is not exclusive. If you are a student and have an idea that is not listed here, don't hesitate to apply with your own idea. Note that it is good practice to ask opinions about it in the MeeGo community, though!

Also consider the [https://bugs.meego.com/buglist.cgi?query_format=advanced&short_desc=%5BFEA%5D&bug_status=NEW&short_desc_type=allwordssubstr current list of pending feature requests] in Bugzilla.

== Ideas list ==

{| class="wikitable"
| style="background:LightGreen" | Final proposal
| style="background:Orange" | Study of alternatives needed
| style="background:Tomato" | Draft proposal
|}

=== Easy ===

{| class="wikitable"
|- style="background-color: #eef"
! Title !! Abstract/Description !! Skills !! Reporter !! Possible Mentor(s) !! Comments
|-style="background:LightGreen"
| ''The best thing ever'' || This is a sample idea I used to build this table. Ideally, the project abstract should be around this long, explaining what the idea is about. Remember to give some headroom in order for potential students to apply their own spin to it. || having good ideas || [http://meego.com/users/javispedro javispedro] || [http://meego.com/users/javispedro javispedro] || Please use this row as template!
|-style="background:Tomato"
| ''Filmaster.com client'' || The [http://filmaster.com/ Filmaster.com] "Film buffs community" could use a nice mobile client for MeeGo. They're already working on iPhone / Android apps, MeeGo should have one, too! || Qt / QML? || [http://meego.com/users/Saviq Saviq] || ||
|-style="background:Tomato"
| ''orkut.com client'' || orkut.com is the most popular Social Network in Brazil, we can create a client for MeeGo to interact on this network. || Qt / QML opensocial api || [http://meego.com/users/barroca barroca] || [http://meego.com/users/barroca barroca] || Maybe Using intel SDK for MeeGo
|-style="background:Tomato"
| ''google latitude client'' || Update location information using Google Latitude and display friends Latitude information. || Qt / QML latitude api || [http://meego.com/users/barroca barroca] || [http://meego.com/users/barroca barroca] ||
|-style="background:Tomato"
| ''Bluetooth keyboard input method support'' || Disable on-screen virtual keyboard when a bluetooth keyboard is connected and activates it again when the bluetooth keyboard is disconnected. || Bluetooth api, MeeGo Input Methods || [http://meego.com/users/mdamt mdamt] || [http://meego.com/users/mdamt mdamt] ||
|}

=== Medium ===
{| class="wikitable"
|- style="background-color: #eef"
! Title !! Abstract/Description !! Skills !! Reporter !! Possible Mentor(s) !! Comments
|-style="background:LightGreen"
| ''The best thing ever'' || This is a sample idea I used to build this table. Ideally, the project abstract should be around this long, explaining what the idea is about. Remember to give some headroom in order for potential students to apply their own spin to it. || having good ideas || [http://meego.com/users/javispedro javispedro] || [http://meego.com/users/javispedro javispedro] || Please use this row as template!

|-style="background:Tomato"
| ''hardware monitor'' || Hardware Monitor for MeeGo developed using the SDK || Qt / QML || [http://meego.com/users/barroca barroca] || [http://meego.com/users/barroca barroca] ||
|}

=== Hard ===
{| class="wikitable"
|- style="background-color: #eef"
! Title !! Abstract/Description !! Skills !! Reporter !! Possible Mentor(s) !! Comments
|-style="background:LightGreen"
| ''The best thing ever'' || This is a sample idea I used to build this table. Ideally, the project abstract should be around this long, explaining what the idea is about. Remember to give some headroom in order for potential students to apply their own spin to it. || having good ideas || [http://meego.com/users/javispedro javispedro] || [http://meego.com/users/javispedro javispedro] || Please use this row as template!

|-style="background:Tomato"
| ''picture viewer editor'' || Picture viewer and editor that supports multi-touch gestures written on QML or using SDK. || Qt / QML MeeGo SDK || [http://meego.com/users/barroca barroca] || ||

|-style="background:Tomato"
| ''MeeGo on Mac'' || Install MeeGo on Mac and fix issues. || || [http://meego.com/users/barroca barroca] || ||

|-style="background:Tomato"
| ''MeeGo Input Methods on QtCreator'' || Run MeeGo Input Methods inside applications run by QtCreator, it should work on platforms supported by Qt Creator || QInputContext, platform specific IPC, Qt || [http://meego.com/users/mdamt mdamt] || [http://meego.com/users/mdamt mdamt] ||

|}

GSoC 2011/Ideas

2011-03-16T20:40:09Z

Mdamt: /* Hard */

'''Add your project ideas to the table below.'''

'''If you are a mentor or want to be come one of the possible projects, add your name to the table with your meego.com username'''.

Everybody can add ideas to the list, there's no need to be a mentor or a student. Don't try to guess if your idea will ever be used in MeeGo or not, just add it to the list. We will try to avoid duplicated work.

This list is not exclusive. If you are a student and have an idea that is not listed here, don't hesitate to apply with your own idea. Note that it is good practice to ask opinions about it in the MeeGo community, though!

Also consider the [https://bugs.meego.com/buglist.cgi?query_format=advanced&short_desc=%5BFEA%5D&bug_status=NEW&short_desc_type=allwordssubstr current list of pending feature requests] in Bugzilla.

== Ideas list ==

{| class="wikitable"
| style="background:LightGreen" | Final proposal
| style="background:Orange" | Study of alternatives needed
| style="background:Tomato" | Draft proposal
|}

=== Easy ===

{| class="wikitable"
|- style="background-color: #eef"
! Title !! Abstract/Description !! Skills !! Reporter !! Possible Mentor(s) !! Comments
|-style="background:LightGreen"
| ''The best thing ever'' || This is a sample idea I used to build this table. Ideally, the project abstract should be around this long, explaining what the idea is about. Remember to give some headroom in order for potential students to apply their own spin to it. || having good ideas || [http://meego.com/users/javispedro javispedro] || [http://meego.com/users/javispedro javispedro] || Please use this row as template!
|-style="background:Tomato"
| ''Filmaster.com client'' || The [http://filmaster.com/ Filmaster.com] "Film buffs community" could use a nice mobile client for MeeGo. They're already working on iPhone / Android apps, MeeGo should have one, too! || Qt / QML? || [http://meego.com/users/Saviq Saviq] || ||
|-style="background:Tomato"
| ''orkut.com client'' || orkut.com is the most popular Social Network in Brazil, we can create a client for MeeGo to interact on this network. || Qt / QML opensocial api || [http://meego.com/users/barroca barroca] || [http://meego.com/users/barroca barroca] || Maybe Using intel SDK for MeeGo
|-style="background:Tomato"
| ''google latitude client'' || Update location information using Google Latitude and display friends Latitude information. || Qt / QML latitude api || [http://meego.com/users/barroca barroca] || [http://meego.com/users/barroca barroca] ||
|}

=== Medium ===
{| class="wikitable"
|- style="background-color: #eef"
! Title !! Abstract/Description !! Skills !! Reporter !! Possible Mentor(s) !! Comments
|-style="background:LightGreen"
| ''The best thing ever'' || This is a sample idea I used to build this table. Ideally, the project abstract should be around this long, explaining what the idea is about. Remember to give some headroom in order for potential students to apply their own spin to it. || having good ideas || [http://meego.com/users/javispedro javispedro] || [http://meego.com/users/javispedro javispedro] || Please use this row as template!

|-style="background:Tomato"
| ''hardware monitor'' || Hardware Monitor for MeeGo developed using the SDK || Qt / QML || [http://meego.com/users/barroca barroca] || [http://meego.com/users/barroca barroca] ||
|}

=== Hard ===
{| class="wikitable"
|- style="background-color: #eef"
! Title !! Abstract/Description !! Skills !! Reporter !! Possible Mentor(s) !! Comments
|-style="background:LightGreen"
| ''The best thing ever'' || This is a sample idea I used to build this table. Ideally, the project abstract should be around this long, explaining what the idea is about. Remember to give some headroom in order for potential students to apply their own spin to it. || having good ideas || [http://meego.com/users/javispedro javispedro] || [http://meego.com/users/javispedro javispedro] || Please use this row as template!

|-style="background:Tomato"
| ''picture viewer editor'' || Picture viewer and editor that supports multi-touch gestures written on QML or using SDK. || Qt / QML MeeGo SDK || [http://meego.com/users/barroca barroca] || ||

|-style="background:Tomato"
| ''MeeGo on Mac'' || Install MeeGo on Mac and fix issues. || || [http://meego.com/users/barroca barroca] || ||

|-style="background:Tomato"
| ''MeeGo Input Methods on QtCreator'' || Run MeeGo Input Methods inside applications run by QtCreator, it should work on platforms supported by Qt Creator || QInputContext, platform specific IPC, Qt || [http://meego.com/users/mdamt mdamt] || [http://meego.com/users/mdamt mdamt] ||

|}

Maliit

2011-03-02T09:28:10Z

Mdamt: /* Team */

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

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

= About Maliit - the MeeGo Input Methods project =

Maliit provides a flexible and cross graphical user interface toolkit input method framework. It is usable on all MeeGo user experiences.

= Features =

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

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

* 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

= Maliit in action =

* [http://www.linpus.com/products_meego_slate.html Linpus Slate] ([http://www.linpus.com/images/slate/kb.png screenshot showing Linpus virtual keyboard])
* [http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 Intel MeeGo tablet] with Swype keyboard
* [http://wiki.meego.com/Input_Method_Framework/MeeGo_1.1#Netbook Installed on MeeGo 1.1 Netbook release] with MeeGo own keyboard

[[File:Lenovo_meego_vkb.jpg|400px|MeeGo 1.1. Netbook on Lenovo S10-3T Ideapad with Maliit virtual keyboard installed.]]

* [http://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo 1.1 Handset] on Aava Mobile with MeeGo own keyboard

[[File:Meego1.1_handset_on_aava.jpg|200px|MeeGo 1.1 Handset on Aava Mobile with with MeeGo own keyboard]]

= Developers =
== Packages for Ubuntu (10.04 Lucid Lynx / 10.10 Maveric Meerkat) ==
The MeeGo Input Methods are not 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

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

== Repositories ==
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework meego-im-framework]:
git clone git@gitorious.org:meegotouch/meegotouch-inputmethodframework.git
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodengine meego-im-engine]:
git clone git@gitorious.org:meegotouch/meegotouch-inputmethodengine.git
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard meego-keyboard]:
git clone git@gitorious.org:meegotouch/meegotouch-inputmethodkeyboard.git

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

= Communication channels =
== Mailing list ==
* ([https://bugs.meego.com/show_bug.cgi?id=13696 request pending])

== Bug reports and feature requests ==
* Please use [https://bugs.meego.com/enter_bug.cgi?product=OS%20Base&component=Virtual%20keyboard bugs.meego.com] for bug reports and feature requests. New ideas should first be discussed on the mailing list.

== IRC ==
Visit us in #meego-inputmethods at freenode.net

= Team =

* Michael Hasselmann (dev)
* Richard Sun (PM)
* [http://meego.com/users/mdamt Mohammad Anwari] (Architect)
* Viacheslav Sobolev (dev)
* Jon Nordby (dev)
* Aapo Kojo (ScrumMaster)
* Pekka Vuorela (lead developer)
* Rakesh Cherian ( test developer ,bug triage)
* Gibran Rodriguez (Testing)
* Jan Arne Petersen (dev)
* [http://meego.com/users/otso Otso Virtanen] (product manager)

Maliit

2011-02-28T19:36:48Z

Mdamt: /* Team */

[[Category:Maliit]]

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

= About Maliit - the MeeGo Input Methods project =

Maliit provides a flexible and cross graphical user interface toolkit input method framework. It is usable on all MeeGo user experiences.

= Features =

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

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

* 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

= Maliit in action =

* [http://www.linpus.com/products_meego_slate.html Linpus Slate] ([http://www.linpus.com/images/slate/kb.png screenshot showing Linpus virtual keyboard])
* [http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 Intel MeeGo tablet] with Swype keyboard
* [http://wiki.meego.com/Input_Method_Framework/MeeGo_1.1#Netbook Installed on MeeGo 1.1 Netbook release] with MeeGo own keyboard

[[File:Lenovo_meego_vkb.jpg|400px|MeeGo 1.1. Netbook on Lenovo S10-3T Ideapad with Maliit virtual keyboard installed.]]

* [http://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo 1.1 Handset] on Aava Mobile with MeeGo own keyboard

[[File:Meego1.1_handset_on_aava.jpg|200px|MeeGo 1.1 Handset on Aava Mobile with with MeeGo own keyboard]]

= Developers =
== Packages for Ubuntu (10.04 Lucid) ==
The MeeGo Input Methods are not 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"
# Add ppa:openismus-team/openismus-meego-im
# Add ppa:kubuntu-ppa/backports (needed for Qt 4.7, on Lucid)
# Install meego-keyboard-dev and meegotouch-demos-widgetsgallery (for simple testing) through Synaptics Package Manager

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):
meego-im-uiserver -software -bypass-wm-hint
# Test virtual keyboard in MeeGo Touch's widgetsgallery:
QT_IM_MODULE=MInputContext widgetsgallery

== Repositories ==
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework meego-im-framework]:
git clone git@gitorious.org:meegotouch/meegotouch-inputmethodframework.git
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodengine meego-im-engine]:
git clone git@gitorious.org:meegotouch/meegotouch-inputmethodengine.git
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard meego-keyboard]:
git clone git@gitorious.org:meegotouch/meegotouch-inputmethodkeyboard.git

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

= Communication channels =
== Mailing list ==
* ([https://bugs.meego.com/show_bug.cgi?id=13696 request pending])

== Bug reports and feature requests ==
* Please use [https://bugs.meego.com/enter_bug.cgi?product=OS%20Base&component=Virtual%20keyboard bugs.meego.com] for bug reports and feature requests. New ideas should first be discussed on the mailing list.

== IRC ==
Visit us in #meego-inputmethods at freenode.net

= Team =

* Michael Hasselmann (dev)
* Richard Sun (PM)
* Mohammad Anwari (Architect)

Maliit

2011-02-24T11:52:26Z

Mdamt: /* About Maliit - the MeeGo Input Methods project */

[[Category:Maliit]]

= About Maliit - the MeeGo Input Methods project =

Maliit provides a flexible and cross graphical user interface toolkit input method framework. It is usable on all MeeGo user experiences.

= Features =

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

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

* 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

= Maliit in action =

* [http://www.linpus.com/products_meego_slate.html Linpus Slate] ([http://www.linpus.com/images/slate/kb.png screenshot showing Linpus virtual keyboard])
* [http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 Intel MeeGo tablet] with Swype keyboard
* [http://wiki.meego.com/Input_Method_Framework/MeeGo_1.1#Netbook Installed on MeeGo 1.1 Netbook release] with MeeGo own keyboard

[[File:Lenovo_meego_vkb.jpg|400px|MeeGo 1.1. Netbook on Lenovo S10-3T Ideapad with Maliit virtual keyboard installed.]]

= Developers =
== Packages for Ubuntu (10.04 Lucid) ==
The MeeGo Input Methods are not 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"
# Add ppa:openismus-team/openismus-meego-im
# Add ppa:kubuntu-ppa/backports (needed for Qt 4.7, on Lucid)
# Install meego-keyboard-dev and meegotouch-demos-widgetsgallery (for simple testing) through Synaptics Package Manager

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):
meego-im-uiserver -software -bypass-wm-hint
# Test virtual keyboard in MeeGo Touch's widgetsgallery:
QT_IM_MODULE=MInputContext widgetsgallery

== Repositories ==
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework meego-im-framework]:
git clone git@gitorious.org:meegotouch/meegotouch-inputmethodframework.git
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodengine meego-im-engine]:
git clone git@gitorious.org:meegotouch/meegotouch-inputmethodengine.git
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard meego-keyboard]:
git clone git@gitorious.org:meegotouch/meegotouch-inputmethodkeyboard.git

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

= Communication channels =
== Mailing list ==
* ([https://bugs.meego.com/show_bug.cgi?id=13696 request pending])

== Bug reports and feature requests ==
* Please use [https://bugs.meego.com/enter_bug.cgi?product=OS%20Base&component=Virtual%20keyboard bugs.meego.com] for bug reports and feature requests. New ideas should first be discussed on the mailing list.

== IRC ==
Visit us in #meego-inputmethods at freenode.net

Maliit

2011-02-24T11:51:21Z

Mdamt: /* Maliit in action */

[[Category:Maliit]]

= About Maliit - the MeeGo Input Methods project =

Maliit provides a pluggable framework for input methods. It is usable on all MeeGo user experiences.

= Features =

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

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

* 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

= Maliit in action =

* [http://www.linpus.com/products_meego_slate.html Linpus Slate] ([http://www.linpus.com/images/slate/kb.png screenshot showing Linpus virtual keyboard])
* [http://www.engadget.com/photos/new-meego-tablet-user-experience-hands-on-at-mwc-2011/#3877322 Intel MeeGo tablet] with Swype keyboard
* [http://wiki.meego.com/Input_Method_Framework/MeeGo_1.1#Netbook Installed on MeeGo 1.1 Netbook release] with MeeGo own keyboard

[[File:Lenovo_meego_vkb.jpg|400px|MeeGo 1.1. Netbook on Lenovo S10-3T Ideapad with Maliit virtual keyboard installed.]]

= Developers =
== Packages for Ubuntu (10.04 Lucid) ==
The MeeGo Input Methods are not 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"
# Add ppa:openismus-team/openismus-meego-im
# Add ppa:kubuntu-ppa/backports (needed for Qt 4.7, on Lucid)
# Install meego-keyboard-dev and meegotouch-demos-widgetsgallery (for simple testing) through Synaptics Package Manager

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):
meego-im-uiserver -software -bypass-wm-hint
# Test virtual keyboard in MeeGo Touch's widgetsgallery:
QT_IM_MODULE=MInputContext widgetsgallery

== Repositories ==
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework meego-im-framework]:
git clone git@gitorious.org:meegotouch/meegotouch-inputmethodframework.git
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodengine meego-im-engine]:
git clone git@gitorious.org:meegotouch/meegotouch-inputmethodengine.git
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard meego-keyboard]:
git clone git@gitorious.org:meegotouch/meegotouch-inputmethodkeyboard.git

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

= Communication channels =
== Mailing list ==
* ([https://bugs.meego.com/show_bug.cgi?id=13696 request pending])

== Bug reports and feature requests ==
* Please use [https://bugs.meego.com/enter_bug.cgi?product=OS%20Base&component=Virtual%20keyboard bugs.meego.com] for bug reports and feature requests. New ideas should first be discussed on the mailing list.

== IRC ==
Visit us in #meego-inputmethods at freenode.net

Maliit/MeeGo 1.1

2010-11-19T12:49:03Z

Mdamt: /* Netbook */

= Handset =
Virtual keyboard works in handset UX except in N900 where there is something blocks the touchscreen usage together with the virtual keyboard.

= Netbook =
In order to get virtual keyboard on netbook UX, you need to do the following:
* enable 'handset' repository
* install 'meegotouch-inputmethodbridges' package, which should pull all other meegotouch input method dependencies
* You may need to install 'meegotouch-inputmethodkeyborad' package too
* Modify /etc/xdg/autostart/meego-im-uiserver.desktop to be look like this:
<code>[Desktop Entry]

Exec=/usr/bin/meego-im-uiserver -target slate -bypass-wm-hint

X-Moblin-Priority=High

OnlyShowIn=X-MEEGO-HS;X-MEEGO-NB
</code>

This will work with 1024x600 resolution. Replace 'slate' with other code if you have different resolution. You can get the codes from /etc/meegotouch/devices.conf file.
* Relogin (or reboot) to desktop

Any time you activate text entry, virtual keyboard will popup with special known features:
* A horizontal swipe gesture on the keyboard will change the keyboard layout.
* ENTER key is under space (shift-space)
* ENTER doesn't work in Chromium url bar (but it works on web pages)
* text entry doesn't relocate when virtual keyboard is up, so you need to manually scroll the application
* Swipe down on the keyboard closes it
* Multitouch keyboard can be enabled by doing this on console: "<code>gconftool-2 -t bool -s /meegotouch/inputmethods/multitouch/enable true</code>". With it you can type upper case letters (and ENTER) by holding Shift key. Note that the gesture might go flakey, try with double finger swipe to overcome.

Maliit/MeeGo 1.1

2010-11-17T14:25:16Z

Mdamt: /* Netbook */

= Handset =
Virtual keyboard works in handset UX except in N900 where there is something blocks the touchscreen usage together with the virtual keyboard.

= Netbook =
In order to get virtual keyboard on netbook UX, you need to do the following:
* enable 'handset' repository
* install 'meegotouch-inputmethodbridges' package, which should pull all other meegotouch input method dependencies
* Modify /etc/xdg/autostart/meego-im-uiserver.desktop to be look like this:
<code>[Desktop Entry]

Exec=/usr/bin/meego-im-uiserver -target slate -bypass-wm-hint

X-Moblin-Priority=High

OnlyShowIn=X-MEEGO-HS;X-MEEGO-NB
</code>

This will work with 1024x600 resolution. Replace 'slate' with other code if you have different resolution. You can get the codes from /etc/meegotouch/devices.conf file.
* Relogin (or reboot) to desktop

Any time you activate text entry, virtual keyboard will popup with special known features:
* A horizontal swipe gesture on the keyboard will change the keyboard layout.
* ENTER key is under space (shift-space)
* ENTER doesn't work in Chromium url bar (but it works on web pages)
* text entry doesn't relocate when virtual keyboard is up, so you need to manually scroll the application
* Swipe down on the keyboard closes it

Maliit/MeeGo 1.1

2010-11-17T14:22:42Z

Mdamt: /* Netbook */

= Handset =
Virtual keyboard works in handset UX except in N900 where there is something blocks the touchscreen usage together with the virtual keyboard.

= Netbook =
In order to get virtual keyboard on netbook UX, you need to do the following:
* enable 'handset' repository
* install 'meegotouch-inputmethodbridges' package, which should pull all other meegotouch input method dependencies
* Modify /etc/xdg/autostart/meego-im-uiserver.desktop to be look like this:
<code>[Desktop Entry]

Exec=/usr/bin/meego-im-uiserver -target slate -bypass-wm-hint

X-Moblin-Priority=High

OnlyShowIn=X-MEEGO-HS;X-MEEGO-NB
</code>

This will work with 1024x600 resolution. Replace 'slate' with other code if you have different resolution. You can get the codes from /etc/meegotouch/devices.conf file.
* Relogin (or reboot) to desktop

Any time you activate text entry, virtual keyboard will popup with special known features:
* A horizontal swipe gesture on the keyboard will change the language.
* ENTER key is under space (shift-space)
* ENTER doesn't work in Chromium url bar (but it works on web pages)
* text entry doesn't relocate when virtual keyboard is up, so you need to manually scroll the application
* Swipe down on the keyboard closes it

Maliit/MeeGo 1.1

2010-11-17T14:22:19Z

Mdamt: /* Netbook */

= Handset =
Virtual keyboard works in handset UX except in N900 where there is something blocks the touchscreen usage together with the virtual keyboard.

= Netbook =
In order to get virtual keyboard on netbook UX, you need to do the following:
* enable 'handset' repository
* install 'meegotouch-inputmethodbridges' package, which should pull all other meegotouch input method dependencies
* Modify /etc/xdg/autostart/meego-im-uiserver.desktop to be look like this:
<code>[Desktop Entry]

Exec=/usr/bin/meego-im-uiserver -target slate -bypass-wm-hint

X-Moblin-Priority=High

OnlyShowIn=X-MEEGO-HS;X-MEEGO-NB
</code>
This will work with 1024x600 resolution. Replace 'slate' with other code if you have different resolution. You can get the codes from /etc/meegotouch/devices.conf file.
* Relogin (or reboot) to desktop

Any time you activate text entry, virtual keyboard will popup with special known features:
* A horizontal swipe gesture on the keyboard will change the language.
* ENTER key is under space (shift-space)
* ENTER doesn't work in Chromium url bar (but it works on web pages)
* text entry doesn't relocate when virtual keyboard is up, so you need to manually scroll the application
* Swipe down on the keyboard closes it

Maliit/MeeGo 1.1

2010-11-17T11:47:59Z

Mdamt: /* Netbook */

Maliit/MeeGo 1.1

2010-11-17T09:59:08Z

Mdamt: /* Netbook */

Maliit/MeeGo 1.1

2010-11-17T09:58:14Z

Mdamt: /* Netbook */

Maliit/MeeGo 1.1

2010-11-17T09:55:40Z

Mdamt: Created page with "= Handset = Virtual keyboard works in handset UX except in N900 where there is something blocks the touchscreen usage together with the virtual keyboard. = Netbook = In order to…"

User:Mdamt

2010-11-09T15:29:05Z

Mdamt: Created page with "= Mohammad Anwari = http://maemo.org/profile/view/mdamt/"

= Mohammad Anwari =
http://maemo.org/profile/view/mdamt/

MeeGo Conference 2010/Volunteering

2010-11-09T15:27:40Z

Mdamt:

Your help is needed to make the MeeGo Conference 2010 a success! Please fill in your name for any of the 2 hour needed slots.

We need volunteers in the following roles:

; Conference Setup/Cleanup
: Setting up banners, installing wires, tables, chairs, ensuring that the conference hall is looking great for the early arrivals on Monday morning; and then packing everything up again on Wednesday evening. Lots of hands needed!
; Info Desk
: We need volunteers to take a couple of hours out of their conference to ensure that people know what's going on, give directions to newcomers, help co-ordinate with the conference staff when small issues arise.
; Session Tech Support
: Work with the conference center audio/visual staff, ensure that speakers are wired up with mics, that video is working, that presenters have the technical assistance they need (for example, if they need to play audio).
; Speaker Assistants
: Co-ordinate with speakers, organise a signal to let them know when they are running out of time, introduce them before their presentation, and handle audience questions on their behalf.
; Live Stream IRC Moderators
: Sit on IRC and ensure everything stays clean and on-topic. Be op for an hour!
; Breakout Room Table
: There is a room available for break-out sessions and BOFs, and we would like to ensure that people can schedule times for its use, to avoid different groups getting in each other's way. There will need to be people "manning" the schedule, and ensuring that when people arrive for a reserved session that they get priority.
; Hacking Lounge
: Some hackroom sessions may need helpers (I don't really understand what is involved here --[[User:Dneary|Dneary]] 09:44, 9 November 2010 (UTC))
; Other
: You'd like to help, but don't want to do any of the tasks above, or can't decide? Add your name here, and we will put you to use somewhere!

X = needs a volunteer

{| class="wikitable" cellpadding="5" cellspacing="0" border="1"
|- style="background:LightGrey"
! Day/Time
! Conference Setup/Cleanup
! Info Desk Needs 2 all the time
! Session Tech Support
! Speaker Assistants
! Live Stream IRC Moderators
! Breakout Room Table
! Hacking Lounge
! Other
|- style="background:LightBlue"
|colspan="9"| Saturday Nov 13
|-
| Nov 13, 13:00-15:00
|
| [[User:macron | Ronan Mac Laverty]]
|
|
|
|
|
|
|-
| Nov 13, 15:00-17:00
|
|
|
|
|
|
|
|
|-
| Nov 13, 17:00-19:00
|
|
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Sunday Nov 14
|-
| Nov 14, 9:00-11:00
|
|
|
|
|
|
|
|
|-
| Nov 14, 11:00-13:00
|
|
|
|
|
|
|
|
|-
| Nov 14, 13:00-15:00
| Needed: 5 [[User:Chippy |Chippy]] Quim Gil [[User:thomas |thomas]] [[User:macron | Ronan Mac Laverty]] Robert Gundulis 
|
|
|
|
|
|
|
|-
| Nov 14, 15:00-17:00
| Needed: 5 Andrew Flegg Aniello Del Sorbo [[User:timsamoff | timsamoff]]
|
|
|
|
|
|
|
|-
| Nov 14, 17:00-19:00
|
|
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Monday Nov 15
|-
| Nov 15, 8:00-10:00
|
| X [[User:Jsmanrique| Manrique López]]
| X
| Needed: 1 Quim Gil
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 10:00-12:00
|
| X
| X
| Needed: 1 [[User:Msinternet | Martin Saunders]]
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 12:00-14:00
|
| X
| X
| Needed: 5 [[User:mdamt | mdamt]] (preferably President then 1872 room) [[User:Chippy |Chippy]] 
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 14:00-16:00
|
| X
| X
| Needed: 5 [[User:Vdvsx | Valerio Valerio]] [[User:Chippy |Chippy]]
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 16:00-18:00
|
| [[User:timsamoff | timsamoff]]
| X
| Needed: 5
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|- style="background:LightBlue"
|colspan="9"| Tuesday Nov 16
|-
| Nov 16, 8:00-10:00
|
| X [[User:Jsmanrique | Manrique Lopez]]
| X
| Needed: 5
| X
| X
| X
|
|-
| Nov 16, 10:00-12:00
|
| X
| X
| Needed: 5 [[User:Vdvsx | Valerio Valerio]]
| X
| X
| X
|
|-
| Nov 16, 12:00-14:00
|
| X
| X
| Needed: 5 [[User:Chippy |Chippy]]
| X
| X
| X
|
|-
| Nov 16, 14:00-16:00
|
| X
| X
| Needed: 5 [[User:Chippy |Chippy]]
| X
| X
| X
|
|-
| Nov 16, 16:00-18:00
|
| [[User:timsamoff | timsamoff]]
| X
| Needed: 5
| X
| X
| X
|
|-
| Nov 16, 18:00-19:00
|
| X
|
|
| X
| X
| X
|
|- style="background:LightBlue"
|colspan="9"| Wednesday Nov 17
|-
| Nov 17, 8:00-10:00
|
| X
| X
| Needed: 2 [[User:Dneary | Dave Neary]]
| X
| X
| X
|
|-
| Nov 17, 10:00-12:00
|
| X
| X [[User:Saviq | Michał Sawicz]]
| Needed: 2 [[User: Chippy | Chippy]]
| X
| X
| X
|
|-
| Nov 17, 12:00-14:00
|
| X
| X
| Needed: 2 [[User:Chippy |Chippy]]
| X
| X
| X
|
|-
| Nov 17, 14:00-16:00
| All hands on deck [[User:Chippy |Chippy]] Quim Gil [[User:macron | Ronan Mac Laverty]]
| X
| X
| X
| X
| X
| X
|
|}

MeeGo Conference 2010/Volunteering

2010-11-09T11:34:04Z

Mdamt:

Your help is needed to make the MeeGo Conference 2010 a success! Please fill in your name for any of the 2 hour needed slots.

We need volunteers in the following roles:

; Conference Setup/Cleanup
: Setting up banners, installing wires, tables, chairs, ensuring that the conference hall is looking great for the early arrivals on Monday morning; and then packing everything up again on Wednesday evening. Lots of hands needed!
; Info Desk
: We need volunteers to take a couple of hours out of their conference to ensure that people know what's going on, give directions to newcomers, help co-ordinate with the conference staff when small issues arise.
; Session Tech Support
: Work with the conference center audio/visual staff, ensure that speakers are wired up with mics, that video is working, that presenters have the technical assistance they need (for example, if they need to play audio).
; Speaker Assistants
: Co-ordinate with speakers, organise a signal to let them know when they are running out of time, introduce them before their presentation, and handle audience questions on their behalf.
; Live Stream IRC Moderators
: Sit on IRC and ensure everything stays clean and on-topic. Be op for an hour!
; Breakout Room Table
: There is a room available for break-out sessions and BOFs, and we would like to ensure that people can schedule times for its use, to avoid different groups getting in each other's way. There will need to be people "manning" the schedule, and ensuring that when people arrive for a reserved session that they get priority.
; Hacking Lounge
: Some hackroom sessions may need helpers (I don't really understand what is involved here --[[User:Dneary|Dneary]] 09:44, 9 November 2010 (UTC))
; Other
: You'd like to help, but don't want to do any of the tasks above, or can't decide? Add your name here, and we will put you to use somewhere!

X = needs a volunteer

{| class="wikitable" cellpadding="5" cellspacing="0" border="1"
|- style="background:LightGrey"
! Day/Time
! Conference Setup/Cleanup
! Info Desk Needs 2 all the time
! Session Tech Support
! Speaker Assistants
! Live Stream IRC Moderators
! Breakout Room Table
! Hacking Lounge
! Other
|- style="background:LightBlue"
|colspan="9"| Saturday Nov 13
|-
| Nov 13, 13:00-15:00
|
|
|
|
|
|
|
|
|-
| Nov 13, 15:00-17:00
|
|
|
|
|
|
|
|
|-
| Nov 13, 17:00-19:00
|
|
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Sunday Nov 14
|-
| Nov 14, 9:00-11:00
|
|
|
|
|
|
|
|
|-
| Nov 14, 11:00-13:00
|
|
|
|
|
|
|
|
|-
| Nov 14, 13:00-15:00
| Needed: 5 [[User:Chippy |Chippy]] Quim Gil [[User:thomas |thomas]]
|
|
|
|
|
|
|
|-
| Nov 14, 15:00-17:00
| Needed: 5 Andrew Flegg Aniello Del Sorbo [[User:timsamoff | timsamoff]]
|
|
|
|
|
|
|
|-
| Nov 14, 17:00-19:00
|
|
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Monday Nov 15
|-
| Nov 15, 8:00-10:00
|
| X [[User:Jsmanrique| Manrique López]]
| X
| Needed: 1 Quim Gil
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 10:00-12:00
|
| X
| X
| Needed: 1 [[User:Msinternet | Martin Saunders]]
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 12:00-14:00
|
| X
| X
| Needed: 5 [[User:mdamt | mdamt]] (preferably President then 1872 room) 
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 14:00-16:00
|
| X
| X
| Needed: 5 [[User:Vdvsx | Valerio Valerio]]
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 16:00-18:00
|
| [[User:timsamoff | timsamoff]]
| X
| Needed: 5
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|- style="background:LightBlue"
|colspan="9"| Tuesday Nov 16
|-
| Nov 16, 8:00-10:00
|
| X [[User:Jsmanrique | Manrique Lopez]]
| X
| Needed: 5
| X
| X
| X
|
|-
| Nov 16, 10:00-12:00
|
| X
| X
| Needed: 5 [[User:Vdvsx | Valerio Valerio]]
| X
| X
| X
|
|-
| Nov 16, 12:00-14:00
|
| X
| X
| Needed: 5 [[User:Chippy |Chippy]]
| X
| X
| X
|
|-
| Nov 16, 14:00-16:00
|
| X
| X
| Needed: 5 [[User:Chippy |Chippy]]
| X
| X
| X
|
|-
| Nov 16, 16:00-18:00
|
| [[User:timsamoff | timsamoff]]
| X
| Needed: 5
| X
| X
| X
|
|-
| Nov 16, 18:00-19:00
|
| X
|
|
| X
| X
| X
|
|- style="background:LightBlue"
|colspan="9"| Wednesday Nov 17
|-
| Nov 17, 8:00-10:00
|
| X
| X
| Needed: 2 [[User:Dneary | Dave Neary]]
| X
| X
| X
|
|-
| Nov 17, 10:00-12:00
|
| X
| X [[User:Saviq | Michał Sawicz]]
| Needed: 2 [[User: Chippy | Chippy]]
| X
| X
| X
|
|-
| Nov 17, 12:00-14:00
|
| X
| X
| Needed: 2 [[User:Chippy |Chippy]]
| X
| X
| X
|
|-
| Nov 17, 14:00-16:00
| All hands on deck [[User:Chippy |Chippy]] Quim Gil
| X
| X
| X
| X
| X
| X
|
|}

Input Method Framework

2010-10-11T10:48:52Z

Mdamt: Created page with "MeeGo Input Method Framework is a framework to implement an input method. It is built with MeeGo Touch Framework. = Components = * [http://meego.gitorious.org/meegotouch/meegot…"

MeeGo Input Method Framework is a framework to implement an input method. It is built with MeeGo Touch Framework.

= Components =
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodframework MeeGo Input Method UI Framework]: The framework to implement the user interface of the input method
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodengine MeeGo Input Method Engine Framework]: The framework to implement input method engine
* [http://meego.gitorious.org/meegotouch/meegotouch-inputmethodkeyboard MeeGo Keyboard]: Implementation of virtual and hardware keyboard input method