It is fine not to support MMS now. Hopefully never. BR; Sakari
From: <Gao>, Shawn <[email protected]<mailto:[email protected]>> Date: Friday, December 6, 2013 at 7:27 To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [Crosswalk-dev] Intent to Implement System App Messaging API Hi, All, This copy/paste code implementation is too dirty. And, use unofficial interface and api will be unstable in further Android release. Maybe should be rewrite in future. Considering the MMS issues described in my previous mail below, I suggest not to do such copy/paste exercise, and hold the MMS API implementation until the required MMS APIs are officially supported in Android SDK. Thanks, Shawn From: Crosswalk-dev [mailto:[email protected]] On Behalf Of Gao, Shawn Sent: Friday, December 6, 2013 10:41 AM To: [email protected]<mailto:[email protected]> Subject: Re: [Crosswalk-dev] Intent to Implement System App Messaging API MMS Issue: 1. Android sdk doesn’t have official mms send/receive api. We should copy a bunch of code from android source code, the android native mms apps. We should reinvent a MMS app from scratch. 2. MMS not only includes single image or audio, but also has a complicate format, SMIL, to assemble files and text together, something like HTML. We should copy parsing and rendering code from android source code for SMIL. From: Crosswalk-dev [mailto:[email protected]] On Behalf Of Gao, Shawn Sent: Monday, November 11, 2013 3:20 PM To: [email protected]<mailto:[email protected]> Subject: [Crosswalk-dev] Intent to Implement System App Messaging API Intent to Implement System App Messaging API Summary: This implementation is going to add Messaging API(http://www.w3.org/2012/sysapps/messaging/). Let Javascript developers have ability to send/receive sms/mms and manage messages on Crosswalk. Managing features include find by filter, read and delete messages. Affected component: /xwalk/runtime Related feature: https://crosswalk-project.org/jira/browse/XWALK-53 Target Release: M4 Implementation details: There are 3 parts of implementation. SmsManager, MmsManager, MessagingManager. Each of the 3 is divided into 2 side, Java side and Javascript side. 1. SmsManager. 1) Send. Javascript side, when send api is called, create and push promise object to waiting list. If get send ok/failure message from Java side, found promise object by id and call resolve function. Java side, register intent for send ok/failure event and delivery ok/failure event. When gets send request from Javascript, call Android send sms api. Then receive the ok/failure event, and send these back to Javascript side. 2) Receive. Javascript side, register receive event handler. Java side, register receive event handler by Android Api. When sms comes, send message to Javascript side and call receive event handler. 2. MmsManager. Similar with SmsManager. 3. MessagingManager. Javascript side is similar to SmsManager 1) Find. Search sms/mms by ContentResolver. 2) Read. Read one sms/mms by ContentResolver. 3) Delete. Delete sms/mms by ContentResolver. _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
