All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: DBus APIs
Date: Wed, 13 May 2009 11:51:01 -0500	[thread overview]
Message-ID: <200905131151.01568.denkenz@gmail.com> (raw)
In-Reply-To: <4A0AE49E.8000408@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

Hi Sebastian,

On Wednesday 13 May 2009 10:17:50 Sebastian Mancke wrote:
> Hi,
>
> I just saw the new project and was wondering why there is a completely
> new project for this purpose.
>
> For me, ofone looks very similar to the freesmartphone.org initiative.
> Did you take a deep look into other existing projects? What are your
> opinions not to join those efforts?

We had a very deep look actually, and not only freesmartphone, but also 
Qtopia.  These projects are very similar to oFono on the surface, but their 
APIs just do not fill our needs.  E.g. to have a telephony stack that is GCF-
certification ready and can be used by UI developers with minimal effort on 
their part.

In the case of Qtopia it carries too much legacy baggage. In the case of FSO: 
any API that exposes such low-level details as SMS DCS will never be good 
enough.  UI developers simply should never have to care.

>
> In the case of freesmartphone.org I appreciate the goal of focusing on
> the design of the DBus APIs, instead of 'just' an implementation. It
> would be really cool to get alternative Implementations (e.g. written in
> C) for those APIs. On the other hand it would be too bad not to regard
> the experiences they made.

You're assuming that oFono developers do not have previous telephony 
experience themselves.  Not a fair assumption at all ;)  We have our own ideas 
and as pointed out above, we did learn from the FSO project.

Regards,
-Denis

  reply	other threads:[~2009-05-13 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 15:17 DBus APIs Sebastian Mancke
2009-05-13 16:51 ` Denis Kenzior [this message]
2009-05-14  6:50   ` Sebastian Mancke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200905131151.01568.denkenz@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.