Module Implementation

this tab contains a code editor for editing and compiling the module's implementation modules can have two code implementations javascript for the browser and java for the server not all modules will have a server side java implementation, but all modules must have a browser side javascript implementation module implementations make use of the module api classes, whose implementations can be viewed in the module browser docid\ mhvb3edezpxpnndnmexcb the module api allows most javascript and java module implementations to be almost identical, with the java implementations only needing type information, e g "int" instead of "var" it is beyond the scope of this documentation to describe the module api and coding details use the module browser docid\ mhvb3edezpxpnndnmexcb 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 docid\ aapdcl6ecm shq6oyti1 and optionally module settings docid\ pkigzbovm5un begxye01 until it has the needed inputs for its operation focus first on the javascript implementation make needed code changes and test them in the assembly editor until confident the javascript is working as needed test the javascript implementation by running a test assembly in the assembly editor after you save the module, you can immediately run the test assembly the editor immediately uses any javascript code changes that were made 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 after the module's javascript implementation is tested and working as needed, copy the method contents to the same methods in the java implementation then convert all "var" definitions to the needed java types use the java compiler's error information to finish the conversion of the javascript code to java 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 community forum docid 4ohricqkb6o8x63ts7r3z when you need help building new modules