canmove, Confirmed users
725
edits
Talk:WebAPI/WebTelephony: Difference between revisions
Jump to navigation
Jump to search
→philikon's thoughts
| Line 37: | Line 37: | ||
== philikon's thoughts == | == philikon's thoughts == | ||
* IMHO | * IMHO <code>navigator.telephony.dial("numbergoeshere");</code> is nicer than <code>new TelephonyCall("numbergoeshere");</code> | ||
is nicer than | |||
* We have a bunch of telephony-related functionality that's not reflected yet: | * We have a bunch of telephony-related functionality that's not reflected yet: | ||
** controlling and reading radio power | ** controlling and reading radio power | ||
** reading radio metadata (operator, signal strength, etc.) | ** reading radio metadata (operator, signal strength, etc.) | ||
** ... | ** ... | ||
* I would also suggest another readyState, <code>"dialing"</code> that comes before <code>"calling"</code> for outgoing calls. | |||
* Nits: we should probably define the possible values for readyState on the interface (nit: for XHR they're ints, not strings... I like being consistent, but I also prefers strings... hmmm...). Also, event listener objects should probably be declared as <code>EventListener</code>. | |||
My proposal on this (as a delta to the main proposal): | My proposal on this (as a delta to the main proposal): | ||
| Line 54: | Line 49: | ||
interface Telephony { | interface Telephony { | ||
void power(bool on); | void power(bool on); | ||
Some thoughts on this: | |||
TelephonyCall dial(String number); | TelephonyCall dial(String number); | ||
EventListener onpowerchange | EventListener onpowerchange | ||
EventListener onsignalstrengthchange | EventListener onsignalstrengthchange | ||
EventListener onoperatorchange | EventListener onoperatorchange | ||
} | } | ||