Options for the underlying surface widget.
Set this to false if you do not want the Surface to set itself up inside a runOutsideAngular call. We do not recommend
this. When the Surface setup is run inside Angular all of the event bindings from the surface's pan/zoom/drag handlers are piped
through Angular, causing change detection events, which can result in a performance hit. We've only added this in case there is
an unforeseen backwards compatibility issue in someone's app, but all of our testing of this change suggests that is unlikely.
ID to use for the created surface. Required.
ID of the Toolkit to which to attach the surface. Required.
Optional toolkitOptional parameters for the underlying Toolkit. These will be used only if the Toolkit instance with the given ID has not yet been created somewhere else in the app.
output event emitter, for proxying events from vertex components.
Options for the view - mappings of components and behaviour to model object types.
Provides a component that manages a surface.