[ALOY-714] Shorthand for some proxy properties (i.e., <RightNavButton>)
GitHub Issue | n/a |
---|---|
Type | New Feature |
Priority | Low |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2014-02-26T19:39:40.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Alloy 1.4.0, 2014 Sprint 04 |
Components | XML |
Labels | notable, qe-testadded |
Reporter | Tony Lukasavage |
Assignee | Tim Poulsen |
Created | 2013-06-19T14:40:45.000+0000 |
Updated | 2014-05-30T15:24:21.000+0000 |
Description
Currently to use certain proxy properties in markup, like , the element itself is used only as a container for the actual element to be rendered. For example, to show a button, you'd need to do this:
<RightNavButton>
<Button title="press me"/>
</RightNavButton>
but it would be easier to render it as a button if you don't have any child elements:
<RightNavButton title="press me"/>
This is just one example. We need to investigate the current list of proxy properties and see which can also be treated in a similar manner.
Components with leftNavButton / rightNavButton proxy properties that accept arbitrary Views: * leftNavButton / rightNavButton -- Window, SplitWindow, Popover Map annotations have leftButton and leftView properties (and corresponding right button/view), which serve a similar purpose though they're not implemented with a single proxy property in the same way. Though, those properties are mutually exclusive -- you have have a button or view, not both. So perhaps Alloy shorthands could be applied to them in the same way.
PR: https://github.com/appcelerator/alloy/pull/336 Test app: test/apps/testing/ALOY-714 Functional test: 1. Build the app for iOS 2. The navigation bar in the resulting app should have left & right navigation buttons. The left was created with standard markup, the right with the
Verified working as expected on iPhone 5 7.1 TiSDK 3.3.0.v20140429122517 Alloy 1.4.0-dev CLI 1.4.0-dev Appcelerator Studio 3.3.0.201404291930 Closing