[ALOY-306] Abstract types in markup do not currently support platform, formFactor, or inline event attributes
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2012-10-12T20:53:34.000+0000 |
| Affected Version/s | 2012 Sprint 20 |
| Fix Version/s | Alloy 0.3.1, 2012 Sprint 21 |
| Components | XML |
| Labels | notable |
| Reporter | Tony Lukasavage |
| Assignee | Unknown |
| Created | 2012-09-27T20:43:36.000+0000 |
| Updated | 2018-03-07T22:26:04.000+0000 |
Description
For the following components, the code for their abstract types are generated directly in the parser, not in the generateNode() function. While this ensures that these abstract types can only be used inside of the appropriate tags, it misses the preprocessing done in generateNode(), which makes conditional determinations based on platform, formFactor, and also handles inline markup eventing.
* Ti.UI.ButtonBar
* Ti.UI.iOS.CoverFlowView
* Ti.UI.iOS.Tabbedbar
* Ti.UI.iOS.Toolbar
We need to see if there is a reasonable way to still enforce that the abstract types for these components only occur in these components, but also allow them the full processing that generateNode() provides. Separate parsers may need to be written for all abstract types as well.
No comments