(Created page with "==Tasks== {|border="1" cellpadding="4" class="wikitable" |- ! Description ! Status ! Details |- | Get an own repostiory (gitorious.org/maliit) instead of meego.gitorious.org/mee...") |
|||
| Line 1: | Line 1: | ||
| + | [[Category:MaliitTasks]] | ||
==Tasks== | ==Tasks== | ||
| + | |||
| + | 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. | ||
| + | |||
{|border="1" cellpadding="4" class="wikitable" | {|border="1" cellpadding="4" class="wikitable" | ||
|- | |- | ||
| - | ! | + | ! Task |
| + | ! Assignee | ||
! Status | ! Status | ||
! Details | ! 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. | | 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% | || 90% | ||
|| | || | ||
| Line 17: | Line 23: | ||
|- | |- | ||
| Have consistent package names based on the repository names. The package names will depend on different naming conventions of different platforms. | | Have consistent package names based on the repository names. The package names will depend on different naming conventions of different platforms. | ||
| + | || | ||
|| 0% | || 0% | ||
|| | || | ||
|- | |- | ||
| Use consistent Maliit paths. | | Use consistent Maliit paths. | ||
| + | || | ||
|| 0% | || 0% | ||
|| | || | ||
| Line 28: | Line 36: | ||
* /usr/lib/meego-imengines/drivers → /usr/lib/maliit/engines | * /usr/lib/meego-imengines/drivers → /usr/lib/maliit/engines | ||
* /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) | ||
| + | || | ||
| + | || 0% | ||
| + | || | ||
| + | * /meegotouch/inputmethods/plugins → /maliit/plugins | ||
| + | * /meegotouch/inputmethods/onscreen → /maliit/onscreen | ||
| + | * /meegotouch/inputmethods/virtualkeyboard → /malitt/keyboard | ||
| + | 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. | ||
|} | |} | ||
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. | 0% |
| |
| Use Maliit based settings keys. (allow to use old ones through configure/runtime option) | 0% |
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. |