[TIMOB-1594] Android: Add Support for Processing AndroidManifest in tiapp.xml
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:56:37.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.5.0 M02 |
| Components | Android |
| Labels | android, feature |
| Reporter | Don Thorp |
| Assignee | Marshall Culpepper |
| Created | 2011-04-15T02:56:55.000+0000 |
| Updated | 2011-04-17T01:56:37.000+0000 |
Description
Allow activity entries to be described in an section of tiapp.xml it will need to work with code generation and build to create the appropriate activity shims to AndroidManifest.xml entries.
(from [d5d94b0af6c3cba8c379e8d9cea20b1ac257f894]) [#1594] Beginnings of android manifest settings in tiapp.xml. Currently supports screen settings, permissions and simple activity declarations (no attributes beyond name). See http://gist.github.com/624357">http://gist.github.com/624357 for sample tiapp.xml. http://github.com/appcelerator/titanium_mobile/commit/d5d94b0af6c3cba8c379e8d9cea20b1ac257f894"> http://github.com/appcelerator/titanium_mobile/commit/d5d94b0af6c3c...
(from [4c057f4b09cf55e8e64d078d5a881623275d4ee1]) [#1594] Support attributes on the activities (still no support for intent filter). Support services. Make the entire supports-screens section in manifest template replaceable by what's in tiapp.xml, and put defaults in the tiapp.xml template -- as well as defaults in the builder.py code in case the section is missing from tiapp.xml, which will occur if app created < 1.5 http://github.com/appcelerator/titanium_mobile/commit/4c057f4b09cf55e8e64d078d5a881623275d4ee1"> http://github.com/appcelerator/titanium_mobile/commit/4c057f4b09cf5...
Pull screens / permissions out of <android>, will go under <android><manifest>, which will go "as-is" into generated manifest.
(from [931e61d2725bb93d3cad6b9fc8ce62a513558167]) [#1594] Move tiapp <android:manifest> to , support (JS-based activities) and generate their entries in AndroidManifest.xml https://github.com/appcelerator/titanium_mobile/commit/931e61d2725bb93d3cad6b9fc8ce62a513558167"> https://github.com/appcelerator/titanium_mobile/commit/931e61d2725b...
(from [9985f8f908c01a722823bec6d4cd34df97c198c1]) [#1594 state:resolved] Map entries from tiapp.xml into the generated AndroidManifest.xml, including any attributes thate are put on to the and elements in tiapp.xml. Differentiate between stuff that's additive (such as entries) versus stuff that needs to replace entries in the manifest because they only appear once (<uses-sdk> and <supports-screens>). [#2375 state:resolved] Show warning during build if density-specific images are present but anyDensity="true" is not set. https://github.com/appcelerator/titanium_mobile/commit/9985f8f908c01a722823bec6d4cd34df97c198c1"> https://github.com/appcelerator/titanium_mobile/commit/9985f8f908c0...
(from [eecd982e9e9df75098ded4415f12be2e0a25a8aa]) [#1594 state:resolved] Be sure to only try to merge manifest info from tiapp into actual manifest if the tiapp.py parser actually found a entry. [#2375 state:resolved] Hard-code suppression of the anyDensity warning for when KitchenSink is running, so as to not freak everybody out. The density-specific image folder is in KS just to test loading from res/drawable. https://github.com/appcelerator/titanium_mobile/commit/eecd982e9e9df75098ded4415f12be2e0a25a8aa"> https://github.com/appcelerator/titanium_mobile/commit/eecd982e9e9d...