[ALOY-77] Support per-component tag parsing for complex relationships
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2012-07-19T11:52:06.000+0000 |
| Affected Version/s | 2012 Sprint 14 |
| Fix Version/s | 2012 Sprint 14 |
| Components | XML |
| Labels | n/a |
| Reporter | Tony Lukasavage |
| Assignee | Tony Lukasavage |
| Created | 2012-06-27T11:41:46.000+0000 |
| Updated | 2014-02-04T00:34:41.000+0000 |
Description
We will need to probably build out a system by which we can do various combinations of XML from View markup.
For example, in Ti, we have certain parent/child relationships to certain objects which need to be mapped so that its more helpful in XML.
Example is a map. Ideally, you would do something like:
<map>
<annotation></annotation>
</map>
As a way to statically build a map with a single annotation.
Also, in the tableview, you have a similar scenario but with additional nesting possibilities:
<tableview>
<tableviewrow>
<imageview url="foo.png" />
</tableviewrow>
</tableview>
Also, as in the map above, we need to also be smart about Ti builtins to make sure we auto-prefix the ns (Ti.Map vs. Ti.UI) in these cases.
Tag-specific parsers can now be written in the
Alloy/commands/compile/parsers