[ALOY-585] ListView XML markup integration
GitHub Issue | n/a |
---|---|
Type | New Feature |
Priority | Critical |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2013-05-01T16:59:20.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Alloy 1.2.0, 2013 Sprint 09 |
Components | Runtime, XML |
Labels | notable, qe-testadded |
Reporter | Tony Lukasavage |
Assignee | Tony Lukasavage |
Created | 2013-03-25T14:35:05.000+0000 |
Updated | 2013-07-17T00:44:13.000+0000 |
Description
While the new Ti.UI.ListView UI component can be used in Alloy like this:
<Alloy>
<Window>
<ListView id="list"/>
</Window>
</Alloy>
but this forces me to put all the necessary ListView UI creation in my JS controller code. This is only one step removed essentially from coding the whole thing traditionally. We need to actually create markup integration for the ListView and its templates to allow developers to define them much more easily.
Proposed syntax will be forthcoming as more research is done on the ListView component itself. References being used to learn about the ListView are:
* [KitchenSink ListView samples](https://github.com/appcelerator-developer-relations/KitchenSink/tree/master/Resources/ui/common/baseui/listview)
* [ListView spec on the wiki](https://wiki.appcelerator.org/display/community/Titanium+ListView+Specification)
* [YAML spec](https://gist.github.com/bryan-m-hughes/4677555)
Additional considerations:
* Data binding will need to be implemented
* Many parsers will likely need to be written as ListView makes use of non-View object literals for templates and sections. Since these are not standard Titanium components, they will require extra effort to parse.
* Must work for both Android and iOS. Alloy's generated code will undoubtedly surface parity issues between the two so time for logging issues back to TIMOB needs to be accounted for.
No comments