Adobe 65011817 Extended User Guide - Page 313

MXML Export

Page 313 highlights

Last updated 12/8/2009 EXTENDING FIREWORKS 309 Rich symbols Attributes text.autoExpand text.italic text.underline text.bold text.justify text.font text.fontsize text.alignment Type boolean boolean boolean boolean string string integer string MXML Export The Flex application framework consists of MXML, ActionScript 3.0, and the Flex class library. Developers use MXML to declaratively define the application user interface elements and use ActionScript for client logic and procedural control. Developers write MXML and ActionScript source code using the Adobe Flex Builder™ IDE or a standard text editor. MXML is the XML-based language that developers use to lay out components in Flex applications. It provides a declarative approach to controlling an application's visual appearance. Using MXML, developers can position components and specify constraints to enable a more "liquid" user interface. Developers can also use View States and Transitions to control how the application should respond to different user actions and application events. Using Fireworks, you can export Flex code (MXML) in order to easily create a Flex application layout in Fireworks, leveraging Flex common library assets, and export it as MXML for loading into Flex Builder. To export MXML data 1 Choose File > Export. 2 Choose MXML and Images in the Export pop-up menu. 3 Select the Put images in subfolder option if you want to save the images in a separate folder from the MXML code. 4 Select the Current page only option to export only the currently selected page. 5 Click Save to complete the export. Flex Component Definitions for MXML and Images Export When exporting a Fireworks document with the MXML and Image export, Fireworks checks each element's customData property for definitions that dictate how that element should appear in the resulting MXML. If no MXML-related definitions are found, the element is exported as an image. Each Flex component found in the Fireworks common library already has unique customData definitions that allow it to be exported as MXML. If you wish to have elements within your document export as their own custom MXML tags you can do so with the following customData definitions. flexClassName Flex component symbols are associated as being Flex Components by the MXML and Images import through a customData property called flexClassName.

  • 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
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336

309
EXTENDING FIREWORKS
Rich symbols
Las
t
up
d
a
ted
12/8/2009
MXML Export
The Flex application framework consists of MXML, ActionScript 3.0, and the Flex class library. Developers use MXML
to declaratively define the application user interface elements and use ActionScript for client logic and procedural
control. Developers write MXML and ActionScript source code using the Adobe Flex Builder™ IDE or a standard text
editor.
MXML is the XML-based language that developers use to lay out components in Flex applications. It provides a
declarative approach to controlling an application's visual appearance. Using MXML, developers can position
components and specify constraints to enable a more “liquid” user interface. Developers can also use View States and
Transitions to control how the application should respond to different user actions and application events.
Using Fireworks, you can export Flex code (MXML) in order to easily create a Flex application layout in Fireworks,
leveraging Flex common library assets, and export it as MXML for loading into Flex Builder.
To export MXML data
1
Choose File > Export.
2
Choose MXML and Images in the Export pop-up menu.
3
Select the Put images in subfolder option if you want to save the images in a separate folder from the MXML code.
4
Select the Current page only option to export only the currently selected page.
5
Click Save to complete the export.
Flex Component Definitions for MXML and Images Export
When exporting a Fireworks document with the MXML and Image export, Fireworks checks each element’s
customData
property for definitions that dictate how that element should appear in the resulting MXML. If no
MXML-related definitions are found, the element is exported as an image. Each Flex component found in the
Fireworks common library already has unique
customData
definitions that allow it to be exported as MXML. If you
wish to have elements within your document export as their own custom MXML tags you can do so with the following
customData
definitions.
flexClassName
Flex component symbols are associated as being Flex Components by the MXML and Images import through a
customData
property called
flexClassName
.
text.autoExpand
boolean
text.italic
boolean
text.underline
boolean
text.bold
boolean
text.justify
string
text.font
string
text.fontsize
integer
text.alignment
string
Attributes
Type