{ "id": "63589", "key": "TIMOB-2957", "fields": { "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": { "id": "2", "description": "The problem described is an issue which will never be fixed.", "name": "Won't Fix" }, "resolutiondate": "2013-01-14T10:35:31.000+0000", "created": "2011-04-15T03:33:43.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [], "versions": [ { "id": "11233", "name": "Release 1.6.0", "archived": true, "released": true, "releaseDate": "2011-02-23" } ], "issuelinks": [], "assignee": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-22T17:22:38.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" } ], "description": "{html}
On the incredible there is no external data storage so when I\r\nwrote a file I need the ability to set the privilege on it so it\r\ncan be accessed by another activity not belonging to my app\r\n(Context.MODE_WORLD_READABLE).
\r\nExpose MODE_WORLD_READABLE through the Ti.Filesystem module on\r\nAndroid. I will ask the enterprise client to post more information\r\non their preference for this exposure.
\r\nAdding some kind of permission property on to the object\nTitanium.Filesystem.File would work for me. Thanks!
Any chance we can get this moved into 1.7?
Opie, this needs to be considered for our spec as appropriate.\nI'm assigning it to S12 so that it can scoped wrt the spec. We will\ndo the work once the spec has been approved. Please move it back\ninto the new state once you update the spec and this ticket with\nany pertinent information.
This item was taken into consideration for the stream spec and\nshould be moved to another milestone I think where it can be\ngrouped with the stream implementation. Assigning back to Don for\nplacement.