HI, Kenneth
Tizen is using the config.xml for the permission configurations, it
requires the web app developer to
directly write the config.xml under the Tizen-GWT.
e.g. For the permissions of Alarm, need the user to add the
following in the config.xml
<tizen:privilege name="http://tizen.org/privilege/alarm.read"/>
<tizen:privilege name="http://tizen.org/privilege/alarm.write"/>
If Tizen 3.0 will use the style of Manifest.json, list an initial mappings from
the manifest.json to config.xml as below table, just for reference.
For example, if Application.read is defined in Tizen's manifest.json, the
item should be added into config.xml
<tizen:privilege name="http://tizen.org/privilege/application.read"/>
1 Currently Android Manifest has different prefix and suffix related to
the permission item.
Only necessary permission in Android related manifest.json will be picked up for
Android port. Crosswalk on Android doesn't have impact on Tizen.
2 Tizen can add more permissions in its manifest.json if needed.
3 In Android Port, the mapping will be implemented based on the
permissions that
have been defined in Crosswalk and supported by Android Manifest
Permission Name (Tizen)
Permission field in Tizen Manifest.json (If needed)
Permission fields in Tizen config.xml
Application
Application.launch
application.launch
Application.read
application.read
Application.kill
application.kill
Alarm
Alarm.read
alarm.read
Alarm.write
alarm.write
Contacts
Contacts.read
contacts.read
Contacts.write
contacts.write
CallHistory
CallHistory.read
callhistory.read
Callhistory.write
callhistory.write
Content
Content.read
content.read
Content.write
content.write
Messaging
Sms.read
sms.read
Sms.write
sms.write
Sms.receive
sms.receive
Sms.send
sms.send
Mms.receive
mms.receive
Message.sendrespond
sessage.sendrespond
Push
push
Telephony
telephonystate
telephony.state
RawSockets
RawSockets
rawsocket
Bluetooth
Bluetooth.connect
bluetooth.connect
Bluetooth.admin
bluetooth.admin
Calendar
Calendar.read
calendar.read
Calendar.write
calendar.write
SecureElement
Secure.write
secure.write
SystemSettings
System.write
system.write
Time
Time.write
time.write
Time.read
time.read
Battery
Battery
battery
NetworkServiceDiscovery
Network
network
Vibration
Vibration
vibration
Geolocation
Geolocation
geolocation
ScreenOrientation
ScreenOrientation
screenorientation
Thanks
Best regards
David
From: Kenneth Rohde Christiansen [mailto:kenneth.christian...@gmail.com]
Sent: Tuesday, December 24, 2013 6:41 PM
To: Liu, David
Cc: crosswalk-dev@lists.crosswalk-project.org
Subject: Re: [Crosswalk-dev] Intent to Implement: [Android] crosswalk manifest
permissions mapping to Android Manifest in packaging tool.
Hi there,
Comments below:
On Tue, Dec 24, 2013 at 7:33 AM, Liu, David
<david....@intel.com<mailto:david....@intel.com>> wrote:
Hi, Kenneth
Thanks for your kindly comments.
1 This intent is only for Android port. Later will try to work out
a list of the mapping to Tizen 3.0.
I understand that, but we need to make sure that we are not shooting ourselves
in the foot by making sure that this is easily applicable to Tizen 3.0 as well.
A design document with at least initial findings for Tizen 3.0 and other
platforms, would be an important step in moving forward.
2 Crosswalk currently only defines the permission name, the
permission fields in the manifest.json is defined and sent out for reviewing
which means if the user (e.g. web app user and others) wants to use the
crosswalk manifest.json and map to AndroidManaifest.xml
he can define part field or all fields in the crosswalk manifest.json
config.xml has predefined permission names for Tizen as well, and we much
support those for legacy apps.
3 Currently the mapping is used in packaging tool, later maybe it
will be used in nodejs(xwalk-apk-generator) with package.json.
Kenneth
_______________________________________________
Crosswalk-dev mailing list
Crosswalk-dev@lists.crosswalk-project.org
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
