08-27-2006, 07:34 PM
|
|
|
Join Date: 11-07-2001
|
|
Location: Miami, FL
|
|
PDAPhone: Touch
|
|
Carrier: Sprint
|
|
Headset: BT8020
|
| Posts:
132 |
 |
|
How exposed to 3rd party developers is 6700's "phone" API?
How exposed to thirdparty developers is the 6700's "phone" API -- the API used by the default "phone" app when you make/receive calls, dial numbers, etc? In theory, does enough public information exist for someone to completely replace the built-in "phone" app with one they wrote?
Put another way... are there API-level commands that would enable a thirdparty app to wait for notification that there's an incoming call, and directly handle the events arising from it itself? Say...
* doze until incoming call
* Incoming Call!
* fetch caller id info from event object
* look for matching info somewhere
* display info on screen alerting user that xxx is calling and show picture (or just display number and caller id info if that's all that's available)
* spawn thread to play soundtracker mod until notified to stop
* wait for notification that call has gone to voicemail, or user input event signaling desire to answer call
-- user wants to answer call:
* tell modplayer to stop playing
* tell phone to answer call
* update screen to indicate call in progress
* wait for call to drop, or user to press key indicating desire to end call
... keep waiting
etc
... and, just as importantly, are any of those APIs locked/disabled/crippled by Sprint?
I tried looking the info up at MSDN, but I have no idea what to search for. I've gotten the impression that the API and capability exists (on paper, at least), but up to now nobody except Palm has actually taken advantage of it to change the default phone user interface (apparently, the fact that Palm decided to deviate from the norm and customize/rewrite the default UI was sufficiently newsworthy to make headlines).
|
|
|
|
|