Adobe 38039927 Extended User Guide - Page 261

Cross-Product Extensions

Page 261 highlights

257 Chapter 7: Cross-Product Extensions Cross-product extensions include any Fireworks-related extensions developed for, or in, another Adobe application. These cross-product extensions include those written for other tools, such as Adobe Dreamweaver that use existing Fireworks functionality. They may use JavaScript APIs for adding image-editing functionality to those applications as well as custom Fireworks panels developed in Adobe Flash to enhance the functionality of Fireworks. For example, a developer may want to create an ActionScript command so that a user can replace text in an image without leaving the current movie. Similarly, a Flash developer may create a panel so that a Fireworks user can easily create spirals and other nonstandard shapes repeatedly. Cross-product architecture The Fireworks cross-product communication architecture provides a new way for extension developers to create Fireworks-related features for other applications. With this new architecture, your extensions allow a user to perform common image-editing operations (cropping, rotating, adjusting color, blurring, and almost all Fireworks operations) without leaving the current application or opening Fireworks. XML and remote procedure calls Applications written with Flash ActionScript 2.0 or C++ applications can control Fireworks by sending JavaScript instructions, called remote procedure calls (RPC), encoded in XML through a local socket. The Fireworks RPC gives other applications access to functionality previously restricted to JavaScript programs running inside Fireworks. The RPC mechanism exposes the Fireworks JavaScript DOM through XML and a TCP socket connection. In this way, an application (written with ActionScript 2.0 or C++) running on the same computer as Fireworks (only local connections are allowed to the loopback address) can be used to open Fireworks documents, slice them, optimize them, and then export them. Users can also create a new Fireworks document through another application, draw in the document, and preview it in the browser. Nearly anything that can be accomplished with a JavaScript program running in Fireworks can now be done through remote procedure calls. Note: Fireworks excludes functionality related to starting other applications or manipulating non-Fireworks related files (for more information, see "Security" on page 110).

  • 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

257
Chapter 7: Cross-Product Extensions
Cross-product extensions include any Fireworks-related extensions developed for, or in, another Adobe appli-
cation. These cross-product extensions include those written for other tools, such as Adobe Dreamweaver that use
existing Fireworks functionality. They may use JavaScript APIs for adding image-editing functionality to those
applications as well as custom Fireworks panels developed in Adobe Flash to enhance the functionality of Fireworks.
For example, a developer may want to create an ActionScript command so that a user can replace text in an image
without leaving the current movie. Similarly, a Flash developer may create a panel so that a Fireworks user can easily
create spirals and other nonstandard shapes repeatedly.
Cross-product architecture
The Fireworks cross-product communication architecture provides a new way for extension developers to create
Fireworks-related features for other applications. With this new architecture, your extensions allow a user to
perform common image-editing operations (cropping, rotating, adjusting color, blurring, and almost all Fireworks
operations) without leaving the current application or opening Fireworks.
XML and remote procedure calls
Applications written with Flash ActionScript 2.0 or C++ applications can control Fireworks by sending JavaScript
instructions, called
remote procedure calls
(RPC), encoded in XML through a local socket. The Fireworks RPC gives
other applications access to functionality previously restricted to JavaScript programs running inside Fireworks.
The RPC mechanism exposes the Fireworks JavaScript DOM through XML and a TCP socket connection. In this
way, an application (written with ActionScript 2.0 or C++) running on the same computer as Fireworks (only local
connections are allowed to the loopback address) can be used to open Fireworks documents, slice them, optimize
them, and then export them. Users can also create a new Fireworks document through another application, draw in
the document, and preview it in the browser. Nearly anything that can be accomplished with a JavaScript program
running in Fireworks can now be done through remote procedure calls.
Note:
Fireworks excludes functionality related to starting other applications or manipulating non-Fireworks related
files (for more information, see “Security” on page 110).