This tab contains a code editor for editing and compiling the module's implementation:
It is beyond the scope of this documentation to describe the Module API and coding details. Use the Module Browser to examine the code for the Module API classes which have inlined documentation, plus examine existing module implementations to learn boilerplate patterns for how modules work with input data and generate output.
At a high level, the general development cycle for a new module is as follows:
Begin by saving a copy of an existing module that closely does what is needed by the new module. Modify its Module Definition and optionally Module Settings until it has the needed inputs for its operation.
You can optionally run the assembly editor in debug mode to trace your code. Enable debug mode here:
Use the Show/Hide Debugger link at the top right of the editor to toggle the debug window:
Debug information appears as the assembly is executed. Use _debug(content) found in the _mixinBase class to write information into the debug window. If the content is an object the debug window will inspect that object and give you links to inspect the content within it.
Test the Java implementation by executing the test assembly on the server:
Leave debug information on so that any _debug() output or runtime errors will appear:
A new browser tab/window will open with the output from the execution on the server:
It is best to have an XML Viewer plugin installed in your browser so the output XML will be formatted for viewing.
You can refresh the output page after making Java code changes and saving the module, for quick test iterations.
Post to our Help Forum when you need help building new modules.