If, however, you want to delve a little deeper into the code, there are parts of the book
where you can do just that and learn how to add complex functionality to your designs. If you
want to go further still, we??™ll recommend the best places to get that information.
We??™re happy to have you along for this ride, and we hope you enjoy it and learn a lot from it.
Flex isn??™t just for programmers; it??™s time for designers to take back RIAs, and show what that ???R???
really stands for. The Internet is not just about collecting data; it??™s also about visual communication
and giving people a rich user experience, and that??™s what designers do best.
xv
INTRODUCTION
Layout conventions
To keep this book as clear and easy to follow as possible, the following text conventions are
used throughout.
Important words or concepts are normally highlighted on the first appearance in bold type.
Code is presented in fixed-width font.
New or changed code is normally presented in bold fixed-width font.
Pseudo-code and variable input are written in italic fixed-width font.
Menu commands are written in the form Menu ?¤ Submenu ?¤ Submenu.
Where I want to draw your attention to something, I??™ve highlighted it like this:
Sometimes code won??™t fit on a single line in a book. Where this happens, I use an arrow like this: ??.
This is a very, very long section of code that should be written all ??
on the same line without a break.
Ahem, don??™t say I didn??™t warn you.
Pages:
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