[Shr-Devel] Dbusification of phone UI and general phone UI architecture and the role of ophonekitd in all of that.

[Sebastian Krzyszkowiak]

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>
> SK> Alternatives on SHR should *use* ophonekitd, not *replace* it.
> SK> That's why we do whole phone(g)ui stack...
>
> hi,
>
> 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
> needed.
>
> cheers
> Petr
> _______________________________________________
> Shr-devel mailing list
> Shr-devel at lists.shr-project.org
> http://lists.shr-project.org/mailman/listinfo/shr-devel
>

litephone and Paroli also aim to replace shr-settings. Those are
alternatives to whole SHR stack, not only ophonekitd.

-- 
Sebastian Krzyszkowiak
dos