(→Framework) |
(→MeeGo 1.3) |
||
| Line 6: | Line 6: | ||
Development in in progress. | 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.2x''': Still uses MeeGo Touch. | ||
| - | * '''0.8x''': Compiles MeeGo Touch free version by default. | + | * '''0.8x''': Compiles MeeGo Touch free version by default, has legacy build option. (DONE) |
| + | ** Maliit now an [http://lists.meego.com/pipermail/meego-dev/2011-June/483406.html independent project]. | ||
** Installation paths, library names and GConf keys now follow new Maliit naming conventions. | ** 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. | ** 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 | * '''0.9x''': Alpha release that will lead up to Maliit 1.0 | ||
| Line 19: | Line 27: | ||
** API cleanup should be done for all Maliit libraries (including engines and feedback API). | ** 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. | ** In first release for the 0.9x series, the C++ based reference VKB (Maliit Keyboard) will be LMT-free. | ||
| - | * '''1.0''' | + | * '''1.0''': Stable release |
| - | + | ||
| - | + | ||
=== Framework === | === Framework === | ||
| Line 28: | Line 34: | ||
* Better support for Qt applications not linked to MeeGo Touch | * Better support for Qt applications not linked to MeeGo Touch | ||
** Orientation change | ** Orientation change | ||
| - | * | + | * 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 === | === MeeGo Keyboard === | ||
| Line 36: | Line 41: | ||
* New word prediction widgets: Word Ribbon (DONE) | * New word prediction widgets: Word Ribbon (DONE) | ||
* Extended support for CJK languages | * Extended support for CJK languages | ||
| - | * Remove libmeegotouch dependency | + | * Remove libmeegotouch dependency |
== MeeGo 1.2 == | == MeeGo 1.2 == | ||
| Maliit - Input Methods for MeeGo |
|---|
| Overview · Development · Installing · Roadmap |
Submit your ideas in Ideas page to get considered to be put into the roadmap.
Contents |
Development in in progress.
MeeGo 1.3 will have Maliit 1.0.
Development in progress.
With Maliit 1.0 the goal is long-term API stability for application and input method plugin API.
All items in this section are DONE.
| Maliit - Input Methods for MeeGo |
|---|
| Overview · Development · Installing · Roadmap |