{ "id": "62226", "key": "TIMOB-1594", "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": [ { "id": "11227", "name": "Release 1.5.0 M02", "archived": true, "released": true, "releaseDate": "2010-11-22" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T01:56:37.000+0000", "created": "2011-04-15T02:56:55.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "android", "feature" ], "versions": [], "issuelinks": [], "assignee": { "name": "mculpepper", "key": "mculpepper", "displayName": "Marshall Culpepper", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-04-17T01:56:37.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}
Allow activity entries to be described in an section of\ntiapp.xml it will need to work with code generation and build to\ncreate the appropriate activity shims to AndroidManifest.xml\nentries.
(from [d5d94b0af6c3cba8c379e8d9cea20b1ac257f894])\n[#1594] Beginnings of android manifest settings\nin tiapp.xml. Currently supports screen settings, permissions and\nsimple activity declarations (no attributes beyond name). See\nhttp://gist.github.com/624357\nfor sample tiapp.xml. \nhttp://github.com/appcelerator/titanium_mobile/commit/d5d94b0af6c3c...
(from [4c057f4b09cf55e8e64d078d5a881623275d4ee1])\n[#1594] Support attributes on the activities\n(still no support for intent filter). Support services. Make the\nentire supports-screens section in manifest template replaceable by\nwhat's in tiapp.xml, and put defaults in the tiapp.xml template --\nas well as defaults in the builder.py code in case the section is\nmissing from tiapp.xml, which will occur if app created < 1.5\n\nhttp://github.com/appcelerator/titanium_mobile/commit/4c057f4b09cf5...
Pull screens / permissions out of <android>, will go under\n<android><manifest>, which will go \"as-is\" into\ngenerated manifest.
(from [931e61d2725bb93d3cad6b9fc8ce62a513558167])\n[#1594] Move tiapp <android:manifest> to ,\nsupport (JS-based activities) and generate their entries in\nAndroidManifest.xml \nhttps://github.com/appcelerator/titanium_mobile/commit/931e61d2725b...
(from [9985f8f908c01a722823bec6d4cd34df97c198c1])\n[#1594 state:resolved] Map entries from tiapp.xml\ninto the generated AndroidManifest.xml, including any attributes\nthate are put on to the and elements in tiapp.xml. Differentiate\nbetween stuff that's additive (such as entries) versus stuff that\nneeds to replace entries in the manifest because they only appear\nonce (<uses-sdk> and <supports-screens>). [#2375\nstate:resolved] Show warning during build if density-specific\nimages are present but anyDensity=\"true\" is not set. \nhttps://github.com/appcelerator/titanium_mobile/commit/9985f8f908c0...
(from [eecd982e9e9df75098ded4415f12be2e0a25a8aa])\n[#1594 state:resolved] Be sure to only try to\nmerge manifest info from tiapp into actual manifest if the tiapp.py\nparser actually found a entry. [#2375\nstate:resolved] Hard-code suppression of the anyDensity warning for\nwhen KitchenSink is running, so as to not freak everybody out. The\ndensity-specific image folder is in KS just to test loading from\nres/drawable. \nhttps://github.com/appcelerator/titanium_mobile/commit/eecd982e9e9d...