- From: Tran, Dzung D <dzung.d.tran@intel.com>
- Date: Mon, 21 Dec 2009 13:58:44 -0800
- To: Suresh Chitturi <schitturi@rim.com>, "richard.tibbett@orange-ftgroup.com" <richard.tibbett@orange-ftgroup.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
+1 for second method Dzung Tran -----Original Message----- From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Suresh Chitturi Sent: Monday, December 21, 2009 01:15 PM To: richard.tibbett@orange-ftgroup.com; public-device-apis@w3.org Subject: RE: [contacts] Extending the Contacts.create() method Hi Richard, all, My opinion is that such convenience methods is useful (can lead to fewer lines of code). I would prefer the second choice over the first among the two options below. Regards, Suresh -----Original Message----- From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of richard.tibbett@orange-ftgroup.com Sent: Monday, December 21, 2009 11:32 AM To: public-device-apis@w3.org Subject: [contacts] Extending the Contacts.create() method Hi, Just documenting some thoughts on improving the Contacts.create(...) method [1] to allow for additional contact attributes to be specified at object creation. The method could be overloaded as follows: interface Contacts { Contact create (in DOMString name); Contact create (in ContactProperties options); // ... Other methods }; Or it could be extended with optional additional contact attributes as follows: interface Contacts { Contact create (in DOMString name, in optional ContactProperties options); // ... other methods }; Any feedback on the best approach, or whether the current simple create(...) method [1] is sufficient is welcome :-) Kind Regards, Richard [1] http://dev.w3.org/2009/dap/contacts/#widl-Contacts-create --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Monday, 21 December 2009 21:59:26 UTC