[Shr-Devel] Dbusification of phone UI and general phone UI architecture and the role of ophonekitd in all of that.
seba.dos1 at gmail.com
Thu Aug 27 12:12:39 CEST 2009
On 8/26/09, Petr Vanek <vanous at penguin.cz> wrote:
> SK> > ophonekitd should preferably not have too many roles.
> SK> >
> SK> > It is currently possible to use alternatives, such as litephone.
> SK> > That will be harder, if ophonekitd does too many jobs.
> SK> >
> SK> > Helge Hafting
> SK> Alternatives on SHR should *use* ophonekitd, not *replace* it.
> SK> That's why we do whole phone(g)ui stack...
> imho, shr is already offering alternative phone stacks (paroli,
> litephone? etc.) and ophonekitd is probably in the way there... you have
> to disable it but then you cannot use shr-settings fully anymore... i
> think striking the right balance in the ophonekitd involvement would be
> Shr-devel mailing list
> Shr-devel at lists.shr-project.org
litephone and Paroli also aim to replace shr-settings. Those are
alternatives to whole SHR stack, not only ophonekitd.
More information about the Shr-devel