Submit your ideas in Ideas page to get considered to be put into the roadmap.
MeeGo 1.3
Development in in progress.
MeeGo 1.3 will have Maliit 1.0.
- New package-names (DONE)
- Settings applet for meego-ux-settings
- Better integration with standard applications
Maliit 1.0
Development in progress.
With Maliit 1.0 the goal is long-term API stability for application and input method plugin API.
- 0.2x: Still uses MeeGo Touch.
- 0.8x: Compiles MeeGo Touch free version by default, has legacy build option. (DONE)
- Maliit now an independent project.
- Installation paths, library names and GConf keys now follow new Maliit naming conventions.
- Legacy LMT build can be done using qmake CONFIG+=nomeegotouch (works in -framework and -plugins repo).
- No API changes in plugin or application API! New library structure will require recompilation though.
- 0.9x: Alpha release that will lead up to Maliit 1.0
- Will contain API cleanups (not LMT related, but rather about removing cruft and cleanup).
- API cleanup should be done for all Maliit libraries (including engines and feedback API).
- In first release for the 0.9x series, the C++ based reference VKB (Maliit Keyboard) will be LMT-free.
- 1.0: Stable release
Framework
- Use D-Bus datatype instead of serialized Qt types in D-Bus API (DONE)
- Support for non X11 platform
- Better support for Qt applications not linked to MeeGo Touch
- Unified, UI independent, settings API
- Probably even hide the framework's GConf usage behind some API that can be used by apps and plugins.
MeeGo Keyboard
- Key magnification and accent pop-ups (DONE)
- New word prediction widgets: Word Ribbon (DONE)
- Extended support for CJK languages
- Remove libmeegotouch dependency
MeeGo 1.2
All items in this section are DONE.
Framework
- private D-Bus connection
- new information exposures:
- anchor position
- cursor position
- libmeegotouch removal
- self-compositing
- self-rotation animation
Engine framework
- New interface: Handwriting recognition
- New functionality: Dynamic virtual keyboard layout