On Thu, Oct 10, 2013 at 9:56 AM, Kenneth Rohde Christiansen < kenneth.christian...@gmail.com> wrote:
> We need to support config.xml for legacy apps and it would work like > for current tizen apps. > By "legacy apps" are you referring only to pure W3C .wgt apps, or W3C .wgt derivative apps (Tizen, Blackberry, etc.)? For those not familiar with how much is OS specific in those formats, you can see the document on converting a web app to Tizen [1], specifically pages 33-42. > As far as I understand it, this is 100% platform specific, right? > >From the standpoint of Crosswalk application developers, it is should be 0% platform specific. Implementation wise within Crosswalk (or Crosswalk packaging utilities) your statement is accurate. The interface exposed to Crosswalk application developers needs to be platform agnostic. Application developers might care about device characteristics (screen density, orientation, hardware features, etc.) -- but they shouldn't need to know how (for example) to request Bluetooth access for each OS/platform. James 1. http://download.tizen.org/misc/media/conference2012/wednesday/ballroom-a/2012-05-09_1415-1455-converting_your_web_app_to_tizen.pdf > I agree with James, we should start by creating a matrix of all the > various permissions existing in the different platforms to get a > better idea of it all. > > Kenneth > > On Wed, Oct 9, 2013 at 5:54 PM, Ketrenos, James P > <james.p.ketre...@intel.com> wrote: > > Android's Mainfest.permissions are another example of the feature level > that > > would need to be called out in the application manifest (in order for the > > Crosswalk packaging infrastructure to be able to map the Crosswalk > > declaration to the appropriate target OS feature) > > > > You can find their table here: > > http://developer.android.com/reference/android/Manifest.permission.html > > > > It might be good to create a matrix of all the different permission > features > > supported by the various containment systems (iOS, Android, Metro, Tizen, > > Chrome Packaged Apps) > > > > James > > > > > > On Wed, Oct 9, 2013 at 2:01 AM, Zhu, Yongsheng <yongsheng....@intel.com> > > wrote: > >> > >> Ming Bai, > >> > >> Thanks for starting the discussion for them. It would be really helpful > >> for us. 3 questions: > >> > >> 1. What kind of features will be added into permissions and what > >> kind of features will be in requirements? How are the relationship with > >> SysApps and HTML5 fetures? > >> > >> 2. Some of permissions are for browser specific usage, like > >> bookmark. Do you think they’re valid for crosswalk? > >> > >> 3. Have you considered the usage scenarios for Android since all > of > >> them are from Tizen but will be shared by all platforms? > >> > >> > >> > >> Yongsheng > >> > >> > >> > >> From: crosswalk-dev-boun...@lists.crosswalk-project.org > >> [mailto:crosswalk-dev-boun...@lists.crosswalk-project.org] On Behalf Of > >> Ming, Bai > >> Sent: Wednesday, October 09, 2013 4:45 PM > >> To: Poussa, Sakari; Christiansen, Kenneth R; Kostiainen, Anssi; > Oliveira, > >> Caio; You, Yongkang; Zhang, Xu U; > crosswalk-dev@lists.crosswalk-project.org > >> Subject: [Crosswalk-dev] Crosswalk API permissions and requirements > >> > >> > >> > >> Hi all, > >> As we are pushing forward our implementation of runtime model and > >> extension APIs, it's becoming increasingly important and urgent for us > to > >> finalize the category of API permissions requirements, on which many > other > >> features are dependent, like manifest, security architecture, API > itself, > >> and so forth. So let me first introduce a little bit about it in case > some > >> of you may not very familiar with. > >> This http://developer.chrome.com/apps/manifest.html is the chromium > >> manifest definition. There are two regions regarding the issue in > question: > >> > >> "permissions": [...], > >> > >> "requirements": {...}, > >> > >> The permissions is the field an application must declare in its > >> manifest in order to use the corresponding API. For example "alarms" for > >> chrome.alarms API. > >> The requirements denotes the technologies required by the > application, > >> it may looks like this > >> > >> "requirements": { > >> > >> "3D": { > >> > >> "features": ["webgl"] > >> > >> } > >> > >> } > >> > >> In Tizen we also have these permissions and requirements defined, > in a > >> similar way. For example the privilege " > http://tizen.org/privilege/alarm"; > >> maps to the Alarm APIs ( add,remove,etc..) You may refer to the > attachment > >> for more details. > >> So as you are all aware, we've got a lot of APIs to implement, some > of > >> which comes from tizen and some from w3c, and we also have a road map > for > >> that. The issue is, we need a way to categorize these APIs into > different > >> permission/requirement groups, just like that in Tizen or chromium. It > might > >> be a little hard for us because we may need to align with W3c or Tizen. > >> How do you think? > >> > >> > >> -- > >> > >> - Ming, Bai > >> > >> > >> _______________________________________________ > >> Crosswalk-dev mailing list > >> Crosswalk-dev@lists.crosswalk-project.org > >> https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev > >> > > > > > > _______________________________________________ > > Crosswalk-dev mailing list > > Crosswalk-dev@lists.crosswalk-project.org > > https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev > > > > > > -- > Kenneth Rohde Christiansen > Web Platform Architect, Intel Corporation. > Phone +45 4294 9458 ﹆﹆﹆ >
_______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
