[Gpephone-devel] Tasks and task priority

[YU Yijun RD-ILAB-PEK]

Hi, Florian,

It's a good starting point and I think now it is time to elaborate each item a little bit (something similar as high level design) before we dig further into them. I suggest we can merge the list with that in the wiki and then illustrate one by one. 

Taking your expertise into consideration, could you start with some of the items, e.g.:
Hotkey configuration,
Network connectivity management,
power management notification and awareness,
evaluate usable theme engines, create at least one decent example theme
(Sapwood theme engine?)

Regards
Yu Yijun

>-----Original Message-----
>From: gpephone-devel-bounces at linuxtogo.org
>[mailto:gpephone-devel-bounces at linuxtogo.org] On Behalf Of Florian Boor
>Sent: 2007年7月24日 0:37
>To: gpephone-devel at linuxtogo.org
>Subject: [Gpephone-devel] Tasks and task priority
>
>Hello all,
>
>in order to make GPE Phone Edition a complete and usable framework we need to
>find out what we actually need to have. I assume that we maybe want to make use
>of some bits Hiker provides. Some tasks contain hints about how to start with
>them.) I left out all optional tasks - just the essential ones for now:
>
>
>Applications
>
>- PIM data exchange via OBEX (Hiker Exchange manager?)
>- More flexible homescreen and application launcher.
>- File manager (in progress, use gpe-filemanager / GnomeVFS)
>- Task switcher
>- gpe-phonepanel plugin to select and display the ptim input method
>- Text input method for devices with numeric keypad
>- Camera application
>- Control panel (power down, wifi on/off, gsm on/off - maybe profile selection)
>
>
>Configuration
>
>- connectivity setup and control (GSM, UMTS, Wifi, Bluetooth...)
>- audio preferences
>- IP network configuration
>- screen calibration, backlight control
>- time, date and language / locale
>- GSM settings
>- sounds and eyecandy (ringtones, themes, wallpapers)
>
>The configuration tasks that do system level settings need to be designed for
>privilege separation: The UIs should not run as root user while the backends
>need to have additional privileges. Considering to use a part of the Hiker
>framework that's a must anyway.
>
>
>Framework
>
>- hotkey configuration (should be a static, system wide configuration)
>- event manager, idle detection (button and hardware events, might become part
>of application launcher and machined)
>- filesystem abstraction to avoid exposing the whole filesystem to users
>- application lifecycle management (Hiker)
>- use of a unified settings API (Hiker?)
>- phoneserver + TAPI improvements (e.g. stability, portability, delivery of dbus
>status signals)
>- network connectivity management (Maybe based on NetworkManager, we have a
>modified one for PDA use somewhere.)
>- introduction of security mechanisms
>- power management notification and awareness (It might be worth to take a look
>at Maemo here.)
>- alarm framework (Hiker?)
>- evaluate usable theme engines, create at least one decent example theme
>(Sapwood theme engine?)
>
>
>Greetings
>
>Florian
>
>--
>The dream of yesterday                  Florian Boor
>is the hope of today                    Tel: +49 271-771091-15
>and the reality of tomorrow.            Fax: +49 271-771091-19
>[Robert Hutchings Goddard, 1904]        florian.boor at kernelconcepts.de
>
>1D78 2D4D 6C53 1CA4 5588  D07B A8E7 940C 25B7 9A76
>
>_______________________________________________
>Gpephone-devel mailing list
>Gpephone-devel at linuxtogo.org
>http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/gpephone-devel