Meego Wiki
Views
From MeeGo wiki
< Maliit(Difference between revisions)
Jump to: navigation, search
(add meego input methods category)
 
(One intermediate revision not shown)
Line 12: Line 12:
! Task !! Assignee !! Status !! Details
! Task !! Assignee !! Status !! Details
|-
|-
-
| Alternative for MInputMethodState || [https://bugs.meego.com/show_bug.cgi?id=20076 BMC#20076] || in progress || We need to provide a fully working alternative for MInputMethodState. And this would also fit with our plans to offer better support for plain Qt, QML, Qt Components (and GTK+ on MeeGo). We can decide to add the less important features (toolbar and keyboard customization) at a later point, for example.
+
| Alternative for MInputMethodState || [https://bugs.meego.com/show_bug.cgi?id=20076 BMC#20076] || done || We need to provide a fully working alternative for MInputMethodState. And this would also fit with our plans to offer better support for plain Qt, QML, Qt Components (and GTK+ on MeeGo). We can decide to add the less important features (toolbar and keyboard customization) at a later point, for example.
|-
|-
| Decide on where to put extended API || [https://bugs.meego.com/show_bug.cgi?id=20076 BMC#20076] || done || No agreement yet on whether it's better to provide needed API through signals/slots in inputcontext or whether it's better to provide a separate library (in MeeGo Input Methods itself). Andy Ross is supposed to kick off the discussion on the public ML (check next week).
| Decide on where to put extended API || [https://bugs.meego.com/show_bug.cgi?id=20076 BMC#20076] || done || No agreement yet on whether it's better to provide needed API through signals/slots in inputcontext or whether it's better to provide a separate library (in MeeGo Input Methods itself). Andy Ross is supposed to kick off the discussion on the public ML (check next week).
Line 23: Line 23:
|}
|}
-
[[Category:Maliit]]
+
[[Category:Maliit]][[Category:MeeGo Input Methods]]

Latest revision as of 16:18, 12 July 2011

MeeGo Input Methods IRC meeting, March 29th 2011

How can we simplify development and maintenance of input contexts?

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

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

The outcome of this meeting were the following tasks:

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