Titanium

[ALOY-383] inViewHierarchy markup attribute

GitHub Issuen/a
TypeNew Feature
PriorityHigh
StatusClosed
ResolutionWon't Fix
Resolution Date2012-12-07T14:52:01.000+0000
Affected Version/sAlloy 0.3.1
Fix Version/sAlloy 0.3.4, 2012 Sprint 25
ComponentsXML
Labelsn/a
ReporterTony Lukasavage
AssigneeTony Lukasavage
Created2012-11-14T02:46:41.000+0000
Updated2014-01-28T23:18:07.000+0000

Description

We should add an *inViewHierarchy* attribute to the XML markup, that when set to false, would indicate that the view is not to be added to the view hierarchy by Alloy. This would be useful in the case of markup for dialogs, or in the case of special properties that rely on references to titanium proxies. Properties like rightNavButton, leftNavButton, searchbar, etc... More details on these properties can be found in ALOY-382.

Comments

  1. Fokke Zandbergen 2012-12-07
  2. Tony Lukasavage 2012-12-07 @Fokke, you make a good point that by simply adding the views under that they are automatically not in the view hierarchy. I wanted to have the inViewHierarchy attribute to allow structuring as in ALOY-382, but perhaps abiding by the XML view hierarchy convention would be a bit "purer".
  3. Tony Lukasavage 2012-12-07 Let's continue without it, using the modified structure in ALOY-382. This can be revisited if there ever is an additional need that can not be handled by simply making the UI components a child of

JSON Source