<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Daniel Robinson wrote:
<blockquote
cite="mid:eef811f30707181509n368789a3pbdd2266587323b6b@mail.gmail.com"
type="cite">I don't know how much of the at signaling is available at
the data terminal. What is the signaling for sending caller ID to a
cellular phone? For example, on POTS, the digits are signaled with a
Bell 103 modem between the first and second ring. <br>
<br>
Someone said something about having the ringback tone be a sound file
that is configurable according to caller. I don't know if that is
possible from the phone. The ring back tone is generated by switching
equipment, not the terminal.
<br>
</blockquote>
To clarify, I'm thinking not of getting in the way of the basics of
things like gsmd, which should handle the fact that there is an
incoming call and also pick up the caller ID if present, but what
openmoko does as a result of this information. Given the fact that
there is an incoming call from number 555-123-4567 what should the
'phone do? Should it silently ignore the call, send it straight to
voicemail (either operator or on the 'phone itself), use a specific
ringtone for the user, even shut down entirely (some sort of "if I ring
my 'phone from this number then nuke it" option!). The point is, there
are lots of possibilities and we don't want them all sitting inside
gsmd, it makes more sense for them to be external modules that can be
chained together in a clean fashion without requiring direct access to
something as sensitive as gsmd. At least, that's my take on it.<br>
<br>
<blockquote
cite="mid:eef811f30707181509n368789a3pbdd2266587323b6b@mail.gmail.com"
type="cite">--Dan<br>
</blockquote>
<br>
Cheers,<br>
Jim.<br>
<blockquote
cite="mid:eef811f30707181509n368789a3pbdd2266587323b6b@mail.gmail.com"
type="cite"><br>
<div><span class="gmail_quote">On 7/18/07, <b
class="gmail_sendername">Jim McDonald</b> <<a moz-do-not-send="true"
href="mailto:Jim@devzero.net">Jim@devzero.net</a>> wrote:</span>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
<div lang="x-unicode">
<div lang="x-unicode">[This may have been better
to post to the development list but as
people are talking about it here I'll start here]<br>
<br>
Hi,<br>
A number of people have been talking about the cool things that they
would like their 'phone to do but after spending some time looking at
the information available so far I don't see anything that suggests the
current codebase will allow people the freedom that they need. If I
take a simple example of an incoming call them some of the suggestions
that we have seen so far to handle it include different ring tones for
different people or groups of people, auto-handling of the call by
sending it to voicemail or letting it through, different responses
depending on the time of day, <i>etc. </i>The point that I'm trying
to make is that there are a multitude of things that you <i>could</i>
do but each person will have a limited number of things that they want
the 'phone to <i>actually</i> do. As such, building out all of these
options in to a single piece of code will not only be very hard to
manage and maintain but will severely limit the ability of people to
scratch their itches and develop code to make the 'phone do what they
want it to.<br>
<br>
If the monolithic approach is out then some sort of modular approach
is required. The most obvious example out there today is Firefox,
which comes in a relatively simple base configuration but provides any
number of hooks to allow people to write their own extensions on top of
the base code and as such to alter the functionality of the product
very extensively. If we want this openmoko to be as free as possible
then it also needs to be as easy as possible for people to extend, and
this is the most likely way of doing it.<br>
<br>
I know that there are a lot of potential problems that need to be
addressed when building this out but if there is a vision from the
start as to how this would work then it would go a long way to making
the final product the 'phone that we are all dreaming of, regardless of
the fact that those dreams are often divergent from others if not
totally exclusive. So my questions are there plans to include these
hooks, and if not can it be considered?<br>
<br>
Or is there another way to do this other than hooks?<br>
<br>
Cheers,<br>
Jim.<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
OpenMoko community mailing list<br>
<a moz-do-not-send="true"
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a>
<br>
<a moz-do-not-send="true"
onclick="return top.js.OpenExtLink(window,event,this)"
href="http://lists.openmoko.org/mailman/listinfo/community"
target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
<br>
</blockquote>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
OpenMoko community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openmoko.org/mailman/listinfo/community">http://lists.openmoko.org/mailman/listinfo/community</a>
</pre>
</blockquote>
<br>
</body>
</html>