{
	"id": "94004",
	"key": "ALOY-80",
	"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": [
			{
				"id": "14036",
				"description": "2012 Sprint 14",
				"name": "2012 Sprint 14",
				"archived": true,
				"released": true,
				"releaseDate": "2012-07-19"
			}
		],
		"resolution": {
			"id": "1",
			"description": "A fix for this issue is checked into the tree and tested.",
			"name": "Fixed"
		},
		"resolutiondate": "2012-07-19T11:52:03.000+0000",
		"created": "2012-06-27T12:26:23.000+0000",
		"priority": {
			"name": "High",
			"id": "2"
		},
		"labels": [],
		"versions": [
			{
				"id": "14036",
				"description": "2012 Sprint 14",
				"name": "2012 Sprint 14",
				"archived": true,
				"released": true,
				"releaseDate": "2012-07-19"
			}
		],
		"issuelinks": [],
		"assignee": {
			"name": "tlukasavage",
			"key": "tlukasavage",
			"displayName": "Tony Lukasavage",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"updated": "2014-06-22T13:21:21.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": "12326",
				"name": "XML",
				"description": "View XML and parsing"
			}
		],
		"description": "h2. Description\r\n\r\nRight now, the markup syntax for {{Ti.UI.iPad.SplitWindow}} assumes that it has 2 children, and that each is a {{Ti.UI.Window}}. It also assumes that the first window is the {{masterView}} and that the second is the {{detailView}}. While this convention over configuration may fit for this component, I wanted to throw out a few alternatives to see what others think.\r\n\r\nh2. Alternatives\r\n\r\nh4. Add custom attribute to child windows\r\n{code:xml}\r\n<SplitWindow ns=\"Ti.UI.iPad\">\r\n    <Window split=\"master\"/>\r\n    <Window split=\"detail\"/>\r\n</SplitWindow>\r\n{code}\r\n\r\nh4. Enforce IDs of master and detail (I don't like this one, but it's a possibility)\r\n{code:xml}\r\n<SplitWindow ns=\"Ti.UI.iPad\">\r\n    <Window id=\"master\"/>\r\n    <Window id=\"detail\"/>\r\n</SplitWindow>\r\n{code}\r\n\r\nh4. Check class for master and detail\r\n{code:xml}\r\n<SplitWindow ns=\"Ti.UI.iPad\">\r\n    <Window class=\"master otherclass\"/>\r\n    <Window class=\"detail\"/>\r\n</SplitWindow>\r\n{code}\r\n\r\nh4. Use an entirely new markup\r\n{code:xml}\r\n<SplitWindow ns=\"Ti.UI.iPad\">\r\n    <Master>\r\n        <!-- Implicitly creates a window, so you can put any markup in here ->\r\n    </Master>\r\n    <Detail></Detail>\r\n</SplitWindow>\r\n{code}\r\n\r\nh2. Thoughts?\r\n\r\nI kinda like the entirely new markup, cause its clear what's going and you don't need to explicitly list the Window. Though perhaps it is overkill for a component that has a pretty specific configuration. Anyone else?",
		"attachment": [],
		"flagged": false,
		"summary": "Establish Ti.UI.iPad.SplitWindow markup syntax",
		"creator": {
			"name": "tlukasavage",
			"key": "tlukasavage",
			"displayName": "Tony Lukasavage",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"subtasks": [],
		"reporter": {
			"name": "tlukasavage",
			"key": "tlukasavage",
			"displayName": "Tony Lukasavage",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"environment": null,
		"comment": {
			"comments": [
				{
					"id": "201038",
					"author": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "We can revisit later if necessary",
					"updateAuthor": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2012-07-02T05:52:53.000+0000",
					"updated": "2012-07-02T05:52:53.000+0000"
				},
				{
					"id": "207927",
					"author": {
						"name": "rmcmahon",
						"key": "rmcmahon",
						"displayName": "Russell McMahon",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "I like the new markup. I sent the ticket to Rick for his feedback.",
					"updateAuthor": {
						"name": "rmcmahon",
						"key": "rmcmahon",
						"displayName": "Russell McMahon",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2012-07-16T17:40:14.000+0000",
					"updated": "2012-07-16T17:40:14.000+0000"
				},
				{
					"id": "208185",
					"author": {
						"name": "rmcmahon",
						"key": "rmcmahon",
						"displayName": "Russell McMahon",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Added on behalf of Rick Blalock...\r\n\r\n\"I don't have much of an opinion on this.  The only one I didn't like was the one where the window had an attribute called \"split\".  All the other ones made enough sense to me and are basically the same from my POV.  From an engineering POV there might be a downside to having it's own custom tag but I can't think of what that would be off the top of my head.\r\n\r\nI assume in examples #2 and #3 you could make the window wrap other markup too.\r\n\r\nEither way, most of those look good to me.\"",
					"updateAuthor": {
						"name": "rmcmahon",
						"key": "rmcmahon",
						"displayName": "Russell McMahon",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2012-07-17T15:30:42.000+0000",
					"updated": "2012-07-17T15:30:42.000+0000"
				},
				{
					"id": "208186",
					"author": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "FYI, this is currently implemented simply as the first window in the hierarchy being the master, the second is the detail.",
					"updateAuthor": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2012-07-17T15:32:25.000+0000",
					"updated": "2012-07-17T15:32:25.000+0000"
				}
			],
			"maxResults": 4,
			"total": 4,
			"startAt": 0
		}
	}
}