Jump to content

PIM/Mobile: Difference between revisions

From KDE Community Wiki
< PIM
Vkrause (talk | contribs)
Line 26: Line 26:
! Status !! Task !! Description !! Contact
! Status !! Task !! Description !! Contact
{{FeatureTodo|Draft support|Save and restore drafts||}}
{{FeatureTodo|Draft support|Save and restore drafts||}}
{{FeatureTodo|Feedback while processing|Disable input, avoid double send clicks, progress feedback, error reporting||}}
{{featureInProgress|Feedback while processing|Disable input, avoid double send clicks, progress feedback, error reporting|[email protected]| Anselmo}}
{{FeatureTodo|Editor scrolling|Eg. by expanding the editor to show the entire content and using a toplevel QML Flickable element||}}
{{FeatureTodo|Editor scrolling|Eg. by expanding the editor to show the entire content and using a toplevel QML Flickable element||}}
|}
|}

Revision as of 15:36, 23 June 2010

KDE PIM for Mobile Devices

Stuff that needs to be done

A still very incomplete, high-level list of tasks.

General

Status Task Description Contact
TO DO Slideout Panels Make them as pretty as Nuno wants them to be
TO DO Text Input Focus Key presses end up in text input fields without focus <Artur>
TO DO Action slideout panel for more actions Find a way to organize more than 6 actions in there, Nuno, Björn and Steve have various ideas for that already
TO DO Native file dialogs There are ugly patches in komo/kdelibs which deal with some of them already
IN PROGRESS Progress reporting Indicate that a folder/mail/etc. is currently being loaded
TO DO Startup Screen Initial Akonadi startup takes a bit, so show some progress for example. Also consider an error overlay like on the desktop.

KMail Mobile

Composer

Status Task Description Contact
TO DO Draft support Save and restore drafts
IN PROGRESS Feedback while processing Disable input, avoid double send clicks, progress feedback, error reporting
TO DO Editor scrolling Eg. by expanding the editor to show the entire content and using a toplevel QML Flickable element