Adobe 12040118 Using Help - Page 207

JavaScript UI example

Page 207 highlights

Adobe After Effects Help Using Help Creating User Interface Elements Back 207 Guidelines for creating and using modal dialogs When your script creates a dialog, you typically create controls that the user must interact with in order to enter values that your script will use. In general, you can minimize the number of event callback functions you attach to various controls in your dialogs, unless interaction with those controls changes the operation of the dialog itself. In most cases where you simply want to read the states of various controls when the dialog is dismissed, you do not need to handle events for them. For instance, you often don't need onClick() functions for every checkbox and radiobutton in your dialog: when the dialog is dismissed, read their states using their value properties. Some exceptions to this guideline: • onChange() functions are needed for edittext elements, if users enter values which must be validated (like a number within a range). The event callback must perform any necessary validation, and interact with the user on errors. • Define onClick() for OK and Cancel buttons which close the dialog with a given value. Note: Perform this function only if you have not defined the defaultElement and/or cancelElement properties or named these buttons in such a way that they will automatically be identified as the OK and Cancel buttons. Prompts and Alerts Some JavaScript environments provide functions on the global window object to display message boxes or alert boxes and a prompt box that displays one or two lines of text and then allows the user to enter one line of text. The scripting user interface defines functions alert(), confirm() and prompt() on the Window class that provides this standard functionality. The host application controls the appearance of these simple dialog boxes, so they are consistent with other alert and message boxes displayed by the application. See the "JavaScript UI reference" on page 213 for details. JavaScript UI example Having explored the individual scripting components that make up the user interface, you are now ready to see the parts assembled into real-world JavaScript code that produces a fully functional user interface. The JavaScript UI code sample described below includes the following functions, which creates a simple user interface builder window populated with various panels, checkboxes, buttons and controls. When you run the builder, you can then cause it to create an Alert Box. • createBuilderDialog() -- Creates an empty dialog window near the upper left of the screen and adds a title panel, a checkbox, a control panel and a panel with buttons to test parameters and create the Alert Box specification. • initializeBuilder() --Sets up initial control states and attaches event callback functions to controls. • runBuilder() -- Runs the builder dialog and returns the resulting Alert Box UI • createResource() -- Creates and returns a string containing a dialog resource specification that creates the Alert Box UI using the parameters entered • stringProperty() -- Returns a formatted string • arrayProperty() -- Returns a formatted array • createTestDialog() -- Creates a new Test dialog These functions are bundled together into a Main script, which assembles the final Alert Box dialog. Using Help Back 207

  • 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

U
sing H
elp
B
ack
207
Adobe After Effects Help
Creating User Interface Elements
U
sing H
elp
B
ack
207
Guidelines for creating and using modal dialogs
When your script creates a dialog, you typically create controls that the user must interact with in order to
enter values that your script will use. In general, you can minimize the number of event callback functions you
attach to various controls in your dialogs, unless interaction with those controls changes the operation of the
dialog itself. In most cases where you simply want to read the states of various controls when the dialog is
dismissed, you do not need to handle events for them. For instance, you often don’t need
onClick()
functions
for every
checkbox
and
radiobutton
in your dialog: when the dialog is dismissed, read their states using their
value
properties.
Some exceptions to this guideline:
onChange()
functions are needed for
edittext
elements, if users enter values which must be validated (like a
number within a range). The event callback must perform any necessary validation, and interact with the
user on errors.
Define
onClick()
for OK and Cancel buttons which close the dialog with a given value.
Note
: Perform this function only if you have
not
defined the defaultElement and/or cancelElement properties
or
named these buttons in such a way that they will automatically be identified as the OK and Cancel buttons.
Prompts and Alerts
Some JavaScript environments provide functions on the global window object to display message boxes or
alert boxes and a prompt box that displays one or two lines of text and then allows the user to enter one line
of text.
The scripting user interface defines functions
alert(), confirm()
and
prompt()
on the
Window
class that
provides this standard functionality. The host application controls the appearance of these simple dialog
boxes, so they are consistent with other alert and message boxes displayed by the application. See the “JavaS-
cript UI reference” on page 213 for details.
JavaScript UI example
Having explored the individual scripting components that make up the user interface, you are now ready to
see the parts assembled into real-world JavaScript code that produces a fully functional user interface.
The JavaScript UI code sample described below includes the following functions, which creates a simple user
interface builder window populated with various panels, checkboxes, buttons and controls. When you run the
builder, you can then cause it to create an Alert Box.
createBuilderDialog()
-- Creates an empty dialog window near the upper left of the screen and adds a title
panel, a checkbox, a control panel and a panel with buttons to test parameters and create the Alert Box
specification.
initializeBuilder() --
Sets up initial control states and attaches event callback functions to controls.
runBuilder()
-- Runs the builder dialog and returns the resulting Alert Box UI
createResource()
-- Creates and returns a string containing a dialog resource specification that creates the
Alert Box UI using the parameters entered
stringProperty()
-- Returns a formatted string
arrayProperty()
-- Returns a formatted array
createTestDialog()
-- Creates a new Test dialog
These functions are bundled together into a Main script, which assembles the final Alert Box dialog.