Hi Sakari, On the meeting, Anssi suggest to use xwalk.experimental and send out email. Please check his reply.
Thanks, Halton. From: Poussa, Sakari Sent: Thursday, November 21, 2013 1:34 PM To: Huo, Halton; Kenneth Rohde Christiansen Cc: crosswalk-dev@lists.crosswalk-project.org Subject: Re: [Crosswalk-dev] Intent to Implement: [Android] W3C DeviceCapabilities/Codecs xwalk.sysapps I though it was already clear from my previous message. BR; Sakari From: <Huo>, Halton <halton....@intel.com<mailto:halton....@intel.com>> Date: Wednesday, November 20, 2013 at 5:05 To: Sakari Poussa <sakari.pou...@intel.com<mailto:sakari.pou...@intel.com>>, Kenneth Rohde Christiansen <kenneth.christian...@gmail.com<mailto:kenneth.christian...@gmail.com>> Cc: "crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org>" <crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org>> Subject: RE: [Crosswalk-dev] Intent to Implement: [Android] W3C DeviceCapabilities/Codecs Hi Sakari, Could you make a final decision which namespace that sysapp API will using? navigator.* or xwalk.sysapps.*? Thanks, Halton. From: Poussa, Sakari Sent: Tuesday, November 19, 2013 7:04 PM To: Kenneth Rohde Christiansen Cc: Huo, Halton; crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org> Subject: Re: [Crosswalk-dev] Intent to Implement: [Android] W3C DeviceCapabilities/Codecs Sorry, my bad. I thought all the sysapps APIs are under navigator, but seems that they are using xwalk.sysapps.* Then this API should follow that pattern as well. Which I guess is what Kenneth is also saying. BR; Sakari From: Kenneth Rohde Christiansen <kenneth.christian...@gmail.com<mailto:kenneth.christian...@gmail.com>> Date: Tuesday, November 19, 2013 at 12:24 To: Sakari Poussa <sakari.pou...@intel.com<mailto:sakari.pou...@intel.com>> Cc: "Huo, Halton" <halton....@intel.com<mailto:halton....@intel.com>>, "crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org>" <crosswalk-dev@lists.crosswalk-project.org<mailto:crosswalk-dev@lists.crosswalk-project.org>> Subject: Re: [Crosswalk-dev] Intent to Implement: [Android] W3C DeviceCapabilities/Codecs Still, all other sysapps API's are "prefixed" as they are under the sysapps.* namespace. Thus if the specs change at some point they can be migrated to another place and two incompatible implementations can be supported in parallel, with the one under sysapps.* as deprecated. When you add things directly under navigator.* you can never reuse that place for the final API when it reached Recommendation level. This scares me. Kenneth On Tue, Nov 19, 2013 at 10:07 AM, Poussa, Sakari <sakari.pou...@intel.com<mailto:sakari.pou...@intel.com>> wrote: Hi, I would not like to prefix it. Actually, I think it would be fine to use the namespace as in the the spec (navigator). All the SysApps APIs are now more or less experimental and if we start second guessing what is more mature than the other, we'll have this discussion for each API. Thus, my recommendation is just to implement the spec as it is now. BR; Sakari
_______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
