(Created page with "{| border="0" cellpadding="4" class="wikitable" ! Task !! Assignee !! Status !! Details |- | Alternative for MInputMethodState || || n/a || We need to provide a fully working alt…") |
|||
| Line 1: | Line 1: | ||
{| border="0" cellpadding="4" class="wikitable" | {| border="0" cellpadding="4" class="wikitable" | ||
| + | |||
| + | = 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) | ||
| + | |||
| + | The outcome of this meeting were the following tasks: | ||
| + | |||
! Task !! Assignee !! Status !! Details | ! Task !! Assignee !! Status !! Details | ||
|- | |- | ||
| Task | Assignee | Status | Details |
|---|---|---|---|
| Alternative for MInputMethodState | n/a | 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 | n/a | 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 | n/a | We clean up the D-Bus API cleanup, instead of further abstraction. We will use native D-Bus types instead of (serialized) Qt datatypes. | |
| Check QtDBus status in Qt 4.8 | n/a | 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 | n/a | Obvious. Currently no overview of its intent or how it actually works, only documentation on the methods itself. |