There are two ways of looking at the application that is laid out in MXML. Figure 1-8
shows how the Panel component looks in the Design view.
5. If you switch to the Source view (see Figure 1-9), you can see the underlying code that is created
for the application.
Figure 1-9. Moving from Design to
Source view
You can see this code in Figure 1-10. The code??™s structure is similar to XML because MXML is an XMLbased
language, and you use the MXML code to lay out user-interface components for your applications.
The first line defines the version of XML used. The second line defines the application, and it is
inside these application tags that we place our components. You can see that within the application tags
we now have the tags for the Panel component that we created in the Design view. The Panel tags start
with
, which contains the properties of the component, and end with . So
far, the properties are the default size and location that occurred when we created the component. You
may also have noticed that the interface changed when we made the transition to Source view. This is
because working within the Source view is significantly different than working in the Design view. We
9
INTRODUCING FLEX AND FLEX BUILDER 3
no longer have the Components panel visible. This is because in the Source view, you can write the components
in directly by typing the MXML tags. Similarly, the Properties panel also disappears because we
can write the properties directly into the tags.
Pages:
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