Adobe 65011817 Extended User Guide - Page 287

Object IDs

Page 287 highlights

Last updated 12/8/2009 EXTENDING FIREWORKS 283 Cross-Product Extensions • The set operation sets the object properties. The set operation can contain only the obj and name attributes and exactly one parameter. The parameter must be the same data type as the data type of the property being set, or Fireworks will return an error. In the following example, the client sets the property of "name" (a string providing a directory path) to the value file://hd/foo/stuff: • The func operation calls a method that operates on the specified object. The number and type of parameters vary according to the method called by the func operation. In the following example, the client calls the undo method to operate on the object with object ID 1: • The release operation informs the server that the client has finished working on the specified object. A release request must specify only an obj attribute and no subelements. In the following example, the client tells the server that it is has finished working on the object with ID 1: Note: Each type of request requires an obj attribute, and all but the release request require a name attribute. Requests can be only of types get, set, func, or release. The RPC server rejects all other types. Object IDs RPC clients reference objects on the server by their object IDs. Because all functionality is exposed by means of objects, every client request must contain a valid object ID. When an object that can be accessed through RPC is created, it is assigned a unique object ID. The object retains that ID for its entire lifetime. This happens for all RPC server objects, whether they are created directly by an RPC call or by an internal Fireworks function. The object IDs can be reused after the corresponding object is destroyed. Note: The object ID number should be treated as a string data type that could contain non-numbers, (do not treat the object ID as an integer data type). Fireworks has the following four reserved object IDs: • "0" This is the Invalid Object ID, used for nonexistent or invalid objects. It is not frequently used for the RPC client, but it is used in several places for the RPC server. "fw" is the Fireworks Application Object ID. The Fireworks Application Object ID references the main application object in Fireworks and is of the Fireworks class. This object is used to open and create documents. In JavaScript, it is the object referenced by App or fw. "smartShape" is the SmartShape Object ID. This object id references the global JavaScript variable smartShape and is used to create an manipulate Auto Shapes. "Document" is the Fireworks Document Compatibility Object ID (it is deprecated, like its JavaScript counterpart). It was used in Fireworks 2 for cleaning up file paths, and is included here only for completeness. "Errors" is the Fireworks Errors Object ID, used mainly for reporting and determining when errors occur in Fireworks. Its JavaScript counterpart is Errors. All other object IDs are generated when the object is created, and may or may not have the same IDs between application invocations.

  • 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

283
EXTENDING FIREWORKS
Cross-Product Extensions
Las
t
up
d
a
ted
12/8/2009
The
set
operation sets the object properties. The
set
operation can contain only the
obj
and
name
attributes and
exactly one parameter. The parameter must be the same data type as the data type of the property being set, or
Fireworks will return an error. In the following example, the client sets the property of “name” (a string providing
a directory path) to the value
file://hd/foo/stuff
:
<set obj="1" name="appDir"><string order="1" value="file://foo/stuff" /></set>
The
func
operation calls a method that operates on the specified object. The number and type of parameters vary
according to the method called by the
func
operation. In the following example, the client calls the
undo
method
to operate on the object with object ID 1:
<func obj="1" name="undo" />
The
release
operation informs the server that the client has finished working on the specified object. A
release
request must specify only an
obj
attribute and no subelements. In the following example, the client tells the server
that it is has finished working on the object with ID 1:
<release obj="1" />
Note:
Each type of request requires an obj attribute, and all but the release request require a name attribute. Requests
can be only of types get, set, func, or release. The RPC server rejects all other types.
Object IDs
RPC clients reference objects on the server by their object IDs. Because all functionality is exposed by means of objects,
every client request must contain a valid object ID. When an object that can be accessed through RPC is created, it is
assigned a unique object ID. The object retains that ID for its entire lifetime. This happens for all RPC server objects,
whether they are created directly by an RPC call or by an internal Fireworks function. The object IDs can be reused
after the corresponding object is destroyed.
Note:
The object ID number should be treated as a string data type that could contain non-numbers, (do not treat the
object ID as an integer data type).
Fireworks has the following four reserved object IDs:
"0"
This is the Invalid Object ID, used for nonexistent or invalid objects. It is not frequently used for the RPC client,
but it is used in several places for the RPC server.
"fw"
is the Fireworks Application Object ID. The Fireworks Application Object ID references the main application
object in Fireworks and is of the Fireworks class.
This object is used to open and create documents. In JavaScript, it is the object referenced by
App
or
fw
.
"smartShape"
is the SmartShape Object ID. This object id references the global JavaScript variable
smartShape
and is used to create an manipulate Auto Shapes.
"Document"
is the Fireworks Document Compatibility Object ID (it is deprecated, like its JavaScript counterpart).
It was used in Fireworks 2 for cleaning up file paths, and is included here only for completeness.
"Errors"
is the Fireworks Errors Object ID, used mainly for reporting and determining when errors occur in
Fireworks. Its JavaScript counterpart is
Errors
.
All other object IDs are generated when the object is created, and may or may not have the same IDs between
application invocations.