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