EDOBE XDOM TAKE 6 IR - PRODUCTSHEET Especificaciones descargar pdf (Pagina 213)

CHAPTER 7: Integrating External Libraries Defining entry points for indirect access 213

Support structures

These support structures are passed to functions that you define for your JavaScript interface:

SoCClientName

The SoCClientName data structure stores identifying information for methods and properties of

JavaScript objects created by shared-library C/C++ code. It is defined as follows:

SoCClientName {

char* name_sig ;

uint32_t id ;

char* desc ;

}

SoHObject

An opaque pointer (long *) to the C/C++ representation of a JavaScript object.

SoHServer

An opaque pointer (long *) to the server object, which acts as an object factory for

the shared library.

SoCClientName

A structure that uniquely identifies methods and properties.

TaggedData

A structure that encapsulates data values with type information, to be passed

between C/C++ and JavaScript.

name_sig

The name of the property or method, unique within the class.

Optionally contains a signature following an underscore, which identifies the types of

arguments to methods; see Function signatures

. When names are passed back to your

SoObjectInterface

functions, the signature portion is omitted.

A unique identifying number for the property or method, or 0 to assign a generated UID.

If you assign the UID, your C/C++ code can use it to avoid string comparisons when

identifying JavaScript properties and methods. It is recommended that you either assign all

UIDs explicitly, or allow them all to be generated.

desc

A descriptive string or NULL.

1 2 ... 208 209 210 211 212 213 214 215 216 217 218 ... 303 304

Sin comentarios

EDOBE XDOM TAKE 6 IR - PRODUCTSHEET Especificaciones Pagina 213