{
	"id": "101656",
	"key": "ALOY-290",
	"fields": {
		"issuetype": {
			"id": "4",
			"description": "An improvement or enhancement to an existing feature or task.",
			"name": "Improvement",
			"subtask": false
		},
		"project": {
			"id": "11113",
			"key": "ALOY",
			"name": "Alloy",
			"projectCategory": {
				"id": "10400",
				"description": "Tools for developing applications",
				"name": "Tooling"
			}
		},
		"fixVersions": [],
		"resolution": {
			"id": "3",
			"description": "The problem is a duplicate of an existing issue.",
			"name": "Duplicate"
		},
		"resolutiondate": "2013-11-07T13:24:24.000+0000",
		"created": "2012-09-21T06:57:03.000+0000",
		"priority": {
			"name": "Medium",
			"id": "3"
		},
		"labels": [
			"android",
			"density",
			"resources",
			"screen"
		],
		"versions": [
			{
				"id": "14171",
				"description": "",
				"name": "2012 Sprint 19",
				"archived": true,
				"released": true,
				"releaseDate": "2012-09-24"
			}
		],
		"issuelinks": [],
		"assignee": {
			"name": "tlukasavage",
			"key": "tlukasavage",
			"displayName": "Tony Lukasavage",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"updated": "2014-01-28T23:28:53.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": "12332",
				"name": "Titanium SDK",
				"description": "Any integration or issues with the TiSDK"
			}
		],
		"description": "At the @0.2.34 version we found the platform specific folders for views/styles/controllers and with the formFactor attribute we can develop thinking in specific platform (handheld or tablet). But the Android Platform has 4 groups of screen (LDPI, MDPI, HDPI and XHDPI) and it's a bit hard to build different views for different screen density.\r\n\r\nLike @tonylukasavage says, The purpouse of this Issue: be able to use alloy views/controllers/styles not only based on platform, but also in the case of android, based on screen density. Such as the image attached (Screen Shot 2012-09-21 at 8.47.27 AM.png).\r\n\r\nIt will help us to build apps more flexible for each platform and screen density (in the case of Android). One example for this use:\r\n\r\nFor LDPI Android screens, we can build screens more focused on the base application task only (in my case an app for soccer lovers) and split the features in other screens/actions, but with HDPI we can use the large height screen and shows more information about the team, players, use images with more details and bigger!",
		"attachment": [
			{
				"id": "31603",
				"filename": "Screen Shot 2012-09-21 at 8.47.27 AM.png",
				"author": {
					"name": "vinicius.rj",
					"key": "vinicius.rj",
					"displayName": "Vinicius Souza",
					"active": true,
					"timeZone": "America/Los_Angeles"
				},
				"created": "2012-09-21T06:57:03.000+0000",
				"size": 16927,
				"mimeType": "image/png"
			}
		],
		"flagged": false,
		"summary": "Android Screen Density based resourses",
		"creator": {
			"name": "vinicius.rj",
			"key": "vinicius.rj",
			"displayName": "Vinicius Souza",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"subtasks": [],
		"reporter": {
			"name": "vinicius.rj",
			"key": "vinicius.rj",
			"displayName": "Vinicius Souza",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"environment": "Android",
		"comment": {
			"comments": [
				{
					"id": "230832",
					"author": {
						"name": "rblalock",
						"key": "rblalock",
						"displayName": "Rick Blalock",
						"active": false,
						"timeZone": "America/Havana"
					},
					"body": "It would be nice to have this more fragment-based as well.  For instance, I wouldn't necessarily want to have a completely separate view for different densities...but I might want to have different views inside:\n\n<Alloy>\n   <Require id=\"someView\" src=\"someView\" density=\"HDPI\" />\n</Alloy>\n\nLikewise, having the flexibility for something in TSS makes sense too:\n\n\"#myView[density=HDPI]\": {\n\n}\n\nA shortcut for the density in the Alloy namespace makes sense as well (I know it's easy to get in the Ti API's but it makes sense to cache that for Android and access via Alloy).",
					"updateAuthor": {
						"name": "rblalock",
						"key": "rblalock",
						"displayName": "Rick Blalock",
						"active": false,
						"timeZone": "America/Havana"
					},
					"created": "2012-12-11T16:29:40.000+0000",
					"updated": "2012-12-11T16:29:40.000+0000"
				},
				{
					"id": "230834",
					"author": {
						"name": "vinicius.rj",
						"key": "vinicius.rj",
						"displayName": "Vinicius Souza",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "@Rick Blalock, your solution sounds good and more looks more simple to implement by TI-ALLOY Dev Team. I'm finishing my iOS UI versions of my app and i'm ready to start my Android UI. This density attribute'll help me save lot of time of coding...",
					"updateAuthor": {
						"name": "vinicius.rj",
						"key": "vinicius.rj",
						"displayName": "Vinicius Souza",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2012-12-11T16:38:12.000+0000",
					"updated": "2012-12-11T16:38:12.000+0000"
				},
				{
					"id": "278626",
					"author": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "This will be handled in ALOY-871",
					"updateAuthor": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-11-07T13:24:24.000+0000",
					"updated": "2013-11-07T13:24:24.000+0000"
				}
			],
			"maxResults": 3,
			"total": 3,
			"startAt": 0
		}
	}
}