Hello Rajesh. Interesting to hear about your experiences.
On 10 June 2014 14:42, <[email protected]> wrote: > Tried every other method, but for now only manifest.json file is > available for giving all permissions, Crosswalk is still developing. I once > tried to change something in the activity file :P, but in vain. Nothing > worked. Some permissions you cannot give at all. Like cross domain ajax > requests etc., they never work cos we usually give permissions for them in > activity file since the whole webView is generated by Crosswalk you cannot > change its settings. > Have you tried setting xwalk_hosts in the manifest file to enable cross-domain ajax? Also, if you find you need to get into the internals of Crosswalk, but can't get enough access by packaging your application using make_apk.py, you could have a look at the embedding API. This gives you finer-grained access to the Crosswalk view. I wrote up a short tutorial here: https://crosswalk-project.org/#documentation/embedding_crosswalk Elliot > > > From: <Smith>, Elliot <[email protected]> > Date: Tuesday, 10 June 2014 6:51 pm > To: "[email protected]" < > [email protected]> > Subject: [Crosswalk-help] Do manifest.json permissions have any runtime > effects on Android? > > (This relates to the question I asked yesterday about whether the > embedding API for Crosswalk does anything with the permissions field when > running on Android.) > > I've been having a close look at the permissions field in the manifest, > and how it's managed by make_apk.py. > > This mapping table is what I'm working from: > > permission_mapping_table = { > 'contacts': ['android.permission.READ_CONTACTS', > 'android.permission.WRITE_CONTACTS'], > 'geolocation': ['android.permission.ACCESS_FINE_LOCATION'], > 'messaging': ['android.permission.READ_SMS', > 'android.permission.READ_PHONE_STATE', > 'android.permission.RECEIVE_SMS', > 'android.permission.SEND_SMS', > 'android.permission.WRITE_SMS'], > 'devicecapabilities': [], > 'fullscreen': [], > 'presentation': [], > 'rawsockets': [], > 'screenorientation': [], > 'vibration': ['android.permission.VIBRATE'] > } > > Some of the fields are used to set <uses-permission> elements in > AndroidManifest.xml. > > Some of the entries don't affect packaging (presentation, fullscreen, > rawsockets, screenorientation etc.). Do they instead affect the application > when the manifest is loaded (e.g. if you use loadAppFromManifest())? > > And will a feature be disabled unless the permission is specified (so > you have to enable fullscreen explicitly, for example)? Or does specifying > this permission just prevent the user from getting a "grant permission?" > popup when these APIs are accessed? > > Finally, is there a mechanism in the embedding API to set a permission > without specifying it in a manifest.json file? (I can't see one.) > > Thanks. > Elliot > -- > Elliot Smith > Senior Software Engineer > Intel Open Source Technology Centre > > ------------------------------ > > This message is for the designated recipient only and may contain > privileged, proprietary, or otherwise confidential information. If you have > received it in error, please notify the sender immediately and delete the > original. Any other use of the e-mail by you is prohibited. Where allowed > by local law, electronic communications with Accenture and its affiliates, > including e-mail and instant messaging (including content), may be scanned > by our systems for the purposes of information security and assessment of > internal compliance with Accenture policy. > > ______________________________________________________________________________________ > > www.accenture.com > -- Elliot Smith Senior Software Engineer Intel Open Source Technology Centre
_______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
