Adobe 65036570 User Guide - Page 445

About testing movies to avoid problems

Page 445 highlights

ADOBE DIRECTOR 11.0 434 User Guide Naming sprites makes changes to your script even easier. For example, the following script refers to a sprite by its number: sprite (1).text Instead, use the following script: sprite("input").member.text When you use the marker name to refer to a frame, you can move the marker without breaking the script. The following script refers to a frame by its number: _movie.go(27) It is better to add a marker to the frame and use the marker name, as in the following script: _movie.go("Main_menu") • During work sessions, save your movie file often. Save a copy of the movie after each milestone, such as a day of work or after adding a significant new feature or section. This way, if problems arise, you can easily compare the current version of the file to a slightly older version to locate the source of the problem. Keep several copies of your file at different stages of development in case you need to go back several steps. About testing movies to avoid problems While you develop movies, you might encounter some difficulties because creating interesting movies and trying out new ideas always involves some experimentation. By testing your movies according to the simple guidelines described in this section, you can prevent problems from becoming obstacles: • If the main.dir file is linked to a miaw.dir file, upgrade both the files to Director 11 before playing the movie. • Test early in development to help ensure that you discover any problems while they are still minor. Waiting to test lets small problems become larger ones as you add features to your movie that depend on problematic functionality that was implemented earlier. • Test often during development. Test the functionality of each small part of your movie as you add it rather than waiting until the movie's whole feature set is implemented. This way, you know that the most recently implemented feature is the most likely source of a problem. If you wait to test one feature until after the next feature is implemented and one of those features exhibits a problem, you have a more complex set of possibilities to evaluate. • Test on all target platforms. Decide what the minimum system requirements are for the computers used by your audience. Verify the performance of your movie on the slowest processor that is acceptable. Determine the range of configurations you have to support (such as Mac® OS, Windows® 2000, and Windows XP), and test enough of them to ensure success. Be sure to include parameters such as browser software, screen resolution, and available memory in your testing. This approach helps you find problems that are specific to an operating system or configuration, which are distinct from authoring errors. Testing strategies Use the following to test your movies effectively: • Testing in the Director authoring environment is different from testing in the Director Projector and Shockwave® Player environments for online content. The Preview In Browser command demonstrates the true behavior of the movie in the Shockwave environment.

  • 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
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452
  • 453
  • 454
  • 455
  • 456
  • 457
  • 458
  • 459
  • 460
  • 461
  • 462
  • 463
  • 464
  • 465
  • 466
  • 467
  • 468
  • 469
  • 470
  • 471
  • 472
  • 473
  • 474
  • 475
  • 476
  • 477
  • 478
  • 479
  • 480
  • 481
  • 482
  • 483
  • 484
  • 485
  • 486
  • 487
  • 488
  • 489
  • 490
  • 491
  • 492
  • 493
  • 494
  • 495
  • 496
  • 497
  • 498

ADOBE DIRECTOR 11.0
User Guide
434
Naming sprites makes changes to your script even easier. For example, the following script refers to a sprite by
its number:
sprite (1).text
Instead, use the following script:
sprite("input").member.text
When you use the marker name to refer to a frame, you can move the marker without breaking the script.
The following script refers to a frame by its number:
_movie.go(27)
It is better to add a marker to the frame and use the marker name, as in the following script:
_movie.go("Main_menu")
During work sessions, save your movie file often. Save a copy of the movie after each milestone, such as a day of
work or after adding a significant new feature or section. This way, if problems arise, you can easily compare the
current version of the file to a slightly older version to locate the source of the problem. Keep several copies of your
file at different stages of development in case you need to go back several steps.
About testing movies to avoid problems
While you develop movies, you might encounter some difficulties because creating interesting movies and trying out
new ideas always involves some experimentation. By testing your movies according to the simple guidelines
described in this section, you can prevent problems from becoming obstacles:
If the main.dir file is linked to a miaw.dir file, upgrade both the files to Director 11 before playing the movie.
Test early in development to help ensure that you discover any problems while they are still minor. Waiting to
test lets small problems become larger ones as you add features to your movie that depend on problematic function-
ality that was implemented earlier.
Test often during development. Test the functionality of each small part of your movie as you add it rather than
waiting until the movie’s whole feature set is implemented. This way, you know that the most recently implemented
feature is the most likely source of a problem. If you wait to test one feature until after the next feature is implemented
and one of those features exhibits a problem, you have a more complex set of possibilities to evaluate.
Test on all target platforms. Decide what the minimum system requirements are for the computers used by your
audience. Verify the performance of your movie on the slowest processor that is acceptable. Determine the range of
configurations you have to support (such as Mac® OS, Windows® 2000, and Windows XP), and test enough of them
to ensure success. Be sure to include parameters such as browser software, screen resolution, and available memory
in your testing. This approach helps you find problems that are specific to an operating system or configuration,
which are distinct from authoring errors.
Testing strategies
Use the following to test your movies effectively:
Testing in the Director authoring environment is different from testing in the Director Projector and
Shockwave
®
Player environments for online content. The Preview In Browser command demonstrates the true
behavior of the movie in the Shockwave environment.