WARNING: This server provides a static reference view of the NetKernel documentation. Links to dynamic content do not work. For the best experience we recommend you install NetKernel and view the documentation in the live system .

Endpoint
Name:nCoDE Runtime
Description:NetKernel Compositional Development Environment
Id:nCoDERuntime
Category:accessor prototype

nCoDE Runtime is an accessor that must be instantiated from a prototype. You must instantiate the prototype in your module to create an accessor that can receive requests.

Parameters

The nCoDERuntime prototype has the following initialisation parameters:

NameRulesTypingDefaultDescription
operatorMandatoryIdentifier or XML(none)
code definition
nameOptionalStringnCoDE Instance
name of endpoint
dynamicImportConfigOptionalIdentifier or XMLnull
enable dynamic imports and define configuration identifier

Here is an auto-generated example of how to instantiate an instance of nCoDE Runtime:

<accessor>
  <prototype>nCoDERuntime</prototype>
  <operator>code definition</operator>
</accessor>
Import Requirements

To use nCoDE Runtime accessor prototype you must import the module urn:org:netkernel:lang:ncode:

<import>
  <uri>urn:org:netkernel:lang:ncode</uri>
</import>

The nCoDE Runtime is a language runtime prototype which creates logical endpoints from a graphical definition edited using a graphical user interface. It translates then definition into DPML to be evaluated. For a more detailed introduction of the capabilities and use of nCoDE please see the nCoDE Introduction.

Operator

The operator parameter specifies a resource identifier that will be used to SOURCE the code definition or program. This resource must be mutable and support the SINK verb if you wish to use the graphical editor. If no resource exists then a blank initial definition will be created with no endpoints as a starting point for editing. There are no limitations on this resource, it may be provided by a fileset, pds, database etc.

dynamicImportConfig

The optional dynamicImportConfig parameter specifies a identifier of a resource that the nCoDE runtime will instantiate which exposes a standard DynamicImport definition. If no dynamicImportConfig parameter is provided then the nCoDE runtime will not support dynamic importing of endpoint palettes. For more details on using the dynamic import capability of nCoDE see the guide.

Example

Here is an example minimal space setup to instantiate an nCoDE instance and expose it to a fulcrum with a dynamic import hook.

<rootspace name="nCoDE Example Space">
  <fileset>
    <regex>res:/etc/system/SimpleDynamicImportHook.xml</regex>
  </fileset>
  <import>
    <uri>urn:org:netkernel:lang:ncode</uri>
    <private />
  </import>
  <import>
    <uri>urn:org:netkernel:ext:layer1</uri>
    <private />
  </import>
  <endpoint>
    <prototype>nCoDERuntime</prototype>
    <name>Example nCoDE</name>
    <operator>res:/resources/ncode1.xml</operator>
    <dynamicImportConfig>active:nCoDEDynamicImports</dynamicImportConfig>
  </endpoint>
  <endpoint>
    <prototype>DynamicImport</prototype>
    <config>active:nCoDEDynamicImports</config>
    <private />
  </endpoint>
  <fileset>
    <regex>res:/resources/ncode1.xml</regex>
    <poll>100</poll>
    <mutable>true</mutable>
    <private />
  </fileset>
</rootspace>