Skip to main content

JSExport

Trait JSExport 

Source
pub unsafe trait JSExport { }
Available on crate features JSExport and objc2 only.
Expand description

JSExport provides a declarative way to export Objective-C objects and classes – including properties, instance methods, class methods, and initializers – to JavaScript.

When an Objective-C object is exported to JavaScript, a JavaScript wrapper object is created.

In JavaScript, inheritance works via a chain of prototype objects. For each Objective-C class in each JSContext, an object appropriate for use as a prototype will be provided. For the class NSObject the prototype will be the Object prototype. For all other Objective-C classes a prototype will be created. The prototype for a given Objective-C class will have its internal [Prototype] property set to point to the prototype created for the Objective-C class’s superclass. As such the prototype chain for a JavaScript wrapper object will reflect the wrapped Objective-C type’s inheritance hierarchy.

JavaScriptCore also produces a constructor for each Objective-C class. The constructor has a property named ‘prototype’ that references the prototype, and the prototype has a property named ‘constructor’ that references the constructor.

By default JavaScriptCore does not export any methods or properties from an Objective-C class to JavaScript; however methods and properties may be exported explicitly using JSExport. For each protocol that a class conforms to, if the protocol incorporates the protocol JSExport, JavaScriptCore exports the methods and properties in that protocol to JavaScript

For each exported instance method JavaScriptCore will assign a corresponding JavaScript function to the prototype. For each exported Objective-C property JavaScriptCore will assign a corresponding JavaScript accessor to the prototype. For each exported class method JavaScriptCore will assign a corresponding JavaScript function to the constructor. For example:


```text
    @protocol MyClassJavaScriptMethods 
    - (void)foo;
    @end

    @interface MyClass : NSObject 
    - (void)foo;
    - (void)bar;
    @end
```

Data properties that are created on the prototype or constructor objects have the attributes: writable:true , enumerable:false , configurable:true . Accessor properties have the attributes: enumerable:false and configurable:true .

If an instance of MyClass is converted to a JavaScript value, the resulting wrapper object will (via its prototype) export the method foo to JavaScript, since the class conforms to the MyClassJavaScriptMethods protocol, and this protocol incorporates JSExport . bar will not be exported.

JSExport supports properties, arguments, and return values of the following types:

Primitive numbers: signed values up to 32-bits convert using JSValue’s valueWithInt32/toInt32. Unsigned values up to 32-bits convert using JSValue’s valueWithUInt32/toUInt32. All other numeric values convert using JSValue’s valueWithDouble/toDouble.

BOOL: values convert using JSValue’s valueWithBool/toBool.

id: values convert using JSValue’s valueWithObject/toObject.

Objective-C instance pointers: Pointers convert using JSValue’s valueWithObjectOfClass/toObject.

C structs: C structs for CGPoint, NSRange, CGRect, and CGSize convert using JSValue’s appropriate methods. Other C structs are not supported.

Blocks: Blocks convert using JSValue’s valueWithObject/toObject.

All objects that conform to JSExport convert to JavaScript wrapper objects, even if they subclass classes that would otherwise behave differently. For example, if a subclass of NSString conforms to JSExport, it converts to JavaScript as a wrapper object rather than a JavaScript string.

See also Apple’s documentation

Trait Implementations§

Source§

impl<T> ImplementedBy<T> for dyn JSExport
where T: ?Sized + Message + JSExport,

Source§

impl ProtocolType for dyn JSExport

Source§

const NAME: &'static str = "JSExport"

The name of the Objective-C protocol that this type represents. Read more
Source§

fn protocol() -> Option<&'static AnyProtocol>

Get a reference to the Objective-C protocol object that this type represents. Read more

Dyn Compatibility§

This trait is dyn compatible.

In older versions of Rust, dyn compatibility was called "object safety".

Implementations on Foreign Types§

Source§

impl<T> JSExport for ProtocolObject<T>
where T: ?Sized + JSExport,

Implementors§