WebAPI/WebSMS: Difference between revisions

Jump to navigation Jump to search
wip api
(create page)
 
(wip api)
Line 13: Line 13:
== Proposed API ==
== Proposed API ==


Coming soon...
This API is work in progress and mostly reflect what is implemented and is going to be really soon. Some changes are going to happen. See the comments below each interfaces.
 
navigator.sms returns an object with the following interface:
 
  interface nsIDOMSmsManager
  {
    nsIDOMSmsRequest send(in DOMString number, in DOMString message);
    void            suggestSend(in DOMString number, in DOMString message);
    unsigned short  getNumberOfMessagesForText(in DOMString text);
    SMSRequest      delete(in long uuid);
    SMSRequest (request.result == SMSIterator) get( { person: "", date: "", direction: "forward" or "backward" } );
  };
 
Comments:
* ''send'' and ''suggestSend'' could take an array of numbers.
* suggestSend could be removed in favor of Web Activities.
* maybe ''delete'' shouldn't return a SMSRequest?
 
  interface nsIDOMSmsRequest
  {
    readonly attribute unsigned short readyState;
    readonly attribute unsigned short errorCode;
    attribute nsIDOMEventListener onsuccess;
    attribute nsIDOMEventListener onerror;
    attribute readonly nsIDOMSmsMessage? message;
  };
 
Comments:
* message attribute might be removed.
 
  interface nsIDOMSmsMessage
  {
    readonly attribute long      uuid;
    readonly attribute DOMString sender;
    readonly attribute DOMString receiver;
    readonly attribute DOMString body;
    readonly attribute Date      timestamp;
  };
 
Comments:
* Have an array of receiver?
* Add a status attribute? (with the following value: ''sending'', ''sent'', ''delivered'' (not sure), ''received'')
* Merge sender/receiver and use the status attribute?
Confirmed users
368

edits

Navigation menu