| Line 38: | Line 38: | ||
* /usr/share/meegotouch/virtual-keyboard → /usr/share/maliit/keyboard | * /usr/share/meegotouch/virtual-keyboard → /usr/share/maliit/keyboard | ||
|- | |- | ||
| - | + | | Use Maliit based settings keys. (allow to use old ones through configure/runtime option) | |
|| | || | ||
|| 100% | || 100% | ||
| Line 47: | Line 47: | ||
When switching to DConf we could just use /org/maliit/... | When switching to DConf we could just use /org/maliit/... | ||
|- | |- | ||
| - | + | | Provide prototype for styling through extended attributes. | |
|| | || | ||
|| 0% | || 0% | ||
|| Keep the idea of generated style container classes, as they provide nice type safety. But at the same time, allow controlling of those attributes through extended attributes API (domain "/style"). | || Keep the idea of generated style container classes, as they provide nice type safety. But at the same time, allow controlling of those attributes through extended attributes API (domain "/style"). | ||
|- | |- | ||
| - | + | | Analyse functional dependencies between key styles | |
|| | || | ||
|| 0% | || 0% | ||
|| Fight combinatorial state explosion in key styling, probably by defining functional dependencies ("A pressed key always uses Color#2 when highlighted") and by using a styling state machine for keys. | || Fight combinatorial state explosion in key styling, probably by defining functional dependencies ("A pressed key always uses Color#2 when highlighted") and by using a styling state machine for keys. | ||
| + | |- | ||
| + | | Register Maliit project @ [http://freedesktop.org freedesktop.org] in order to get own bugtracker and mailing lists | ||
| + | || Jon | ||
| + | || 0% | ||
| + | || | ||
|} | |} | ||
These are the remaining tasks to make Maliit an independent upstream project and to remove any trace/dependency to LMT in Maliit framework and its reference keyboard.
| Task | Assignee | Status | Details |
|---|---|---|---|
| Get an own repostiory (gitorious.org/maliit) instead of meego.gitorious.org/meegotouch. Maliit repo will be the new upstream project for Harmattan and MeeGo Input Methods. | Michael | 90% |
|
| Have consistent package names based on the repository names. The package names will depend on different naming conventions of different platforms. | 0% | ||
| Use consistent Maliit paths. | 100% |
| |
| Use Maliit based settings keys. (allow to use old ones through configure/runtime option) | 100% |
When switching to DConf we could just use /org/maliit/... | |
| Provide prototype for styling through extended attributes. | 0% | Keep the idea of generated style container classes, as they provide nice type safety. But at the same time, allow controlling of those attributes through extended attributes API (domain "/style"). | |
| Analyse functional dependencies between key styles | 0% | Fight combinatorial state explosion in key styling, probably by defining functional dependencies ("A pressed key always uses Color#2 when highlighted") and by using a styling state machine for keys. | |
| Register Maliit project @ freedesktop.org in order to get own bugtracker and mailing lists | Jon | 0% |