This document is a cache from http://help.adobe.com/en_US/flex/mobileapps/developing_mobile_apps_flex.pdf

Developing Mobile Applications with Flex and Flash Builder

Document source : help.adobe.com

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 All Pages

DEVELOPING MOBILE APPLICATIONS WITH FLEX AND FLASH BUILDER

User interface and layout

Last updated 9/8/2011

Each view in an application corresponds to a View container defined in an ActionScript or MXML file. Each View
contains a

data

property that specifies the data associated with that view. Views can use the

data

property to pass

information to each other as the user navigates the application.

Use the

ViewNavigatorApplication.firstView

property to specify the file that defines the first view in the

application. In the previous application, the

firstView

property specifies

views.HomeView

. The following example

shows the HomeView.mxml file that defines that view:

<?xml version="1.0" encoding="utf-8"?>

<s:View xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
title="Home">
<s:layout>
<s:VerticalLayout paddingTop="10"/>
</s:layout>
<s:Label text="The home screen"/>
</s:View>

Blogger David Hassoun blogged about

ViewNavigator basics

Lay out a mobile application with multiple sections

A mobile application can collect related views in different sections of the application. For example, the following figure
shows the organization of a mobile application with three sections.

Any section can use any View. That is, a view does not belong to a specific section. The section just defines a way to
arrange and navigate a collection of views. In the figure, the Search view is part of every section of the application.

At runtime, only one view is active and resident in memory. For more information, see "

Navigate the views of a mobile

application

" on page 27.

Classes used in a mobile application with multiple sections

The following table lists the classes that you use to create a mobile application with multiple sections:

Main application (TabbedViewNavigatorApplication)

Contacts (ViewNavigator)

Edit Contacts (View)

Contacts Home (View)

Search (View)

Email (ViewNavigator)