The enovia.ini variable MX_EDITOR is used to label the button, and the variable MX_EDITOR_PATH is used to specify the path to the external
editor. Once specified, the dialog will include an additional button
used to launch the editor. All changes made to the code will automatically
be read back into the system. As a simple example, on Windows the settings
might be:
MX_EDITOR=notepad
MX_EDITOR_PATH=c:\winnt\system32\notepad.exe
Another approach is to extract the Java code out of the
ENOVIA Live Collaboration database and into a file directory. This can
be done using the extract program MQL command. The resulting code will be ready for compilation
(name mangling will already have been performed) and further development.
Some may choose to do all, or most of their editing in an offline
IDE. The only requirement is that JPO names must follow the Java language
naming convention. While editing outside the ENOVIA Live Collaboration
system, the names of JPO classes can be referenced in a semi-mangled
form. This form consists of the JPO name followed by the string "_mxJPO".
For example, if editing code that needs to instantiate an object defined
by the JPO "emxProject", the following would be used:
emxProject_mxJPO proj = new emxProject_mxJPO();
JPOs in theENOVIA Live Collaboration can be populated
with external files using the insert program MQL command. This command converts mangled names back into
the appropriate special macro form. The previous example would be changed
to:
${CLASS:emxProject} proj = new ${CLASS:emxProject}();