{ "id": "63991", "key": "TIMOB-3359", "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": "11244", "name": "Release 1.7.0", "archived": true, "released": true, "releaseDate": "2011-06-13" }, { "id": "11246", "name": "Sprint 2011-11", "archived": true, "released": true, "releaseDate": "2011-03-21" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T02:01:32.000+0000", "created": "2011-04-15T03:43:11.000+0000", "priority": { "name": "Trivial", "id": "5" }, "labels": [ "android", "feature", "release-1.7.0" ], "versions": [], "issuelinks": [], "assignee": { "name": "billdawson", "key": "billdawson", "displayName": "Bill Dawson", "active": true, "timeZone": "Europe/Berlin" }, "updated": "2011-04-17T02:01:32.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}
Since our base Android api level is now 7 (Android 2.1) and that\nversion supports the \"anyDensity=\"true\"\" configuration by default,\ntake out our template AndroidManifest.xml's supports-screens\nsection because it's setting anyDensity to false, which is no\nlonger in line with Android defaults. We should mimic android\ndefaults.
And remove the builder.py warning about having density-specific\nimages in the app's Resources/images/android folder but not setting\nanyDensity to true, since now anyDensity is true by default.
To test this, create a new project and use this as the\napp.js:
\n\nTitanium.UI.setBackgroundColor('#000');\nvar win = Titanium.UI.createWindow({ \n title:'Test',\n backgroundColor:'#000',\n exitOnClose: true\n});\n\nvar iv = Ti.UI.createImageView({\n image:\"images/density.png\"\n});\nwin.add(iv);\n\n\nwin.open();
\n
\nTake the attached image_files.zip and expand it in the\nResources/android/images folder. So the result will be that you\nwill have these files available:\nResources/android/images/high/density.png
and\nResources/android/images/medium/density.png
.
When you run the application with the WVGA800 emulator, you\nshould see the high density image (the image itself has text on it\nthat identifies itself.) When you run the app in the HVGA emulator,\nyou should see the medium density image.
(from [e37329357f99ebcbe657b01345b815c58561f3b1])\nRemove supports-screens from template AndroidManifest.xml so as to\naccept Android 2.1 defaults [#3359] \nhttps://github.com/appcelerator/titanium_mobile/commit/e37329357f99...
(from [630a27665a2e04da763ae85849469af7249e59fc])\nKitchenSink not ready for high density, so give it a\nanyDensity=false in the android section of its tiapp.xml. [#3359]\n\nhttps://github.com/appcelerator/titanium_mobile/commit/630a27665a2e...
Tested with Titanium SDK version: 1.7.0 (03/17/11 10:02 630a276)\non
\nEmulator API 2.1 WVGA800 - High
\nEmulator API 2.2 WVGA800 - High
\nEmulator API 2.1 HVGA - Medium
\nNexus S 2.3.2 - High